DB2 - Problem description
Problem IC96298 | Status: Closed |
HEALTH MONITOR FAILS TO DIFFERENTIATE BETWEEN HADR PRIMARY AND SECONADRY AFTER HADR TAKEOVER. | |
product: | |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 | |
Problem description: | |
Health monitor, when configured with HADR, throws errors after HADR takeover. We need to fix the gap between HADR and Hmon, hmon is not working in HADR environment. Health monitor is mot able to pick up the new primary after HADR takeover and it continues to assume the old primary as a primary (which is standby actually). db2acd should indicate that DB is inactive to all plugins hosted within acd. Here are few sample error messages in db2diag.log after take over : ---------------------------- 2010-12-20-18.28.00.812000+060 I6243504F789 LEVEL: Warning PID : 44276 TID : 43516 PROC : db2fmp64.exe INSTANCE: DB2 NODE : 000 EDUID : 43516 FUNCTION: DB2 UDB, Health Monitor, db2HmonEvalBackup, probe:70 CALLED : DB2 UDB, Health Monitor, hmonBkpGetHmonSQLConnection RETCODE : ZRC=0xFFFFFFFF=-1 DATA #1 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes sqlcaid : SQLCA sqlcabc: 136 sqlcode: -1060 sqlerrml: 7 sqlerrmc: DB2HMON sqlerrp : SQLELOST sqlerrd : (1) 0x00000000 (2) 0x00000000 (3) 0x00000000 (4) 0x00000000 (5) 0x00000000 (6) 0x00000000 sqlwarn : (1) (2) (3) (4) (5) (6) (7) (8) (9) (10) (11) sqlstate: 08004 2010-12-20-18.28.00.812000+060 I6244295F346 LEVEL: Event PID : 44276 TID : 43516 PROC : db2fmp64.exe INSTANCE: DB2 NODE : 000 EDUID : 43516 FUNCTION: DB2 UDB, Health Monitor, db2HmonEvalBackup, probe:270 STOP : Automatic Backup: evaluation has finished with errors on database SAMPLE ------------------------------ Hence, the gap between Health monitor and HADR needs to be bridged. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * All users on DB2 V10.1 FixPack 3 or below * **************************************************************** * PROBLEM DESCRIPTION: * * Health monitor, when configured with HADR, throws errors * * after * * HADR takeover. We need to fix the gap between HADR and Hmon, * * * * hmon is not working in HADR environment. Health monitor is * * mot * * able to pick up the new primary after HADR takeover and it * * * * continues to assume the old primary as a primary (which is * * * * standby actually). db2acd should indicate that DB is * * inactive to * * all plugins hosted within acd. * * * * * * * * Here are few sample error messages in db2diag.log after take * * * * over : * * * * * * * * ---------------------------- * * * * 2010-12-20-18.28.00.812000+060 I6243504F789 LEVEL: * * Warning * * PID : 44276 TID : 43516 PROC : * * db2fmp64.exe * * * * INSTANCE: DB2 NODE : 000 * * * * EDUID : 43516 * * FUNCTION: DB2 UDB, Health Monitor, db2HmonEvalBackup, * * probe:70 * * CALLED : DB2 UDB, Health Monitor, * * hmonBkpGetHmonSQLConnection * * RETCODE : ZRC=0xFFFFFFFF=-1 * * * * DATA #1 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes * * * * sqlcaid : SQLCA sqlcabc: 136 sqlcode: -1060 sqlerrml: 7 * * sqlerrmc: DB2HMON * * * * sqlerrp : SQLELOST * * sqlerrd : (1) 0x00000000 (2) 0x00000000 (3) * * * * 0x00000000 * * * * (4) 0x00000000 (5) 0x00000000 (6) * * * * 0x00000000 * * * * sqlwarn : (1) (2) (3) (4) (5) (6) * * * * * * (7) (8) (9) (10) (11) * * * * sqlstate: 08004 * * * * * * * * 2010-12-20-18.28.00.812000+060 I6244295F346 LEVEL: * * Event * * PID : 44276 TID : 43516 PROC : * * db2fmp64.exe * * * * INSTANCE: DB2 NODE : 000 * * * * EDUID : 43516 * * FUNCTION: DB2 UDB, Health Monitor, db2HmonEvalBackup, * * probe:270 * * STOP : Automatic Backup: evaluation has finished with * * errors * * on database SAMPLE * * * * * * * * ------------------------------ * * * * * * * * Hence, the gap between Health monitor and HADR needs to be * * * * bridged. * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 V10.1 Fix Pack 4. * **************************************************************** | |
Local Fix: | |
available fix packs: | |
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows | |
Solution | |
Problem first fixed in DB2 V10.1 Fix Pack 4. | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 26.09.2013 09.06.2014 09.06.2014 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) | |
10.1.0.4 |