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 IC91755 Status: Closed

HMONSQLCONNECT, PROBE:100 ERROR WAS OCCURRED.

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
hmonSQLConnect, probe:100 error was occurred. 
db2diag.log was recorded as below. 
 
2012-07-15-14.26.07.346109+540 I7693633E291 LEVEL: Severe 
PID     : 18140                TID  : 1094363456   PROC : db2acd 
INSTANCE: db2inst1             NODE : 000 
FUNCTION: DB2 UDB, Health Monitor, hmonSQLConnect, probe:100 
MESSAGE : SQLGetCurrentCtx error sqlRC=[0] sqlcode[-1442] 
 
hmonSQLConnect is using freed context, so hmonSQLConnect is 
recording this entry.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 UDB version 10.1 fixpack 3.                   * 
****************************************************************
Local Fix:
Restart instance then activate database.
available fix packs:
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows

Solution
Problem was first fixed in DB2 UDB Version 10.1 FixPack 3.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
22.04.2013
08.10.2013
08.10.2013
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.3 FixList
10.1.0.3 FixList