|
Problem IC66864
|
Status: Closed |
HEALTH MONITOR FAILS WITH RC=-1 ON HMONSQLDISCONNECT() |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
Health monitor fails on hmonDisconnect() with RC=-1 if we have
AUTOCOMMIT turned off in db2cli.ini
db2cli.ini
[DBNAME]
AutoCommit=0
The following messages could be observed in the db2diag.log
2000-00-00-00.00.00.000000+120 I39325H346 LEVEL: Severe
PID : 3196 TID : 2096 PROC :
db2fmp.exe
INSTANCE: DB2 NODE : 000
APPID : *LOCAL.DB2.00000000000
EDUID : 2096
FUNCTION: DB2 UDB, Health Monitor, hmonSQLDisconnect, probe:10
MESSAGE : SQLDisconnect error sqlRC=[-1] sqlcode=[0]
2000-00-00-00.00.00.000000+120 I39673H367 LEVEL: Severe
PID : 0000 TID : 0000 PROC :
db2fmp.exe
INSTANCE: DB2 NODE : 000
APPID : *LOCAL.DB2.00000000000
EDUID : 0000
FUNCTION: DB2 UDB, base sys utilities, sqleFreeCtx, probe:50
RETCODE : ZRC=0x8805006B=-2012938133=SQLE_ZRC_CTX_INUSE "Context
is in use" |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* All *
****************************************************************
* PROBLEM DESCRIPTION: *
* Health monitor fails on hmonDisconnect() with RC=-1 if *
* wehaveAUTOCOMMIT turned off in *
* db2cli.inidb2cli.ini[DBNAME]AutoCommit=0The following *
* messages could be observed in the *
* db2diag.log2000-00-00-00.00.00.000000+120 I39325H346 *
* LEVEL:SeverePID : 3196 TID : 2096 *
* PROC :db2fmp.exeINSTANCE: DB2 NODE : *
* 000APPID : *LOCAL.DB2.00000000000EDUID : 2096FUNCTION: DB2 *
* UDB, Health Monitor, hmonSQLDisconnect,probe:10MESSAGE : *
* SQLDisconnect error sqlRC=[-1] *
* sqlcode=[0]2000-00-00-00.00.00.000000+120 I39673H367 *
* LEVEL:SeverePID : 0000 TID : 0000 *
* PROC :db2fmp.exeINSTANCE: DB2 NODE : *
* 000APPID : *LOCAL.DB2.00000000000EDUID : 0000FUNCTION: DB2 *
* UDB, base sys utilities, sqleFreeCtx, probe:50RETCODE : *
* ZRC=0x8805006B=-2012938133=SQLE_ZRC_CTX_INUSE"Contextis in *
* use" *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 Version 9.7 Fix Pack 2 *
**************************************************************** |
| Local Fix: |
|
| available fix packs: |
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 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 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
|
| Solution |
Problem was first fixed in Version 9.7 Fix Pack 2 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 04.03.2010
30.06.2010
30.06.2010 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.FP2
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.2
|
 |
