home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Neueste VersionenFixList
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
Haben Sie Probleme? - Kontaktieren Sie uns.
Kostenlos registrieren anmeldung-x26
Kontaktformular kontakt-x26

DB2 - Problembeschreibung

Problem IT03023 Status: Geschlossen

PD_GET_LOG_MSGS RETURNS SQL22237N WHEN ADMIN LOG NOT EXISTING

Produkt:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problembeschreibung:
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-Zusammenfassung:
**************************************************************** 
* 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.
Lösung
First fixed in DB2 Version 10.1 Fix Pack 5.
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
08.07.2014
15.07.2015
15.07.2015
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
10.1.0.5 FixList