Initial load with change data capture in GoldenGate
Initial load with change data capture in GoldenGate.
1. Initial load with change data capture
Following are descriptions of the steps in the figure:
1.1. Start the Extract
Note: You need to start the Extract before the initial load, so that any SQL data manipulation language (DML) changes made during the load process can be captured.
1.2. Start the data pump
Configure and start the data pump to send extracted changes captured by the local Extract into the source trail across the network to the target server. When on the target server, the changes are written to the remote trail file.
1.3. Perform the initial load
Load the data using either GoldenGate or vendor DBMS utilities. Doing so creates a synchronized copy of each database, except for changes that were captured during the load process by the Extract. These changes will be applied in the next step when the Replicat is started. You only need to run an initial data load the first time you setting up replication. After this, GoldenGate will keep the data synchronized on an ongoing basis using the Extract and Replicat processes.
1.4. Start the Replicat.
Configure and start the Replicat to begin applying changes from the remote trail file. Changes that were captured while the initial-load process was executing have already been written to the remote trail file. It may take a Replicat some time to catch up with the changes, depending on the data volume and the length of time changes were captured during the load process. Also, some of these changes may cause data conflicts, because activity was occurring in the database at the same time the data load was running.
See Also: