|
Problem IT38900
|
Status: Closed |
AFTER REACTIVATING A CRASHED STANDBY DATABASE, SOME READ ON STANDBY OPERATIONS MIGHT GET BACK SQL0901
|
| product: |
DB2 FOR LUW / DB2FORLUW / B50 - DB2 |
| Problem description: |
After reactivating a crashed standby database, some Read on
Standby operations get back SQL0901.
See following diag message:
2021-08-05-01.25.39.978023-240 I3661914E1076 LEVEL:
Severe
PID : 799088 TID : 140735642792224PROC :
db2sysc 0
INSTANCE: db2inst1 NODE : 000 DB :
HADRDB
APPHDL : 0-2499 APPID:
9.30.220.90.37992.210805054636
AUTHID : DB2INST1 HOSTNAME: standby_host
EDUID : 30 EDUNAME: db2agent (HADRDB) 0
FUNCTION: DB2 UDB, relation data serv, sqlrr_dump_ffdc,
probe:250
MESSAGE : ZRC=0x82040001=-2113667071=SQLD_NONSEVERE_PRGERR
"non-severe dms programming error"
DIA8532C An internal processing error has occurred.
DATA #1 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes
sqlcaid : SQLCA sqlcabc: 136 sqlcode: -901 sqlerrml: 31
This is because the data they are accessing are not replayed
yet.
The value shown in the following diag message is less than the
actual replay position before standby crashes.
2021-08-05-01.25.36.428089-240 I3054814E699 LEVEL:
Warning
PID : 799088 TID : 140735676346656PROC :
db2sysc 0
INSTANCE:db2inst1 NODE : 000 DB :
HADRDB
APPHDL : 0-2239 APPID:
9.30.220.90.37152.210805054358
AUTHID : DB2INST1 HOSTNAME: standby_host
EDUID : 22 EDUNAME: db2agent (HADRDB) 0
FUNCTION: DB2 UDB, High Availability Disaster Recovery,
hdrCheckDb, probe:18300
DATA #1 :
Connection is not allowed until replay position
(STANDBY_REPLAY_LOG_POS from "db2pd -hadr") reaches previous
activation's highest replay position: Lso 6982228760
(corresponding Lsn 000000000238671F)
It's possible to verify this by taking the looking at
lastExtNeededForRecovery field when standby reactivates.
The Lsn/Lso values do not fall into lastExtNeededForRecovery log
file, but the log file before it. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* HADR ROS users *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Update to DB2 11.5 Mod 7 *
**************************************************************** |
| Local Fix: |
Retry ROS connection after replay has passed replay position of
last activation. |
| Solution |
|
| Workaround |
****************************************************************
* USERS AFFECTED: *
* HADR ROS users *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Update to DB2 11.5 Mod 7 *
**************************************************************** |
| Comment |
Problem was first fixed in DB2 11.5 Mod 7 |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 29.10.2021
29.11.2021
29.11.2021 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
