DB2 - Problem description
Problem IC63348 | Status: Closed |
To dump additional diagnostic information during migration. | |
product: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
Problem description: | |
If database migration were to fail while migrating the system catalog table SYSIBM.SYSCOLUMNS, due to the migrating database containing corruption, we will not have enough diagnostic information to identify the table that is corrupted. Without this fix, customers will need to restore their downlevel backup images back to the downlevel release, then would require a *special build* to find out which table is actually corrupted. With this fix, the db2diag.log will contain sufficient information such that no special build would be required, hence, allowing us to cleanup the corruption on their downlevel database much quicker. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * ALL * **************************************************************** * PROBLEM DESCRIPTION: * * To dump additional diagnostic information during migration. * **************************************************************** * RECOMMENDATION: * * Upgrade to 9.7 FP1 * **************************************************************** | |
Local Fix: | |
available fix packs: | |
DB2 Version 9.7 Fix Pack 1 for Linux, UNIX, and Windows | |
Solution | |
Problem was first fixed in Version 9.7 Fix Pack 1. | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 23.09.2009 22.12.2009 22.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 |