Troubleshooting
Problem
Rolling upgrade issue occurs when you do a fixpack upgrade after HADR instance restart.
Symptom
Though fixpack upgrade status shows success on the IBM Cloud Pak System user interface, the actual upgrade happens only on the node where you apply the operation. The upgrade does not happen on the other nodes. Check the Db2 level on the individual nodes to verify this behavior.
Cause
When you restart the HADR instance, the HADR parameters in the maestro export are not restored, and the upgrade happens like a normal instance instead of a rolling HADR upgrade.
Diagnosing The Problem
For example, if you have a topology with two HADR nodes, then verify the Db2 level in both the nodes. The fixpack upgrade happens only on the node where you applied the fixpack, and the other node shows the older level of Db2 fixpack.
Resolving The Problem
Run the following workaround steps first on stand by node and then on the primary node:
Note: This workaround requires downtime till the setup is complete.
1. Apply fix pack upgrade operation on both primary and stand by nodes.
2. Run the following command on both primary and standby to unlock the resource and correct the lssam:
rgreq -o unlock db2_db2inst1_db2inst1_HADRDB-rg 3. If database (HADRDB) is in inactive status, activate it using the following command on both primary and standby:
db2 activate db HADRDBNote: This issue is fixed in IBM Cloud Pak System 2.3.3.0 and Db2 Ptype 1.2.12.0. The workaround is applicable for IBM Cloud Pak System versions lower than 2.3.3.0 and Db2 Ptype versions below 1.2.12.0.
Document Location
Worldwide
[{"Line of Business":{"code":"LOB45","label":"Automation"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSJNNT","label":"IBM Cloud Pak System Software Suite"},"ARM Category":[{"code":"a8m0z000000cwm2AAA","label":"Product Components"}],"ARM Case Number":"","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"2.3.0;2.3.1;2.3.2"}]
Was this topic helpful?
Document Information
Modified date:
31 March 2021
UID
ibm16438403