Replication Guide and Reference

Troubleshooting: Problems Using the Capture Program

This section describes commonly known issues with the Capture program. Before running Capture for VSE, ensure that you have all the PTFs for your level of DB2. Specific Capture program problems are described below.

Problem

Capture for VSE does not start.

Ensure that:

• Access has been given for the database log and directory minidisks by specifying the DLBLs in the Capture program: startup JCL.

• Access has been given to the C Run Time Library.

• The ASNLMAIN package file has been loaded to the database.

Problem

The Capture program is not capturing updates.

Any of the following could prevent Capture for VSE from capturing updates:

• DATA CAPTURE CHANGES was not specified on the base tables to be captured.

• The proper order for starting the Capture and Apply programs was not used:

  1. Replication sources and subscriptions must be defined before starting Capture for VM.

  2. Start Capture for VM and look for message number ASN0100I (initialization completed) on the virtual machine console or in the ASN.IBMSNAP_TRACE table.

  3. Start the Apply program.

Check the ASN.IBMSNAP_TRACE table for possible error messages.

Problem

I'm not sure if the Capture program is running successfully.

After you start the Capture and Apply programs, the Apply program performs a full refresh to populate the target tables. Then the Capture program writes message ASN0104I to the ASN.IBMSNAP_TRACE table, providing information related to table owner name, table name, and starting log sequence number value. This provides a point from which the Capture program starts to capture updates.

Subsequent captured updates are placed in change data tables and eventually applied to target tables and pruned from the change data table. After the Capture program runs for some time, you should see rows in the change data table if changes are made to the source. Periodically, check the ASN.IBMSNAP_TRACE table to see the progress made by the Capture program. If it encounters errors, it sends them to the console and also logs them in the trace table. Similarly, the Apply program logs its information in the userid.IBMSNAP_TRAIL table.

Problem

Capture for VSE: issued message ASN0000E instead of the proper message number.

Capture for VSE issued a generic message instead of a proper message. This happens if the specified VSAM message file in the Capture startup JCL was not found. See the Capture for VSE program directory for information on installing the VSAM message file.

Problem

Capture for VSE terminated unexpectedly.

The Capture for VSE program terminates either because of a severe error, or when you issue the STOP command. The Capture program terminates with a return code that indicates successful or unsuccessful completion. Return codes are:

0

STOP command issued

8

Error during initialization

12

Any other severe error

[ DB2 List of Books | Search the DB2 Books ]