DB2 - Problem description
Problem IT11251 | Status: Closed |
UPDATES VIA WHERE CURRENT OF A WITH HOLD CURSOR MAY BE MISSED BY A TABLE SPACE ROLL FORWARD | |
product: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
Problem description: | |
When using WHERE CURRENT OF CURSOR, the table space skipping logic may not properly track which log files are needed for a table space roll forward. Some log records for a tablespace being rolled forward may not be processed. This can lead to table space roll forward failure, or may lead to missing and/or incorrect data for the tablespace being rolled forward. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * Any performing table space roll forward and WHERE CURRENT OF * * cursor WITH HOLD * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to the latest fix pack. * **************************************************************** | |
Local Fix: | |
Set the DB2_COLLECT_TS_REC_INFO registry variable to OFF to disable the log file table space skipping optimization | |
Solution | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 15.09.2015 06.10.2015 06.10.2015 |
Problem solved at the following versions (IBM BugInfos) | |
9.7.FP11 | |
Problem solved according to the fixlist(s) of the following version(s) | |
9.7.0.11 |