|
Problem IC90911
|
Status: Closed |
DEACTIVATE EVENT MONITOR MAY CAUSE MISLEADING SQLO_INTRP ERRORS ON NON-CATALOG PARTITION IN DB2DIAG.LOG |
| product: |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 |
| Problem description: |
In DB2 v10.1 multi partition instance (DPF) the deactivation of
an event monitor, e.g. db2 "set event monitor DB2STATISTICS
state 0" may cause misleading SQLO_INTRP error messages in
db2diag.log for non-catalog partitions:
2013-03-01-10.46.35.806371+060 I30043341A676 LEVEL: Error
PID : 60096626 TID : 3600 PROC :
db2sysc 2
INSTANCE: udbxxx NODE : 002 DB : DB2
APPHDL : 1-8815 APPID: *N1.DB2.130301094606
AUTHID : UDBXXX HOSTNAME: db2host
EDUID : 3600 EDUNAME: db2agntp (DB2) 2
FUNCTION: DB2 UDB, database monitor, sqlm_bds_start_monitor_h,
probe:45
CALLED : DB2 UDB, database monitor, sqm_evmon_mgr::start_evmon
RETCODE : ZRC=0x800F0003=-2146500605=SQLO_INTRP "Interrupt.
User
Cancel." DIA8003C The interrupt has been received.
DATA #1 : String, 13 bytes
DB2STATISTICS |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* ALL *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Problem Description above. *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 Version 10.1 Fix Pack 3. *
**************************************************************** |
| Local Fix: |
|
| 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 |
First fixed in DB2 Version 10.1 Fix Pack 3. |
| Workaround |
not known / see Local fix |
| BUG-Tracking |
forerunner : APAR is sysrouted TO one or more of the following: IC92889 IC95215
follow-up : |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 18.03.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
|
 |
| 10.1.0.3
|
|
