Internal Health Monitor Error Db2
HEALTH CENTER GUI IS STARTED ON WINDOWS PLATFORM. z/os Fixes are available DB2 Version 9.7 Fix Pack 2 for Linux, UNIX, and Windows DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows Subscribe You can track all active APARs for this component. APAR status Closed as program error. Error description 2009-04-09-06.54.30.020000-240 I76564H519 LEVEL: Error PID : 7100 TID : 7140 PROC : db2syscs.exe INSTANCE: DB2 NODE : 000 APPHDL : 0-440 APPID: *LOCAL.DB2.090409105412 AUTHID : DB2ADMIN EDUID : 7140 EDUNAME: db2agent (instance) 0 FUNCTION: DB2 UDB, Health Monitor, hmonSnapAllTSOnDB, probe:15 MESSAGE : Internal Health monitor error DATA #1 : Hexdump, 4 bytes 0x03714758 : 8C00 0D85 .... 2009-04-09-07.14.13.082000-240 I78570H512 LEVEL: Error PID : 7100 TID : 7140 PROC : db2syscs.exe INSTANCE: DB2 NODE : 000 APPHDL : 0-440 APPID: *LOCAL.DB2.090409105412 AUTHID : DB2ADMIN EDUID : 7140 EDUNAME: db2agent (instance) 0 FUNCTION: DB2 UDB, Health Monitor, hmonSnapTS, probe:15 MESSAGE : Internal Health monitor error DATA #1 : Hexdump, 4 bytes 0x037146E4 : 8C00 0D85 .... Local fix Problem summary **************************************************************** * USERS AFFECTED: * * Users on Windows Platform * **************************************************************** * PROBLEM DESCRIPTION: * * USER MAY GET FOLLOWING ERROR IN DB2DIAG.LOG WHEN THE * * HEALTHCENTER GUI IS STARTED ON WINDOWS * * PLATFORM.2009-04-09-06.54.30.020000-240 I76564H519 * * LEVEL:ErrorPID : 7100 TID : 7140 * * PROC :db2syscs.exeINSTANCE: DB2 NODE : * * 000APPHDL : 0-440 * * APPID:*LOCAL.DB2.090409105412AUTHID : DB2ADMINEDUID : 7140 * * EDUNAME: db2agent (instance) 0FUNCTION: DB2 * * UDB, Health Monitor, hmonSnapAllTSOnDB,probe:15MESSAGE : * * Internal Health monitor errorDATA #1 : Hexdump, 4 * * bytes0x03714758 : 8C00 0D85 * * ....2009-04-09-07.14.13.082000-240 I78570H512 * * LEVEL:ErrorPID : 7100 TID : 7140 * * PROC :db2syscs.exeINSTANCE: DB2 NODE : * * 000APPHDL : 0-440 * * APPID:*LOCAL.DB2.090409105412AUTHID : DB2ADMINEDUID : 7140 * * EDUNAME: db2agent (instance)
sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. Results 1 to 3 of 3 Thread: DB2 Internal Health monitor error Tweet Thread Tools Show Printable Version Subscribe to this Thread… Search Thread Advanced Search Display Linear Mode Switch to Hybrid Mode Switch to Threaded Mode http://www.ibm.com/support/docview.wss?uid=swg1IC66947 12-24-08,05:04 #1 ronenshi View Profile View Forum Posts Registered User Join Date Sep 2004 Posts 35 Unanswered: DB2 Internal Health monitor error Hi, I'm running db2 v9.5 EXP-C on linux AMD64 bit, i've removed an event monitor from the control center and found the following error in the db2diag.log file: 2008-12-24-11.18.59.629280+120 I272821783E1106 LEVEL: Error (OS) PID : 27568 TID : http://www.dbforums.com/showthread.php?1636627-DB2-Internal-Health-monitor-error 1096825184 PROC : db2fmp ( INSTANCE: db2inst NODE : 000 FUNCTION: DB2 Common, OSSe, ossGetDiskInfo, probe:140 MESSAGE : ECF=0x90000017=-1879048169=ECF_FILE_PATH_ACCESS_DENIED Access was denied to a component of the path CALLED : OS, -, statfs OSERR: EACCES (13) DATA #1 : String, 50 bytes /home/db2inst/db2inst/NODE0000/SQL00002/SQLT0000.0 DATA #2 : unsigned integer, 8 bytes 1 CALLSTCK: [0] 0x0000002A97707982 /opt/ibm/db2/V9.5/lib64/libdb2osse.so.1 + 0x1A7982 [1] 0x0000002A97708D93 ossLogSysRC + 0x113 [2] 0x0000002A9771DF7E ossGetDiskInfo + 0xB74 [3] 0x0000002AA7E33B80 snapshot_cntrfs + 0xCB2 [4] 0x0000002A959936D4 sqloInvokeFnArgs + 0xB4C [5] 0x0000002A95E00CEC /opt/ibm/db2/V9.5/lib64/libdb2.so.1 + 0x8A8CEC [6] 0x0000002A95E008A0 sqlerDyload + 0x11E [7] 0x0000002A95DFA032 sqlerFmpListener + 0xA62 [8] 0x0000002A95DFEC98 _Z22sqlerWorkerThreadEntryPv + 0x19A [9] 0x0000003C0B30610A /lib64/tls/libpthread.so.0 + 0x610A 2008-12-24-11.57.03.363534+120 I272903015E525 LEVEL: Error PID : 20341 TID : 183093946720 PROC : db2sysc INSTANCE: db2inst NODE : 000 APPHDL : 0-918 APPID: O19C3F78.A712.01DBC4100345 AUTHID : DB2INST EDUID : 7876 EDUNAME: db2agent (instance) FUNCTION: DB2 UDB, Health Monitor, hmonSnapAddCollectionList, probe:170 MESSAGE : Error reading collection data. DATA #1 : Hexdump, 4 bytes 0x0000002AA13F27AC : 0400 0090 P.S I'm not sure if the error are related to the removal of the event monitor... Thanks, Ronen Reply
IBM which I have tested and appears to resolve the problem (described below). It involves DB2 registry variable DB2ENVLIST, and an environment variable DB2_HMON_DFT_STACK_SZ which appears undocumented. Please scroll to bottom of article for the http://www.ebenner.com/db2dba_blog/?p=84 update. Description of the problem: I have several DB2 version 9 Fixpack 4 instances https://bytes.com/topic/db2/answers/782899-db2-health-monitor-v9-fixpack-4-still-can-big-problem installed on Solaris 10, and have several unresolved and serious Health Monitor-related problems. Many DB2 customers appear to have had similar problems since Health Monitor was introduced. My recommendation as of version 9 Fixpack 4 is that Health Monitor should be left inactivated, and IBM needs to focus much more effort on understanding why internal health HMON is as buggy as it is. My own experiences with Health Monitor occurred January - March 2008, resolved like so many customers by deactivating Health Monitor. Many reports of possibly related issues go back to version 8.1 and 2004. One thing I find suspect is that in many of the Health Monitor APARs (listed below). IBM shows the APAR as resolved, simply by advising customers to internal health monitor deactivate Health Monitor. They didn’t fix the problem at all. Yet general IBM documentation advises the use of the Health Monitor. I believe IBM docs should mention some of the risks involved in activating Health Monitor. I have provided full system configuration, db2support and db2trc output to IBM, and will be happy to provide those details and PMR numbers to any IBM engineers who are interested in tracking the progress of resolving these issues. Note About HMON Instance And Database Capture DB2 documentation in most places states that deactivating Health Monitor only entails setting DBM CFG parameter HEALTH_MON OFF. However that only deactivates database-level health capture associated with the db2hmon process. Health monitoring involves more than just db2hmon. Health capture will continue to restart every two hours via the process db2acd, which captures instance level health information and performs tasks related to automated maintenance. The only way to deactivate db2acd at present is to eliminate fenced memory through this procedure. This is not generally desirable because it interferes with use of the db2expln utility and functions which require fenced memory. Not all the problems I detail here may be related to db2hmon, they may be related to db2acd or other functi
a Question Need help? Post your question and get tips & solutions from a community of 418,571 IT Pros & Developers. It's quick & easy. DB2 Health Monitor v9 fixpack 4 still can be a BIG PROBLEM P: 2 jbenner I have opened a PMR for this with IBM, and am not asking for advice from the DB2 DBA community. I am posting this as an FYI that DB2 Health Monitor, even at the latest version of DB2, still can cause huge problems with slow connect times and heavy resource locking in high concurrency / high transaction volume environments. I have an OLTP with 30-90 transactions per second activity, and start of Health Monitor every 2 hours was crashing our application. We only resolved the situation by setting DBM CFG parameter HEALTH_MON = OFF. Note that other thescripts reports show problems with db2hmon going back to version 8.2. My advice for high transaction volume databases is to not even think about leaving Health Monitor active. (I also see other autonomous features such as STMM giving undesirable effects, so we have deactivated self tuning memory manager as well.). Here is more detail, from the doc I sent IBM on 2008.03.14: ====== Summary We are a DB2 version 9 Fixpack 4 user, 64-bit, running on a Solaris 10 zone on a T2000. The production application is very high transaction volume, 20-90 transactions per second. We have experienced three separate errors with DB2 Health Monitor that have forced us to deactivate it entirely. To summarize they are: 1. In high transaction environment, every time DB2 Health Monitor runs (every 2 hours) causes heavy new connection slowdown and heavy table locking. 2. In one server, DB2 Health Monitor crashes every time it runs with a sqlerRemoveAllIPCforRow violation. When it crashes it causes heavy connection slowdowns and heavy table locking which result in errors for the heavy concurrency user application. 3. DB2 Health Monitor CALL REORGCHK_IX_STATS fails with a SQLCODE “-2306” even though the table exists. Detail Problem #1 Health Monitor causes heavy locking and new connections slowdown We originally opened this PMR to request IBM’s help in determining why our high transactio