00C900B0
Explanation
While formatting log records in response to a READS request for IFCID 0306, the Db2 database manager could not format a log record to match the row format that was current when the log record was written. This situation might occur for one of the following reasons:
- A schema-changing ALTER TABLE statement was issued, but no subsequent insert or update operation was issued. The alter operation generates a higher version number, but there is no insert or update operation to trigger an update to the system page.
- An ALTER TABLE statement performed an update operation, but the update was not correctly registered in the table's system pages.
- After the REORG utility was run on a table space, a READS request for IFCID 0306 was still processing the log records that were written before REORG was run. Running REORG had removed all system pages except the system page for the current version of the table space. However, when the Db2 database manager processed the READS request, it attempted to retrieve system pages that existed before REORG was run.
System action
When this code is returned in the output from a READS request for IFCID 0306, log records are returned, but the data in the log records does not reflect the table space format that was current when the log records were written.
If a replication product maintains the current and previous versions of the table
definition, and the PTF for Db2 APAR
PI93252 is applied, the replication program converts the log record's data to the version that was
current at the time the log record was written.
System programmer response
If a schema change prevents replication from starting or continuing, and a replication
product does not maintain the current and previous versions of the table definition, try the
following actions:
- Apply the PTF for Db2 APAR PI93252, if it is not already applied.
- Update the source table definition in the replication product.
- Remap the source table in the replication product.
Refer to the documentation for the replication product for details.
Problem determination
Collect the following diagnostic items:
- Console output from the system on which the job was run, and a listing of the SYSLOG data set for the period of time that spans the failure.
- SVC dump (or system dump), taken to SYS1.DUMPxx data set, as result of an operator-initiated dump command or SLIP trap exit.
- A listing of the SYS1.LOGREC data set, obtained by executing IFCEREP1.