|
Problem IT41907
|
Status: Closed |
CRASH RECOVERY OF CIRCULAR LOGGING DATABASE FAILS WITH ADM1601E
|
| product: |
DB2 FOR LUW / DB2FORLUW / B50 - DB2 |
| Problem description: |
Crash recovery of database configured with circular logging
(both LOGARCHMETH1 and LOGARCHMETH2 database
configuration parameters are set to OFF) might fail with the
following message in db2diag.log:
FUNCTION: DB2 UDB, recovery manager,
sqlpshrValidateLogStreamEndPoint, probe:1112
MESSAGE : ADM1601E A recovery or rollforward operation on
database "TESTDB"
cannot continue because of a missing log file
"S0000000.LOG" on
database partition "0" and log stream "0".
This problem only exists in 11.5.5.0 or later version. It only
affects the scenario where the database crashed during
normal shutdown (database deactivation). |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* Users using circular database and crash occurs during *
* shutdown process. *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* UPdate to product version 11.5.8 *
**************************************************************** |
| Local Fix: |
|
| Solution |
|
| Workaround |
****************************************************************
* USERS AFFECTED: *
* Users using circular database and crash occurs during *
* shutdown process. *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* UPdate to product version 11.5.8 *
**************************************************************** |
| Comment |
Fixed in version 11.5.8 |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 31.08.2022
08.09.2022
08.09.2022 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
