BSDS record format conversion is required

The BSDS must be converted to use the 10-byte format RBA and LRSN records before Db2 12 can start.

At migration to Db2 12, you cannot start Db2 12 until the BSDS is converted to use the 10-byte RBA and LRSN formats. You can convert the BSDS before or during the Db2 12 migration process.

Before you can convert the BSDS, the Db2 subsystem or data sharing member must be started in Db2 11 new-function mode.

Attention: After the BSDS is converted to the 10-byte format, Db2 stops issuing messages to warn you about the risk of reaching the 6-byte RBA or LRSN limits. The increased size of all log records also accelerates progress toward the 6-byte RBA logging limit.

Continuously monitor the RBA and LRSN values until all catalog, directory, and user objects are converted to the 10-byte RBA or LRSN format. Failure to convert page sets before the 6-byte soft logging limit is reached results in failed updates with reason code 00C2026D, and any objects still in the 6-byte format become read-only. RBA or LRSN values greater than x'F00000000000' indicate that your system is at risk of reaching the 6-byte logging limit. For more information about the RBA and LRSN logging limits, see What to do before RBA or LRSN limits are reached.

Start of change In a data sharing environment, page sets contain LRSNs instead of RBAs. After the BSDS has been converted to allow for 10-byte LRSNs, an LRSN that is greater than 6 bytes does not result in failed updates with reason code 00C2026D. It is recommended that after the BSDS has been converted, the catalog and directory table spaces are converted before any other objects. Other objects need to be converted to extended format before the LRSN value reaches the 6-byte LRSN limit. End of change

For instructions, see Convert BSDS records to the extended 10-byte format: DSNTIJCB.