DB2 - Problem description
Problem IC78599 | Status: Closed |
ERROR IN DB2DIAG.LOG UPON LOW PRIORITY AGENT INTERRUPT IS STILL POSSIBLE WITH FIX FOR APAR IC73608 | |
product: | |
DB2 FOR LUW / DB2FORLUW / 950 - DB2 | |
Problem description: | |
apar IC73608 fixes a number of scenarios that can lead to misleading error messages in the db2diag.log e.g. 2010-12-09-11.48.41.308869+060 E2370E590 LEVEL: Error PID : 11041 TID : 46913646016 PROC : db2sysc 0 INSTANCE: db2inst1 NODE : 000 DB : SAMPLE APPHDL : 0-51424 APPID: *LOCAL.db2inst1.101209104846 AUTHID : db2inst1 EDUID : 1751 EDUNAME: db2agent (SAMPLE) 0 FUNCTION: DB2 UDB, DRDA Application Server, sqljsTermAgentReply, probe:10 MESSAGE : DIA5000C A DRDA AS token "AGENT TERMINATING" was detected. The diagnostic data returned is (SRVDGN): "SQLERRP:SQL09054 SQLCODE:-1224". However, there were still a few possible scenarios that were not fully fixed by that apar. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * ALL * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description. * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 v9.5 fp9 or later. * **************************************************************** | |
Local Fix: | |
none. The message as such is harmless, but it may lead to confusion given the high severity level of the message. | |
available fix packs: | |
DB2 Version 9.5 Fix Pack 9 for Linux, UNIX, and Windows | |
Solution | |
First fixed in DB2 v9.5 fp9. | |
Workaround | |
not known / see Local fix | |
BUG-Tracking | |
forerunner : APAR is sysrouted TO one or more of the following: IC78736 IC84145 follow-up : | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 09.09.2011 12.03.2012 12.03.2012 |
Problem solved at the following versions (IBM BugInfos) | |
9.5.FP9 | |
Problem solved according to the fixlist(s) of the following version(s) | |
9.5.0.9 |