|
Problem IC72450
|
Status: Closed |
SYSPROC.ADMIN_REMOVE_MSGS DOES NOT DELETE MESSAGE FILES(GENERATE D BY ADMIN_CMD) WHOSE NAME IS APPENDED WITH UNDERSCORE(_). |
| product: |
DB2 FOR LUW / DB2FORLUW / 980 - DB2 |
| Problem description: |
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 Summary: |
****************************************************************
* USERS AFFECTED: *
* All *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Problem Description above. *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 Version 9.8 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. |
| available fix packs: |
DB2 Version 9.8 Fix Pack 4 for AIX and Linux
DB2 Version 9.8 Fix Pack 5 for AIX and Linux
|
| Solution |
First fixed in DB2 Version 9.8 Fix Pack 4 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 08.11.2010
02.08.2011
02.08.2011 |
| Problem solved at the following versions (IBM BugInfos) |
9.8.FP4
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.8.0.4
|
 |
