DSNJ122I DUAL BSDS DATA SETS ARE OUT OF SYNCHRONIZATION

Explanation

During log manager initialization or stand-alone utility initialization, the dual BSDS data sets were found to differ in content in one of the following ways:

  • A record that exists in both BSDSs is not identical. (This comparison accounts for some minor differences.)
  • A record exists in one BSDS and not in the other.
  • A required record is missing from one BSDS copy.

The print log map (DSNJU004) utility does not print all of the information in the BSDS. Therefore, the output from DSNJU004 might be identical for two BSDSs, but the BSDSs might still be different.

Example scenarios that might cause this problem include the following situations:

  • The change log inventory (DSNJU003) utility was used to alter one copy of a BSDS and not the other.
  • Db2 was forced into single-BSDS mode due to an I/O error, and the stopped BSDS copy was not recovered.

System action

Db2 startup is terminated if the problem is detected during log manager initialization. If the problem is detected by a stand-alone utility, the utility terminates with return code 4.

Operator response

Notify the system programmer.

System programmer response

If the message was issued by Db2 initialization, run DSNJU004 against each BSDS to determine which is more current. Delete the outdated copy, define a replacement for the deleted data set, and copy the remaining BSDS to the replacement by using IDCAMS REPRO.

If the message was issued by the DSNJCNVT utility, you can follow the same procedure as if the message was issued by Db2 initialization. Alternatively, DSNJCNVT can be run with the SYSUT2 DD statement omitted and a SYSUT1 DD statement that specifies the correct BSDS copy. The converted BSDS is written to the SYSUT3 data set and, if provided, the SYSUT4 data set.