|
Problem IT23073
|
Status: Closed |
CRASH RECOVERY OR A DATABASE ROLLFORWARD OR HADR TAKEOVER MAY FAIL DURING ONLINE RECOVERY PROCESSING. |
| product: |
DB2 FOR LUW / DB2FORLUW / B10 - DB2 |
| Problem description: |
Attempts to start the database after a crash recovery or a
database rollforward or HADR takeover may fail with the
following db2diag.log messages:
2017-10-11-07.08.15.147751-240 I191201858A497 LEVEL: Info
PID : 22085684 TID : 8227 PROC :
db2sysc 0
INSTANCE: svtdbm NODE : 000 DB :
HADRDB
APPHDL : 0-8 APPID: *LOCAL.DB2.171011110641
HOSTNAME: tempsvt01
EDUID : 8227 EDUNAME: db2agent (HADRDB) 0
FUNCTION: DB2 UDB, recovery manager,
sqlprInsertToDeferredUndoChain, probe:250
DATA #1 : <preformatted>
Reserve log space for deferred rollback: 1346290156
Where the value for 'reserved space' is unusually large.
and/or the following message:
2017-10-11-07.08.19.289894-240 I191220787A870 LEVEL: Error
PID : 22085684 TID : 8227 PROC :
db2sysc 0
INSTANCE: svtdbm NODE : 000 DB :
HADRDB
APPHDL : 0-8 APPID: *LOCAL.DB2.171011110641
HOSTNAME: tempsvt01
EDUID : 8227 EDUNAME: db2agent (HADRDB) 0
FUNCTION: DB2 UDB, data protection services,
SQLP_TENTRY::sqlpReserveLogSpace, probe:2020
MESSAGE : ZRC=0x85100009=-2062548983=SQLP_NOSPACE
"Log File has reached its saturation point"
DIA8309C Log file was full.
DATA #1 : String, 56 bytes
TID / myTidhdl / sharedLogSpace / totalReservedLogSpace:
DATA #2 : SQLP_TID8, PD_TYPE_SQLP_TID8, 8 bytes
00000000000AEDCF |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* User that have regeistry variable DB2_ONLINERECOVERY *
* enables. *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Apply DB2 V11.1 M3 FP3. *
**************************************************************** |
| Local Fix: |
Disable online recovery via: db2set DB2_ONLINERECOVERY=NO |
| available fix packs: |
Db2 Version 11.1 Mod2 Fix Pack2 iFix002 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod 3 Fix Pack 3 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod3 Fix Pack3 iFix001 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod3 Fix Pack3 iFix002 for Linux, UNIX, and Windows
|
| Solution |
Fix included in DB2 V11.1 M3 FP3. |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 07.11.2017
15.03.2018
15.03.2018 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
