Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Oracle Data Integrator 11g Cookbook

You're reading from   Oracle Data Integrator 11g Cookbook This book is all you need to take your understanding of Oracle Data Integrator to the next level. From initial deployment right through to esoteric techniques, the task-based approach will enhance your expertise effortlessly

Arrow left icon
Product type Paperback
Published in May 2013
Publisher Packt
ISBN-13 9781849681742
Length 352 pages
Edition 1st Edition
Languages
Arrow right icon
Toc

Table of Contents (19) Chapters Close

Oracle Data Integrator 11g Cookbook
Credits
Foreword
About the Authors
About the Reviewers
www.PacktPub.com
Preface
1. Installation, Deployment, and Configuration 2. Defining the Oracle Data Integrator Security FREE CHAPTER 3. Advanced Topology 4. Using Variables 5. Knowledge Module Internals 6. Inside Knowledge Modules – SCD and CDC 7. Advanced Coding Techniques 8. Package Loops and File Processing 9. XML and Web Services 10. Advanced Coding Techniques Using the ODI SDK 11. More on ODI Index

Using one single interface to load changes that occur in any dimensions


When data is de-normalized, data that is originally in multiple source tables often ends up in a single target table. From that perspective, changes that occur in any one of the source tables have to be reflected in the same target table.

One challenge here is that if you simply join the changes from the different source tables while loading the target table, you will only have data to load if all tables have changes: that is, if we simply join the changes from SRC_EMP to the changes from SRC_DEPT, we will only have target data to process when changes occur simultaneously in both tables. If one of the sets is empty, then we will have nothing to process.

For this reason, ODI will only accept one journalized table per data set, and the interface must be duplicated to process the changes of every single one of the source tables. This can be a daunting task if you have a lot of sources and complex mappings. With this recipe...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime
Banner background image