This document will outline the Best Practice approach for Instantiating a DB2 target database from a DB2 or other database source system.
One of the biggest challenges in creating a DB2 target database for replication is to insure that no collisions or data loss will occur when applying the change data after the initial 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. To use this functionality without incurring any data loss, be sure to use a read consistent image of your source database to do the instantiation and keep track of the CSN of 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.
The complete document can be found on the Oracle Support site under the document ID:1310542.1