|
Problem IC66319
|
Status: Closed |
IF CRASH RECOVERY FAILS WITH HADR STARTED THE DATABASE WILL STAY ONLINE BUT WILL STILL BE INCONSISTENT RESULTING WITH SQL1015N. |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
In a HADR environment, if crash recovery is interrupted on the
primary server the database will still stay online instead of
shutting down. Since crash recovery has not completed the
database will still be inconistent. So any subsequent access to
the database will return SQL1015N. Also, the following
db2diag.log message will be returned indicating that the Standby
DB is ahead of the Primary DB:
YYYY-MM-DD-HH.MM.SS.NNNNNN LEVEL: Error
PID : <pid> TID : <tid> : db2sysc 0
INSTANCE: <instance> NODE : 000
EDUID : <eduid> EDUNAME: db2hadrp (<db>) 0
FUNCTION: DB2 UDB, High Availability Disaster Recovery, hdrEduP,
probe:20485
MESSAGE : ADM12500E The HADR standby database cannot be made
consistent with he primary database. The log stream of the
standby database is incompatible with that of the primary
database. To use this database as a standby, it must be
recreated from a backup image or split mirror of the primary
database. |
| Problem Summary: |
USERS AFFECTED: All
PROBLEM DESCRIPTION: please refer to the ERROR DESCRIPTION.
PROBLEM SUMMARY: please refer to the ERROR DESCRIPTION. |
| Local Fix: |
1. Do not interrupt crash recovery from completing. This can
be achieved by limiting remote access to the database if crash
recovery is needed. Or by explicitly activating the database so
that early remote connection termination will not interrupt the
crash recovery process.
2. If crash recovery has already been interrupted then you will
need to stop the instance using the force option. Upon
restarting the instance explicitly start the database so that
crash recovery can complete successfully. |
| available fix packs: |
DB2 Version 9.7 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows
|
| Solution |
Problem first fixed in FixPack 2 (s100514.) |
| Workaround |
see LOCAL FIX |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 17.02.2010
22.07.2010
22.07.2010 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.2
|
 |
