| Latest versions | fixlist |
| 11.1.0.7 |
 |
| 10.5.0.9 |
|
| 10.1.0.6 |
|
| 9.8.0.5 |
|
| 9.7.0.11 |
|
| 9.5.0.10 |
|
| 9.1.0.12 |
|
| Have problems? - contact us. | |
| Register for free |
|
| Contact form |
|
DB2 - Problem description
| Problem IT42040 | Status: Closed |
HANG DURING CRASH RECOVERY WAITING FOR LOG ARCHIVE WITH MIRRORLOGPATH AND BLK_LOG_DSK_FUL ENABLED | |
| product: | |
DB2 FOR LUW / DB2FORLUW / B10 - DB2 | |
| Problem description: | |
Database is configured with log archiving (LOGARCHMETH1),
MIRRORLOGPATH and BLK_LOG_DSK_FUL enabled.
The database starts crash recovery but crash recovery never ends
and seems to hang.
During crash recovery, the db2diag.log has:
2022-09-11-11.21.54.927643+060 I4902563A573 LEVEL: Info
PID : 50725176 TID : 22875 PROC :
db2sysc 0
INSTANCE: inst NODE : 000 DB : DBNAME
HOSTNAME: host
EDUID : 22875 EDUNAME: db2loggw (DBNAME) 0
FUNCTION: DB2 UDB, data protection services, sqlpgOpenLogExtent,
probe:850
MESSAGE : ZRC=0x860F000A=-2045837302=SQLO_FNEX "File not found."
DIA8411C A file "" could not be found.
DATA #1 :
Error opening database log
/db2/DBNAME/log_dir2/NODE0000/LOGSTREAM0000/S0545919.LOG.
2022-09-11-11.21.54.928793+060 I4903137A502 LEVEL: Info
PID : 50725176 TID : 22875 PROC :
db2sysc 0
INSTANCE: inst NODE : 000 DB : DBNAME
HOSTNAME: host
EDUID : 22875 EDUNAME: db2loggw (DBNAME) 0
FUNCTION: DB2 UDB, data protection services, sqlpgStartMfhEntry,
probe:7240
DATA #1 :
Dual log array is full. Checking if any new logs have been
archived.
end: 545889, lowestUnarchivedExtNum: 544658, path: 10
2022-09-11-11.21.54.929222+060 I4903640A406 LEVEL: Info
PID : 50725176 TID : 22875 PROC :
db2sysc 0
INSTANCE: inst NODE : 000 DB : DBNAME
HOSTNAME: host
EDUID : 22875 EDUNAME: db2loggw (DBNAME) 0
FUNCTION: DB2 UDB, data protection services, sqlpgStartMfhEntry,
probe:7280
MESSAGE : Wait 5 minutes for log file to be archived
The "Wait 5 minutes for log file to be archived" message is
repeated every 5 minutes, but there is no log archiving
initiated. | |
| Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * Users with MIRRORLOGPATH, BLK_LOG_DSK_FUL and LOGARCHMETH1 * * enabled * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to latest CSB level of Db2 v11.5.7.0 or later. * **************************************************************** | |
| Local Fix: | |
Set BLK_LOG_DSK_FUL database configuration to OFF. | |
| Solution | |
| Workaround | |
**************************************************************** * USERS AFFECTED: * * Users with MIRRORLOGPATH, BLK_LOG_DSK_FUL and LOGARCHMETH1 * * enabled * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to latest CSB level of Db2 v11.5.7.0 or later. * **************************************************************** | |
| Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 14.09.2022 14.09.2022 14.09.2022 |
| Problem solved at the following versions (IBM BugInfos) | |
| Problem solved according to the fixlist(s) of the following version(s) | |
