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 IC72131 Status: Geschlossen

DB2 CAN ARCHIVE LOGFILES MORE THAN ONCE DURING SHORTAGE OF DISKSPACE IN
LOGFILE PATH

Produkt:
DB2 FOR LUW / DB2FORLUW / 950 - DB2
Problembeschreibung:
During shortage of diskspace in the logfile path, the following 
messages in the db2diag.log will trigger DB2 to start archiving 
logfiles, which have already been archived successfully before: 
 
2010-10-18-09.16.30.130488+060 I11252905A366      LEVEL: Error 
PID     : 3002394              TID  : 1           PROC : 
db2loggr (xxxxxx) 0 
INSTANCE: yyyyy             NODE : 000 
FUNCTION: DB2 UDB, data protection services, sqlpgLoggrInit, 
probe:430 
RETCODE : ZRC=0x85100084=-2062548860=SQLP_NO_SPACE_FOR_LOG 
          "Not enough space to create primary logs" 
 
2010-10-18-09.16.30.342768+060 I11253272A155      LEVEL: Error 
PID:3002394 TID:1 NODE:000 Title: SQLP_DBCB 
Dump File:/yyyyy/sqllib/db2dump/30023941.000 
 
2010-10-18-09.16.30.482742+060 I11253428A303      LEVEL: Severe 
PID     : 3002394              TID  : 1           PROC : 
db2loggr (xxxxxx) 0 
INSTANCE: yyyyy             NODE : 000 
FUNCTION: DB2 UDB, data protection services, sqlpgasn, 
probe:4000 
MESSAGE : Logging can not continue due to an error.
Problem-Zusammenfassung:
Fix delivered in V9.5 Fixpack 5.
Local-Fix:
verfügbare FixPacks:
DB2 Version 9.5 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 10 for Linux, UNIX, and Windows

Lösung
Fix delivered in V9.5 Fixpack 5.
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
22.10.2010
05.07.2011
05.07.2011
Problem behoben ab folgender Versionen (IBM BugInfos)
9.5.FP5
Problem behoben lt. FixList in der Version
9.5.0.8 FixList