DB2 - Problem description
Problem IC62378 | Status: Closed |
REDISTRIBUTE NOT FLUSHING LOG RECORDS IF IT CRASHES | |
product: | |
DB2 FOR LUW / DB2FORLUW / 950 - DB2 | |
Problem description: | |
If the Redistribute utility crashes at a very specific timing point, it can corrupt the dictionary object. A subsequent Redistribute operation will either fails in a way that cannot be recovered from gracefully (ie. a restore from backup would be required), or the table corruption may go undetected. Upon database restart after instance is restarted, a table's dictionary may appear to be missing. If the dictionary is located on new extent (one that was not present in the table BEFORE the Redistribute started), then this extent would not exist in the container -- the missing dictionary makes any existing table data pages useless. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * redistribute could crash if update dictionary a particular * * time (timing related) * **************************************************************** * PROBLEM DESCRIPTION: * * Redistribute does not flush logs in a timely manner if * * redistribute crashes * **************************************************************** * RECOMMENDATION: * * upgrade to v97 or install the latest v95 fix pack * **************************************************************** | |
Local Fix: | |
available fix packs: | |
DB2 Version 9.5 Fix Pack 5 for Linux, UNIX, and Windows | |
Solution | |
v95 code base will be updated so that if redistribute does crash it will have access to appropriate / updated information. The fix is to flush the logs on an insert to a db2 dictionary | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 05.08.2009 15.01.2010 15.01.2010 |
Problem solved at the following versions (IBM BugInfos) | |
9.5., 9.7. | |
Problem solved according to the fixlist(s) of the following version(s) | |
9.5.0.5 |