DB2 - Problem description
Problem IC61997 | Status: Closed |
SQL1042C IN A LOG SHIPPING ENVIRONMENT FOLLOWING A "ROLLFORWARD TO END OF LOGS" OTHER THAN THE FIRST INVOCATION. | |
product: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
Problem description: | |
In a Log shipping environment using "roll forward to end of logs: during the replay of the transaction logs on the target server a SQL1042C is returned. The cause of the SQL1042C is due to the last logfile in the previous "roll forward to end of logs" only containting the initial two log records for a table reorg with the "using" clause. The subseqent rollforward deletes a metadata file in the temporary tablespace specified by the "using" clause in the reorg, which is required by the table reorg. | |
Problem Summary: | |
In a Log shipping environment using "roll forward to end of logs: during the replay of the transaction logs on the target server a SQL1042C is returned. The cause of the SQL1042C is due to the last logfile in the previous "roll forward to end of logs" only containting the initial two log records for a table reorg with the "using" clause. The subseqent rollforward deletes a metadata file in the temporary tablespace specified by the "using" clause in the reorg, which is required by the table reorg. | |
Local Fix: | |
i) Ensure that any rollfroward contains all logs used for a table reorg in the log shipping environment. ii) In a log shipping environment use a point in time (PIT) to rollforward, instead of end of logs. | |
available fix packs: | |
DB2 Version 9.7 Fix Pack 1 for Linux, UNIX, and Windows | |
Solution | |
First fixed in DB2 Version 9.7 Fix Pack 1. | |
Workaround | |
i) Ensure that any rollfroward contains all logs used for a table reorg in the log shipping environment. ii) In a log shipping environment use a point in time (PIT) to rollforward, instead of end of logs. | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 15.07.2009 31.12.2009 31.12.2009 |
Problem solved at the following versions (IBM BugInfos) | |
9.7.FP1 | |
Problem solved according to the fixlist(s) of the following version(s) | |
9.7.0.1 |