Xxxxx

An Oracle White Paper June 2010

Oracle GoldenGate Best Practices: Instantiation from an Oracle Source Database

Instantiation from an Oracle Source Database: Oracle GoldenGate

Executive Overview............................................................................. 1 Introduction ......................................................................................... 1 OracleGoldenGate Token - LOGCSN ................................................ 3 Delivery Process (Replicat) Use of LOGCSN ................................. 5 Before Starting Instantiation................................................................ 6 Homogeneous Instantiation Methods.................................................. 7 Cloning with Oracle RMAN............................................................. 7
Sample Steps - Cloning with Oracle RMAN ........................................... 7

Notes for Oracle RAC and ASM.................................................... 11 Additional Information on RMAN approach ................................... 11 Oracle Data Guard ........................................................................ 12 Heterogeneous InstantiationMethods .............................................. 13 Transportable Tablespaces........................................................... 14 GoldenGate Initial Load (Oracle to Any) ....................................... 14 Oracle EXPDP/IMPDP or EXP/IMP Utilities.................................. 14
Example 1: full database export using expdp ...................................... 15Example 2: schema export using exp .................................................. 16

Conclusion ........................................................................................ 18

Instantiation from an Oracle Source Database: Oracle GoldenGate

Executive Overview
This document is an introduction to Oracle GoldenGate’s best practices and guidelines for instantiation of a targetdatabase from an Oracle Source Database. This document is intended for Oracle Database Administrators (DBAs), and Oracle Developers with some basic knowledge of Oracle GoldenGate software product. The document is intended to be a supplement to the existing series of documentation available from Oracle. The following assumptions have been made during the writing of this document:
• • • •

Thereader has basic knowledge of Oracle GoldenGate products and concepts Referencing Oracle GoldenGate Version 10 and above Referencing Oracle Version 9.2 and above Referencing OS: All Oracle GoldenGate supported platforms for Oracle

Introduction
Oracle GoldenGate provides data capture from transaction logs and delivery tor heterogeneous databases and messaging systems. Oracle GoldenGate provides aflexible, de-coupled architecture that can be used to implement virtually all replication scenarios. One of the biggest challenges in creating a target database for replication is to insure that no “collisions” (applying data that has been already been "applied" by virture of copying data after the same change data has been captured) or data loss will occur when applying the change data after theinitial instantiation of the target database. Oracle GoldenGate has addressed this issue by including functionality to apply the change data to the target at the appropriate CSN (Commit Sequence Number) where no collisions will occur. Please not that OGG uses "CSN" and not "SCN", which are functionally interchangeable but syntactically distinct. To use this functionality without incurring anydata loss you have to make sure to use a read consistent image of your source database to do the instantiation and keep track of the CSN of

Instantiation from an Oracle Source Database: Oracle GoldenGate

your consistent image. This document provides more details and examples on how to use LOGCSN which is stored in the Oracle GoldenGateTrail Files starting with Oracle GoldenGate version 10....