Book Image

Oracle Goldengate 11g Complete Cookbook

By : Ankur Gupta
Book Image

Oracle Goldengate 11g Complete Cookbook

By: Ankur Gupta

Overview of this book

Oracle Goldengate 11g Complete Cookbook is your complete guide to all aspects of Goldengate administration. The recipes in this book will teach you how to setup Goldengate configurations for simple and complex environments requiring various filtering and transformations. It also covers various aspects of tuning and troubleshooting the replication setups using exception handling, custom fields, and logdump utility.The book begins by explaining some basic tasks like Installation and Process groups setup. You will then be introduced to some further topics including DDL replication and various options to perform Initial Loads. You will then learn some advanced administration tasks such as Multi Master replication setup and conflict resolution. Further recipes, contain the cross platform replication and high availability options for Goldengate.
Table of Contents (16 chapters)
Oracle GoldenGate 11g Complete Cookbook
Credits
About the Author
About the Reviewers
www.PacktPub.com
Preface
Index

Creating a multimaster GoldenGate replication configuration


Most of the configurations that we have discussed so far in this book had a one way replication stream. There are a few scenarios where such a setup will not be adequate. A very common usage where a single stream of replication will not be sufficient is a distributed environment where the database is divided into region-specific databases but the users can access the information of any region from any database. In order to keep the tables in sync in such an environment, you need multiple streams to synchronize the data both ways. Such a setup is called active-active or multimaster replication setup.

Another popular use of using active-active replication is maintaining a replicated system which could also be used to serve the complete production load in the event of a failover. Although, you can create a read-only standby database which is kept in sync with the primary database using Active Dataguard, but cannot perform any changes...