|
Problem IT41729
|
Status: Closed |
TRANSACTION MAY NOT BE RESOLVED COMPLETELY IF A TABLESPACE IO ERROR IS ENCOUNTERED DURING RECOVERY WITH DB2_ONLINERECOVERY.
|
| product: |
DB2 FOR LUW / DB2FORLUW / B50 - DB2 |
| Problem description: |
This problem only occurs when DB2_ONLINERECOVERY is enabled.
It can impact a recovery (this includes crash recovery,
rollforward,
HADR takeover) if a tablespace IO error was encountered during
the recovery.
If you see the following db2diag.log message you may have been
exposed to this problem.
2022-07-29-12.21.21.736114-420 I173018E626 LEVEL: Info
PID : 11973 TID : 140139896497920 PROC :
db2sysc
INSTANCE: inst1 NODE : 000 DB :
DATABASE
APPHDL : 0-35 APPID: *LOCAL.DB2.220729192120
HOSTNAME: myhost
EDUID : 131 EDUNAME: db2agent (DATABASE)
FUNCTION: DB2 UDB, recovery manager, sqlprudm, probe:14440
MESSAGE : Moving undoSyncPoint due to error on tablespace
DATA #1 : SQLP_TID8, PD_TYPE_SQLP_TID8, 8 bytes
0000000000000351
DATA #2 : unsigned integer, 8 bytes
65708233
DATA #3 : unsigned integer, 8 bytes
65705833 |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* All *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to the latest modification or fix pack. *
**************************************************************** |
| Local Fix: |
Disable DB2_ONLINERECOVERY via "db2set DB2_ONLINERECOVERY=NO". |
| Solution |
|
| Workaround |
****************************************************************
* USERS AFFECTED: *
* All *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to the latest modification or fix pack. *
**************************************************************** |
| Comment |
Problem was first fixed in Db2 11.5.8.0. |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 09.08.2022
18.08.2022
19.08.2022 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
