DB2 Replication Guide and Reference

Analyzing Data with PREPARE

Enter the following commands to prepare the analysis of the migration database after you run the BUILDDB.SQL file:

1. set db2dbdft=mig_db
   

2. ASNMIG PREPARE mig_db ver x
   

   Where:

   mig_db

   Name of the migration database where the global control tables are stored. This is a required parameter.

   Note:

   If you want to create your global migration control tables in a DB2 for MVS subsystem, DSNDB04 is the default database.

   ver

   Version of the migration data that you want to analyze. You can use L to select the latest version, or you can select a specific version as noted in your migration database. This is a required parameter.

   x

   Use either V or O in the position of this character. V validates only the replication definitions in the global control tables before proceeding with Version 5 migration. O updates the replication definitions in the global control tables based on the Version 5 control table data. This is an optional parameter. The default option is "O" for the first run of the PREPARE action, and "V" for subsequent runs.

   Note:

   Each time the PREPARE action is run for a given migration version, it puts the transformed or new values in the columns (other than the columns that contain the original replication definitions copied from Version 1 servers) in the ASN.GLOBAL_CD_CNTL or ASN.GLOBAL_REF_CNTL table. Therefore, the default option is "O" for the first run of the PREPARE action. When the migration program knows there are values in the columns prepared by the PREPARE action, it defaults this option to "V" to verify values you might have provided.

PREPARE puts an analysis trace into the PREPARE.TRC file, and puts an analysis summary into the PREPARE.RPT file. The trace file is not translated, and should be handled like the Apply trace file. You should always save the output of each run, and carefully analyze the PREPARE.RPT file for any migration issues.

Migration issues that the PREPARE action checks for are:

• Subscription predicates that limit the scope of data applied

• Subscriptions released by EI SQL statements to the IBMSNAP.REF_CNTL table

• Subscriptions referencing Version 1 control tables

• Subscriptions using the FA run mode. All other run modes are converted to type AO

• Subscriptions scheduled with ENABLE = -n

• SQL_STMTs directed to run elsewhere from the source or target server

• Configurations requiring simultaneous Version 5 migration

• Grouping subscriptions in the replication subscription

• DataJoiner servers

• Existence of convergent consistent tables

• Join registrations through views

[ DB2 List of Books | Search the DB2 Books ]