|
Problem IT31986
|
Status: Closed |
CLUSTER INITIATED FAILOVER OF THE HADR DATABASE MAY TIMEOUT IF AIBM.RECOVERYRM MASTER SWAP OCCURS IN PARALLEL
|
| product: |
DB2 FOR LUW / DB2FORLUW / B10 - DB2 |
| Problem description: |
This APAR is only applicable to automated HADR/TSA environments
setup via the db2haicu utility.
In the event of a cluster initiated takeover from host A to host
B, the failover request may "hang" and eventually timeout if the
IBM.RecoveryRM master role is simultaneously failing over to the
destination host (host B).
If this issue is encountered, HADR monitor and start commands
will timeout on the destination host (host B). |
| Problem Summary: |
|
| Local Fix: |
|
| Solution |
|
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 25.02.2020
18.02.2021
18.02.2021 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
