Operating the Apply program for SQL Replication
Operating the Apply program includes such tasks as starting and stopping and using the ASNDONE and ASNLOAD exit routines.
- Starting the Apply program (Linux, UNIX, Windows, z/OS)
You can start an instance of the Apply program to begin applying data to your targets. - Starting an Apply program (System i)
You can start an instance of the Apply program to begin applying data to your targets. - Default operating parameters for the Apply program
When you create the Apply control tables, default values for the Apply operating parameters are saved in the IBMSNAP_APPPARMS table. - Descriptions of Apply operating parameters
When you start the Apply 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 Apply operating parameters
You can change the default values for the operational parameters to values that you typically use in your environment. You can also override these default values when you start the Apply program. - Changing saved Apply parameters in the IBMSNAP_APPPARMS table (z/OS, Linux, UNIX, Windows)
The IBMSNAP_APPPARMS table contains the saved operating parameters for the Apply program. When you start the Apply program, it uses values from this table unless you temporarily override these values by using startup parameters. - Stopping the Apply program
When you stop the Apply program, it no longer copies data to the target tables, and it updates the control tables to ensure that the program starts cleanly the next time that you start it. - Where the Apply program stores details about referential integrity failures
You can find details about rows that were not applied to target tables because of referential integrity (RI) violations. The Apply program in SQL Replication writes these details to a file. - Modifying the ASNDONE exit routine (z/OS, Linux, UNIX, Windows)
You can customize the ASNDONE exit routine on Linux, UNIX, Windows, and z/OS® operating systems to modify the behavior of the Apply program after it finishes processing subscriptions. - Modifying the ASNDONE exit routine (System i)
You can customize the ASNDONE exit routine on System i™ operating systems to modify the behavior of the Apply program after it finishes processing subscriptions. - Refreshing target tables by using the ASNLOAD exit routine
You can use the ASNLOAD exit routine to perform a full refresh of target tables more efficiently than the Apply program's normal method of loading data into targets. - Refreshing one table in a multi-table subscription set
You can prompt the replication programs to reload one table in a subscription set that contains multiple tables. To do this, you use SQL to update values in the IBMSNAP_SUBS_MEMBR table. - Ensuring that utilities used for full refresh wait for committed data
If you specify that the Apply program use the ASNLOAD exit routine with a DB2® for Linux, UNIX, and Windows Version 9.7 and newer source, you must ensure that the utilities that are used for the full refresh wait for committed data.