DB2 - Problem description
Problem IC70207 | Status: Closed |
INVALID OVERFLOW LOG PATH (OVERFLOWLOGPATH) CAUSING DB2 BACKUP TO FAIL WITH SQL2428N. | |
product: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
Problem description: | |
Invalid path condition on the log overflow path results in terminating the attempt to find the log file rather than checking the log archive path as it would in the SQLO_FNEX (file not found) case. This should be corrected as the log archive path is checked if the overflowlogpath exists. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * DB2 users on all hardware * **************************************************************** * PROBLEM DESCRIPTION: * * Invalid path condition on the log overflow path results in * * * * terminating the attempt to find the log file rather than * * * * checking the log archive path as it would in the SQLO_FNEX * * (file * * not found) case. * * * * This should be corrected as the log archive path is checked * * if * * the overflowlogpath exists. * **************************************************************** * RECOMMENDATION: * * upgrade to this fix. In addition see work around in APAR * * information. Manually creating the expected overflowpath, * * or activating and deactivating the database so db2 realizes * * the overvlowpath does not exist. * **************************************************************** | |
Local Fix: | |
Deactivate and reactivate the database so that db2 realizes the overflowpath defined in the dbcfg is not present and does not attempt to use it. Or create the overflowlogpath manually. | |
available fix packs: | |
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows | |
Solution | |
This problem is resolved by the fix, in that the file will now be looked for on the archive path if the overflowpath does not exist. | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 26.07.2010 07.06.2011 07.06.2011 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) | |
9.7.0.4 |