DB2 - Problembeschreibung
Problem IC72449 | Status: Geschlossen |
SYSPROC.ADMIN_REMOVE_MSGS DOES NOT DELETE MESSAGE FILES(GENERATE D BY ADMIN_CMD) WHOSE NAME IS APPENDED WITH UNDERSCORE(_). | |
Produkt: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
Problembeschreibung: | |
Executing a LOAD operation via ADMIN_CMD and option MESSAGES ON SERVER creates and leaves a message file on the database server. This message file is named like 'LOAD_<STRING>_<USERID-postfix>'. SYSPROC.ADMIN_REMOVE_MSGS should be used to remove these message files if no longer needed. In certain situations DB2 will name the message file like following: 'LOAD_<STRING>_' E.g. if the user id information is not available at the time of the DB2 internal message file rename. The attempt to remove a message file whose name ends with underscore will not be successful although ADMIN_REMOVE_MESSAGES reports successful execution as shown below. # ls LOAD_N8BYSB_ # db2 "CALL SYSPROC.ADMIN_REMOVE_MSGS('31393')" Return Status = 0 # ls LOAD_N8BYSB_ This APAR addresses the correct removal of such message files. | |
Problem-Zusammenfassung: | |
**************************************************************** * USERS AFFECTED: * * All * **************************************************************** * PROBLEM DESCRIPTION: * * See Problem Description above. * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 Version 9.7 Fix Pack 4 * **************************************************************** | |
Local-Fix: | |
Check the default message file path (if DB2_UTIL_MSGPATH is not set) '<instowner home>/sqllib/tmp' and delete these message files manually if no longer needed. | |
verfügbare FixPacks: | |
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows | |
Lösung | |
First fixed in DB2 Version 9.7 Fix Pack 4 | |
Workaround | |
keiner bekannt / siehe Local-Fix | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 08.11.2010 01.05.2011 01.05.2011 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
9.7.FP4 | |
Problem behoben lt. FixList in der Version | |
9.7.0.4 |