Fixes are available
Db2 Version 11.1 Mod4 Fix Pack4 iFix001 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod 4 Fix Pack 4 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod 4 Fix Pack 6 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod 4 Fix Pack 5 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod 4 Fix Pack 7 for Linux, UNIX, and Windows
APAR status
Closed as program error.
Error description
In an automated HADR environment, it is possible that the "db2pd -ha" command reports incorrect primary and secondary node values for a HADR database. Take for example the following HADR database 'HADRDB' which is currently primary on hostA and standby on hostB: db2inst1@hostA: $ db2pd -hadr -db HADRDB | grep HADR_ROLE HADR_ROLE = PRIMARY db2inst1@hostB: $ db2pd -hadr -db HADRDB | grep HADR_ROLE HADR_ROLE = STANDBY It is possible that the "db2pd -ha" command reports conflicting information. Take for example the following snippet from the "db2pd -ha" command which reports hostB as the primary and hostA as the standby: db2inst1@hostA: $ db2pd -ha (...) Resource Name = db2_db2inst1_db2inst1_HADRDB-rs Resource State = Online Resource Type = HADR HADR Primary Instance = db2inst1 HADR Secondary Instance = db2inst1 HADR DB Name = HADRDB HADR Primary Node = hostB HADR Secondary Node = hostA (...) In this case, the information reported by the "db2pd -ha" command is incorrect and can be safely ignored. This issue can happen as a result of a cluster(TSA) initiated takeover and has no impact on database functionality and/or availability.
Local fix
The incorrect primary and secondary HADR node values reported by "db2pd -ha" can be safely ignored.
Problem summary
**************************************************************** * USERS AFFECTED: * * ALL * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to Db2 11.1 Mod 4 Fixpack 4 or higher * ****************************************************************
Problem conclusion
First fixed in Db2 11.1 Mod 4 Fixpack 4
Temporary fix
Comments
APAR Information
APAR number
IT24427
Reported component name
DB2 FOR LUW
Reported component ID
DB2FORLUW
Reported release
B10
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2018-03-19
Closed date
2018-11-27
Last modified date
2018-11-27
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
DB2 FOR LUW
Fixed component ID
DB2FORLUW
Applicable component levels
RB10 PSN
UP
[{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSEPGG","label":"DB2 for Linux- UNIX and Windows"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"11.1","Line of Business":{"code":"LOB10","label":"Data and AI"}}]
Document Information
Modified date:
04 May 2022