|
Problem IC70544
|
Status: Closed |
DATABASE MAY FAIL TO START WHEN FACING DISK FULL ERROR WHILE CREATING A LOG FILE EVEN THOUGH BLK_LOG_DSK_FUL IS SET TO YES. |
| product: |
DB2 FOR LUW / DB2FORLUW / 950 - DB2 |
| Problem description: |
Database may fail to start up when facing disk full error while
creating a log file even though BLK_LOG_DSK_FUL
is set to YES.
db2diag.log file will have messages similar to the following
2010-07-11-07.14.00.991034-240 I47397E414 LEVEL: Error
PID : 17802 TID : 47578863364416PROC :
db2sysc 1
INSTANCE: db2inst1 NODE : 001 DB : SAMPLE
EDUID : 166 EDUNAME: db2loggr (SAMPLE) 1
FUNCTION: DB2 UDB, data protection services, sqlpgifl, probe:50
RETCODE : ZRC=0x850F000C=-2062614516=SQLO_DISK "Disk full."
DIA8312C Disk was full.
2010-07-11-07.14.01.081275-240 E47812E416 LEVEL: Info
PID : 17802 TID : 47578863364416PROC :
db2sysc 1
INSTANCE: db2inst1 NODE : 001 DB : SAMPLE
EDUID : 166 EDUNAME: db2loggr (SAMPLE) 1
FUNCTION: DB2 UDB, data protection services,
sqlpgLoggrInitDelOldLog, probe:1440
DATA #1 : <preformatted>
Cleaning up logs from RenameArchNum 34 to delLimit 52.
2010-07-11-07.14.01.223059-240 I51830E414 LEVEL: Error
PID : 17802 TID : 47578863364416PROC :
db2sysc 1
INSTANCE: db2inst1 NODE : 001 DB : SAMPLE
EDUID : 166 EDUNAME: db2loggr (SAMPLE) 1
FUNCTION: DB2 UDB, data protection services, sqlpgifl, probe:50
RETCODE : ZRC=0x850F000C=-2062614516=SQLO_DISK "Disk full."
DIA8312C Disk was full.
2010-07-11-07.14.01.317457-240 I52245E446 LEVEL: Severe
PID : 17802 TID : 47578863364416PROC :
db2sysc 1
INSTANCE: db2inst1 NODE : 001 DB : SAMPLE
EDUID : 166 EDUNAME: db2loggr (SAMPLE) 1
FUNCTION: DB2 UDB, data protection services,
sqlpgInitRecoverable, probe:8330
RETCODE : ZRC=0x85100084=-2062548860=SQLP_NO_SPACE_FOR_LOG
"Not enough space to create primary logs"
2010-07-11-07.14.01.317905-240 I52692E438 LEVEL: Error
PID : 17802 TID : 47578863364416PROC :
db2sysc 1
INSTANCE: db2inst1 NODE : 001 DB : SAMPLE
EDUID : 166 EDUNAME: db2loggr (SAMPLE) 1
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" |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* All users of DB2 Version 9.5 *
****************************************************************
* PROBLEM DESCRIPTION: *
* Functionality was fixed so that when BLK_LOG_DSK_FUL is set *
* to YES, an error message is returned to the db2diag.log file *
* instead of corrupting the transaction log and crashing the *
* instance. *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 Version 9.5 FP7 or higher. *
**************************************************************** |
| Local Fix: |
Add more disk space to the file system of the active log
directory to successfuly create more log files. |
| available fix packs: |
DB2 Version 9.5 Fix Pack 7 for Linux, UNIX, and Windows
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 |
First fixed in DB2 Version 9.5 Fix Pack 7 |
| Workaround |
not known / see Local fix |
| BUG-Tracking |
forerunner : APAR is sysrouted TO one or more of the following: IC71065
follow-up : |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 12.08.2010
20.12.2010
20.12.2010 |
| Problem solved at the following versions (IBM BugInfos) |
9.5.FP7
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.1.0.7
|
 |
| 9.5.0.7
|
|
