DB2 - Problem description
Problem IT16568 | Status: Closed |
ZRC=0X80580003=-2141716477=SQLKD_INTERRUPT "MAPPING FOR SQLKF_INTRP" DIA8003C APPEARS IN DB2DIAG.LOG REPEATEDLY | |
product: | |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 | |
Problem description: | |
The following errors appear in db2diag.log repeatedly. ---------------------------------------------------------------- ---------------- 2016-07-09-15.10.37.009558-600 I18297A605 LEVEL: Severe PID : 3146096 TID : 71482 PROC : db2sysc 1 INSTANCE: db2inst1 NODE : 001 DB : DBSERV APPHDL : 0-27023 APPID: 10.1.215.114.62407.160709211040 AUTHID : SPDSMCOL HOSTNAME: db2host EDUID : 71482 EDUNAME: db2agntp (DBSERV) 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-15.10.37.010192-600 I18903A564 LEVEL: Severe PID : 3146096 TID : 71482 PROC : db2sysc 1 INSTANCE: db2inst1 NODE : 001 DB : DBSERV APPHDL : 0-27023 APPID: 10.1.215.114.62407.160709211040 AUTHID : SPDSMCOL HOSTNAME: db2host EDUID : 71482 EDUNAME: db2agntp (DBSERV) 1 FUNCTION: DB2 UDB, WLM, sqlrwWlmRPCRouter, probe:500 RETCODE : ZRC=0x80580003=-2141716477=SQLKD_INTERRUPT "Mapping for SQLKF_INTRP" DIA8003C The interrupt has been received. ---------------------------------------------------------------- ---------------- There is no real impact to database, except the error message doesn't stop. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * ALL * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * See SYSROUTE APARs to see where this APAR is addressed * **************************************************************** | |
Local Fix: | |
N/A | |
Solution | |
Workaround | |
not known / see Local fix | |
BUG-Tracking | |
forerunner : follow-up : IT20870 | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 11.08.2016 09.05.2017 09.05.2017 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) |