IBM Support

IC86007: "INTERNAL HEALTH MONITOR ERROR " ERRORS DUMPED IN THE DB2DIAG.LOG FOR "DB2.MAX_SORT_PRIVMEM_UTIL" HEALTH INDICATOR

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • Following errors in the db2diag.log after few days, once the
    instance is re started.
    
    2011-06-07-11.07.18.859000+120 I110874F409        LEVEL: Severe
    
    PID     : 3380                 TID  : 2628        PROC :
    db2fmp64.exe
    INSTANCE: DB2INST1               NODE : 000
    
    EDUID   : 2628
    
    FUNCTION: DB2 UDB, Health Monitor, HealthIndicator::getAlertCfg,
    
    probe:30
    
    MESSAGE : Internal Health monitor error
    
    DATA #1 : Hexdump, 4 bytes
    
    0x000000000799EC64 : 0100 0000
    ....
    
    
    2011-06-07-11.07.18.884000+120 I111285F419        LEVEL: Severe
    
    PID     : 3380                 TID  : 2628        PROC :
    db2fmp64.exe
    INSTANCE: DB2INST1               NODE : 000
    
    EDUID   : 2628
    
    FUNCTION: DB2 UDB, Health Monitor, HealthIndicator::getAlertCfg,
    
    probe:40
    
    MESSAGE : Internal Health monitor error
    
    DATA #1 : Hexdump, 13 bytes
    
    0x0000000001BA63B0 : 4442 325F 3031 0020 002D 0020 30
    DB2INST1.
    .-. 0
    
    
    
    2011-06-07-11.07.18.884000+120 I111706F497        LEVEL: Severe
    
    PID     : 3380                 TID  : 2628        PROC :
    db2fmp64.exe
    INSTANCE: DB2INST1               NODE : 000
    
    EDUID   : 2628
    
    FUNCTION: DB2 UDB, Health Monitor, HealthIndicator::getAlertCfg,
    
    probe:50
    
    MESSAGE : Internal Health monitor error
    
    DATA #1 : Hexdump, 25 bytes
    
    0x0000000001BA19C0 : 6462 322E 6D61 785F 736F 7274 5F70 7269
    db2.max_sort_pri
    
    0x0000000001BA19D0 : 766D 656D 5F75 7469 6C
    vmem_util
    
    The health indicator db2.max_sort_privmem_util has been
    deprecated since version 8010200 i.e. V8.2, but still exists in
    the HealthRulesV82.reg file, and hence the error.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * ALL                                                          *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * See Error Description                                        *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Upgrade to V97Fp10                                           *
    ****************************************************************
    

Problem conclusion

  • Fixed in V97FP10
    

Temporary fix

Comments

APAR Information

  • APAR number

    IC86007

  • Reported component name

    DB2 FOR LUW

  • Reported component ID

    DB2FORLUW

  • Reported release

    970

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2012-08-21

  • Closed date

    2014-10-06

  • Last modified date

    2016-03-08

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

    IC91746 IC91911 IC96302 IC96353

Fix information

  • Fixed component name

    DB2 FOR LUW

  • Fixed component ID

    DB2FORLUW

Applicable component levels

  • R970 PSY

       UP



Document information

More support for: DB2 for Linux, UNIX and Windows

Software version: 9.7

Reference #: IC86007

Modified date: 08 March 2016