|
Problem IC72127
|
Status: Geschlossen |
DB2 CAN ARCHIVE LOGFILES MORE THAN ONCE DURING SHORTAGE OF DISKSPACE IN LOGFILE PATH |
| Produkt: |
DB2 FOR LUW / DB2FORLUW / 910 - 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: |
****************************************************************
* USERS AFFECTED: *
* ALL *
****************************************************************
* PROBLEM DESCRIPTION: *
* See error description above. *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 Version 9.1 Fix Pack 11. *
**************************************************************** |
| Local-Fix: |
|
| verfügbare FixPacks: |
DB2 Version 9.1 Fix Pack 11 for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 12 for Linux, UNIX and Windows
|
| Lösung |
First fixed in DB2 Version 9.1 Fix Pack 11. |
| Workaround |
keiner bekannt / siehe Local-Fix |
| Bug-Verfolgung |
Vorgänger : APAR is sysrouted TO one or more of the following: IC72131 IC74135 IC74189
Nachfolger : |
| Weitere Daten |
Datum - Problem gemeldet :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
| 22.10.2010
08.12.2011
08.12.2011 |
| Problem behoben ab folgender Versionen (IBM BugInfos) |
9.1.FP11
|
| Problem behoben lt. FixList in der Version |
| 9.1.0.11
|
 |
