Book Image

Oracle Data Integrator 11g Cookbook

Book Image

Oracle Data Integrator 11g Cookbook

Overview of this book

Oracle Data Integrator (ODI) is Oracle's strategic data integration platform for high-speed data transformation and movement between different systems. From high-volume batches, to SOA-enabled data services, to trickle operations, ODI is a cutting-edge platform that offers heterogeneous connectivity, enterprise-level deployment, and strong administrative, diagnostic, and management capabilities."Oracle Data Integrator 11g Cookbook" will take you on a journey past your first steps with ODI to a new level of proficiency, lifting the cover on many of the internals of the product to help you better leverage the most advanced features.The first part of this book will focus on the administrative tasks required for a successful deployment, moving on to showing you how to best leverage Knowledge Modules with explanations of their internals and focus on specific examples. Next we will look into some advanced coding techniques for interfaces, packages, models, and a focus on XML. Finally the book will lift the cover on web services as well as the ODI SDK, along with additional advanced techniques that may be unknown to many users.Throughout "Oracle Data Integrator 11g Cookbook", the authors convey real-world advice and best practices learned from their extensive hands-on experience.
Table of Contents (19 chapters)
Oracle Data Integrator 11g Cookbook
Credits
Foreword
About the Authors
About the Reviewers
www.PacktPub.com
Preface
Index

Modifying a Slowly Changing Dimension KM to allow undefined behaviors


When working with a slowly changing dimension, you may sometimes encounter a dimension table that has dozens (or perhaps hundreds) of attributes, making the task of setting the SCD behavior for each column very tiresome. There may also be occasions when business requirements dictate that all activity on a specific dimension table be captured historically, that is, all columns are considered to be the "trigger" fields.

In order to address these two situations, a few simple modifications can be made to the SCD IKM to allow the developer to avoid having to set the SCD behavior for every column. By making these simple modifications, the developer will only need to set the behaviors for the Surrogate Key, the Natural Key, the Active Flag, and The Starting and Ending date columns; all other columns will be implicitly managed as trigger fields by automatically setting the Add Row on Change condition.

Although it's certainly possible...