Replication Guide and Reference

Restrictions When Running the Capture Program

The following actions cause the Capture program to terminate while it is running. Stop the Capture program if you want to perform any of the following tasks:

• Cancel an existing replication source.

• Drop a replication source table.

• Make changes that affect the structure of source tables. This includes changes resulting from data definition language or utilities. Structural changes can compromise the data integrity of the copies.

Other Capture program restrictions are:

• Changes are not captured when the database is running with LOGMODE=N.

• One change data table exists per user table defined to the Capture program.

• You must specify DATA CAPTURE CHANGES on the CREATE or ALTER TABLE statement for the user tables.

• Tables with field procedures for columns (FIELDPROC specified on CREATE or ALTER TABLE) are not supported by Capture for VM.

• There can be only one Capture program per database, and each Capture program runs in its own virtual machine. The Capture program identifies itself as an APPC/VM resource. By default, the resource ID value is CAPTURE. To use a different resource ID or to allow multiple Capture programs to run on the system (for different DB2 databases), change the ENQ_NAME parameter in the ASNPARMS file.

• Because the Capture program identifies itself as an APPC/VM resource, you must specify appropriate IUCV VM/ESA System Directory control statements (such as IUCV *IDENT RESANY GLOBAL) for virtual machines that run the Capture program. For more information, see the VM/ESA Planning and Administration Guide.

• The Capture program requires access to the appropriate level of the C Run Time Library. On VM, you must issue GLOBAL LOADLIB SCEERUN before invoking ASNCCP.

[ DB2 List of Books | Search the DB2 Books ]