|
Problem IC72131
|
Status: Closed |
DB2 CAN ARCHIVE LOGFILES MORE THAN ONCE DURING SHORTAGE OF DISKSPACE IN LOGFILE PATH |
| product: |
DB2 FOR LUW / DB2FORLUW / 950 - DB2 |
| Problem description: |
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 Summary: |
Fix delivered in V9.5 Fixpack 5. |
| Local Fix: |
|
| available fix packs: |
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
|
| Solution |
Fix delivered in V9.5 Fixpack 5. |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 22.10.2010
05.07.2011
05.07.2011 |
| Problem solved at the following versions (IBM BugInfos) |
9.5.FP5
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.5.0.8
|
 |
