|
Problem IC78736
|
Status: Closed |
ERROR IN DB2DIAG.LOG UPON LOW PRIORITY AGENT INTERRUPT IS STILL POSSIBLE |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - 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 users on v97fp5 *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 9.7 FP6 or newer fix pack *
**************************************************************** |
| 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.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows
|
| Solution |
Problem First Fixed in DB2 Version 9.7 Fix Pack 6 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 16.09.2011
12.06.2012
05.07.2012 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.FP6
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.6
|
 |
