|
Problem IT39846
|
Status: Closed |
HADR LOG SHIPPING MIGHT BE STUCK AFTER DB2 UPDATE ACROSS 11.5.6
|
| product: |
DB2 FOR LUW / DB2FORLUW / B50 - DB2 |
| Problem description: |
The problem may occur after update of HADR system from a
downlevel below 11.5.6.0 to an uplevel of 11.5.6.0 or later
releases. In particular, the problem only occurs if the update
was carried out with the following sequence:
1. In downlevel, the standby database was shutdown first.
2. In downlevel, the primary database was shutdown after the
standby database was shutdown.
3. Update both primary and standby to uplevel, activate on both
hosts
4. HADR systems appears to be healthy.
5. More work was performed on the primary database on the
uplevel. However the logs generated were not shipped to the
standby. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* HADR *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to the latest fix pack *
**************************************************************** |
| Local Fix: |
The problem can also be avoided with the following sequence of
actions during update:
1. In downlevel, shutdown primary first, then shutdown
standby
2. Update both primary and standby to uplevel, then activate on
both hosts
or follow the HADR rolling update procedures:
1. Shutdown standby, update standby to uplevel, activate
standby
2. Wait for HADR to reach PEER, then issue graceful takeover on
standby
3. Shutdown old primary / new standby, update to uplevel,
activate new standby |
| Solution |
|
| Workaround |
****************************************************************
* USERS AFFECTED: *
* HADR *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to the latest fix pack *
**************************************************************** |
| Comment |
Problem was first fixed in Db2 11.5.8.0 |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 03.02.2022
11.04.2022
11.04.2022 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
