Precise Instantiation for Oracle GoldenGate for Db2 for i
Learn about configuring an initial load of target data, adding the required processes to instantiate replication, and perform the instantiation. The expected outcome of these steps is that source-target data is made consistent (known as the initial synchronization), and that Oracle GoldenGate captures and delivers ongoing transactional changes so that consistency is maintained going forward.
During the initialization of the Oracle GoldenGate environment, you will be doing an initial data synchronization and starting the Oracle GoldenGate processes for the first time. In conjunction with those procedures, you will be creating the Extract and Replicat process groups.
To create an Extract process group, an initial start position for data capture must be established. This initial position will be based on a transaction boundary that is based on either of the following:
-
a timestamp
-
the end of the journal(s)
-
A specific system sequence number
-
A specific sequence number in the journal(s)
When Extract starts for the first time to begin capturing
data, it captures all of the transaction data that it encounters
after the specified start point, but none of the data that
occurred before that point. To ensure that Extract does not
start in the middle of ongoing transactions that would be
discarded, set the tables that are to be captured to an inactive
state. You can either put the system into a restricted state by
using the ALCOBJ
command to lock the objects or
libraries, or you can force all of the current transactions on
those tables to stop at a certain point.
After initialization is complete, remember to unlock any
objects that you locked. To do so, log off of the session that
locked the objects or use the DLCOBJ
command
from the IBM i command line.