|
Problem IT19261
|
Status: Closed |
REDUCE DIAGLEVEL FOR PROBE OUTPUT WHEN MON_GET_PKG_CACHE_STMT PROCESSING ON REMOTE NODE GETS SQLKD_INTERRUPT |
| product: |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 |
| Problem description: |
The following errors keep appearing in db2diag.log frequently.
----------------------------------------
2016-07-09-12.10.37.009558-600 I18297A605 LEVEL:
Severe
PID : 3146096 TID : 71482 PROC :
db2sysc 1
INSTANCE: db2mmp NODE : 001 DB : DBMMP
APPHDL : 0-27023 APPID:
10.1.215.104.62407.160709221049
AUTHID : SPDSMCOL HOSTNAME: hon20001
EDUID : 71482 EDUNAME: db2agntp (DBMMP) 1
FUNCTION: DB2 UDB, WLM, sqlrwWlmRPCRouter, probe:20
CALLED : DB2 UDB, WLM, sqlrwWlmRPCRouter
RETCODE : ZRC=0x80580003=-2141716477=SQLKD_INTERRUPT "Mapping
for SQLKF_INTRP"
DIA8003C The interrupt has been received.
2016-07-09-12.10.37.010192-600 I18903A564 LEVEL:
Severe
PID : 3146096 TID : 71482 PROC :
db2sysc 1
INSTANCE: db2mmp NODE : 001 DB : DBMMP
APPHDL : 0-27023 APPID:
10.1.215.104.62407.160709221049
AUTHID : SPDSMCOL HOSTNAME: hon20001
EDUID : 71482 EDUNAME: db2agntp (DBMMP) 1
FUNCTION: DB2 UDB, WLM, sqlrwWlmRPCRouter, probe:500
RETCODE : ZRC=0x80580003=-2141716477=SQLKD_INTERRUPT "Mapping
for SQLKF_INTRP"
DIA8003C The interrupt has been received.
----------------------------------------
No real impact to database, but the error just doesn't stop. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* ALL *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to Db2 10.5 Fix Pack 9 or higher *
**************************************************************** |
| Local Fix: |
No real impact to database, but the error just doesn't stop. |
| Solution |
First fixed in Db2 10.5 Fix Pack 9 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 14.02.2017
29.09.2017
29.09.2017 |
| Problem solved at the following versions (IBM BugInfos) |
9.0.
|
| Problem solved according to the fixlist(s) of the following version(s) |
