home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Latest versionsfixlist
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IC66138 Status: Closed

USER MAY GET FOLLOWING ERROR IN DB2DIAG.LOG WHEN THE HEALTH CENTER GUI
IS STARTED ON WINDOWS PLATFORM.

product:
DB2 FOR LUW / DB2FORLUW / 950 - DB2
Problem 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                                  ....
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* 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) 0FUNCTION: DB2   * 
* UDB, Health Monitor, hmonSnapTS, probe:15MESSAGE : Internal  * 
* Health monitor errorDATA #1 : Hexdump, 4 bytes0x037146E4 :   * 
* 8C00 0D85                                  ....              * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 v9.5 FP6                                      * 
****************************************************************
Local Fix:
available fix packs:
DB2 Version 9.5 Fix Pack 6a for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 10 for Linux, UNIX, and Windows

Solution
Fix will assure not to display these messages in db2diag.log
Workaround
not known / see Local fix
BUG-Tracking
forerunner  : APAR is sysrouted TO one or more of the following: IC66947 IC66948 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
08.02.2010
12.07.2010
12.07.2010
Problem solved at the following versions (IBM BugInfos)
9.5.FP6
Problem solved according to the fixlist(s) of the following version(s)