Operating the Capture program for SQL Replication
This section pertains to log-based capture for DB2® databases. If you are using trigger-based capture, the triggers are created at registration, and you do not perform the operations described in this section.
- Starting the Capture program (Linux, UNIX, Windows, and z/OS)
Start the Capture program to begin capturing data from the log for DB2 databases. If you are using trigger-based capture for a non-DB2 relational source, triggers are created at registration and you do not need to start the Capture program. - Starting the Capture program from a known point in the DB2 log
You can prompt the Capture program to reread the DB2 recovery log from a known point and reprocess log records that were already captured and applied. - Starting the Capture program (System i)
Start the Capture program to begin capturing data from the journal. - Using SQL to issue commands to a running Capture program (z/OS)
You can issue commands to a running Capture program by inserting SQL statements, enabling you to operate Capture without the MODIFY command or without having to wait for signals to be processed. - Default operating parameters for the Capture program
When you create the Capture control tables, default values for the Capture program's operating parameters are saved in the IBMSNAP_CAPPARMS table. - Descriptions of Capture operating parameters
When you start the Capture program, you can optionally select startup parameters. Here are the startup parameters and recommendations for when to choose one value over another for each parameter. - Methods of changing Capture parameters
You can change the saved values of Capture operating parameters, and you can also temporarily override these values when you start the program or while the program is running. - Altering the behavior of a running Capture program
You can dynamically change the value of one or more Capture operating parameters. The changes are not saved in the IBMSNAP_CAPPARMS table, but are used until you stop the Capture program or supply new values. - Changing saved operating parameters in the IBMSNAP_CAPPARMS table
The IBMSNAP_CAPPARMS table contains the saved operating parameters for the Capture program. When you start the Capture program, it uses values from this table unless you temporarily override these values by using startup parameters or while the program is running. - Stopping the Capture program
You can stop the Capture program for a particular Capture schema. When you stop the Capture program, it no longer captures data from the source. - Reinitializing Capture
Reinitialize the Capture program if you change any attributes of existing registered objects while the Capture program is running. - Suspending the Capture program (Linux, UNIX, Windows, z/OS)
You can suspend the Capture program to free operating system resources during peak periods without destroying the Capture program environment. - Resuming Capture (Linux, UNIX, Windows, z/OS)
You must resume a suspended Capture program if you want it to start capturing data again. - Prompting a Capture program to ignore unwanted transactions
You can prompt a Capture program to ignore transactions in the DB2 recovery log, and these transactions will not be captured.