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

Assumptions, out of scope, and success criteria


A POV cannot be successful unless the customer and IT vendor define upfront what the definition of success is. The customer needs to know the end game, or the POV will never be considered complete, and both parties will blame each other for the lack of success. The assumptions are important to make sure the customer and Oracle both understand how the project will be implemented and what the end architecture will be. Assumptions also clear up any areas that are not well-defined at the start of the project so there is no misunderstanding of what the unknowns are going into the project. Items that were discussed and perhaps considered to be part of the solution but have been excluded are in the Out of scope section. Out of scope also defines very clearly any items that seem like they should be part of the project but both parties have decided they are not because of time or resource constraints.

Assumptions

The assumptions regarding POV were put...