|
Problem IT39287
|
Status: Closed |
HADR STANDBY MAY TAKE LONGER THAN NORMAL TO REACH PEER STATE ON ACTIVATION
|
| product: |
DB2 FOR LUW / DB2FORLUW / B50 - DB2 |
| Problem description: |
An HADR standby when activated may need to perform remote
catch-up. The standby may ask the primary for log files or the
standby will try to retrieve from the archives. It may be
possible under certain circumstances that the standby cannot
receive the log file from the primary nor retrieve the log file
from the archives. In this case, the standby will not achieve
PEER state in a timely fashion. After some amount of time, the
problem will resolve itself and PEER state will be achieved.
If this were to happen, on the primary one may see messages in
the Db2 diagnostics log as follows:
EDUID : 305 EDUNAME: db2hadrp.0.2 (HADRDB)
FUNCTION: DB2 UDB, High Availability Disaster Recovery,
hdrEdu::hdrEduP, probe:20445
DATA #1 :
Remote catchup starts at lso 249353377.
Using page start lso 249353377.
EDUID : 270 EDUNAME: db2lfr.0 (HADRDB)
FUNCTION: DB2 UDB, data protection services,
sqlpgRetrieveLookup, probe:500
DATA #1 :
Log 12 on log stream 0 is in the array but is still being
retrieved. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* All *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to Db2 Version 11.5.7.1. *
**************************************************************** |
| Local Fix: |
After some amount of time, the problem will resolve itself and
PEER state will be achieved. |
| Solution |
|
| Workaround |
****************************************************************
* USERS AFFECTED: *
* All *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to Db2 Version 11.5.7.1. *
**************************************************************** |
| Comment |
Problem was first fixed in Db2 Version 11.5.7.1. |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 01.12.2021
06.12.2021
06.12.2021 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
