Latest versionsfixlist
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IC84145 Status: Closed

ERROR IN DB2DIAG.LOG UPON LOW PRIORITY AGENT INTERRUPT IS STILL POSSIBLE
WITH FIX FOR APAR IC73608

product:
DB2 FOR LUW / DB2FORLUW / A10 - 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 version 10 fixpack 1 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 10.1 Fix Pack 1 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 2 for Linux, UNIX, and Windows
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 fixpack 1
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
12.06.2012
31.10.2012
31.10.2012
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.1 FixList
10.5.0.1 FixList