home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Latest versionsfixlist
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IT03023 Status: Closed

PD_GET_LOG_MSGS RETURNS SQL22237N WHEN ADMIN LOG NOT EXISTING

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
Example query: 
 
 db2 -x "SELECT distinct TIMESTAMP, varchar (SUBSTR(MSG,1,100)) 
AS MSG FROM TABLE ( PD_GET_LOG_MSGS( CURRENT TIMESTAMP - 1 DAYS) 
) AS PD ORDER BY TIMESTAMP DESC" 
SQL22237N  A file system error occurred when performing an 
operation on path 
"/dump/newdemo1/DIAG0129/newdemo1*.nfy". Reason code = "2". 
 
Such SQL22237N is due to admin log ( <instance>.log, or 
<instance>.*.log ) not existing under the DIAGPATH 
directories
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 10.1 Fix Pack 5.                      * 
****************************************************************
Local Fix:
Create a fake admin log, or copy another admin log to the 
directory that is missing the admin log, then the error should 
be gone.
Solution
First fixed in DB2 Version 10.1 Fix Pack 5.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
08.07.2014
15.07.2015
15.07.2015
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.5 FixList