Book Image

Oracle Information Integration, Migration, and Consolidation

Book Image

Oracle Information Integration, Migration, and Consolidation

Overview of this book

The book covers data migration, data consolidation, and data integration, the three scenarios that are typically part of the information integration life cycle. Organizations typically find themselves migrating data to Oracle and either later, or at the same time, consolidating multiple database instances into a single global instance for a department, or even an entire company. The business savings and technical benefits of data consolidation cannot be overlooked, and this book will help you to use Oracle's technology to achieve these goals. This highly practical and business-applicable book will teach you to be successful with the latest Oracle data and application integration, migration, information life-cycle management, and consolidation products and technologies.In this book, you will gain hands-on advice about data consolidation, integration, and migration using tools and best practices. Along the way you will leverage products like Oracle Data Integrator, Oracle GoldenGate, and SQL Developer, as well as Data Hubs and 11gR2 Database. The book covers everything from the early background of information integration and the impact of SOA, to products like Oracle GoldenGate and Oracle Data Integrator. By the end you'll have a clear idea of where information and application integration is headed and how to plan your own projects.
Table of Contents (17 chapters)
Oracle Information Integration, Migration, and Consolidation
Credits
About The Author
About the Contributing Authors
About the Reviewers
www.PacktPub.com
Preface

Technical challenges of information integration


The technical challenges with any information integration all stem from the fact that the application accesses heterogeneous data (VSAM, IMS, IDMS, ADABAS, DB2, MSSQL, and so on) that can even be in a non-relational hierarchical format. Some of the technical problems include:

  • The flexible file definition feature used in COBOL applications in the existing system will have data files with multi-record formats and multi-record types in the same dataset — neither of which exist in RDBMS. Looping data structure and substructure or relative offset record organization such as a linked list, which are difficult to map into a relational table.

  • Data and referential integrity is managed by the Oracle database engine. However, legacy applications already have this integrity built in. One question is whether to use Oracle to handle this integrity and remove the logic from the application.

  • Finally, creating an Oracle schema to maximize performance, which includes mapping non-oracle keys to Oracle primary and secondary keys; especially when legacy data is organized in order of key value which can affect the performance on an Oracle RDBMS. There are also differences in how some engines process transactions, rollbacks, and record locking.