|
Problem IC84145
|
Status: Geschlossen |
ERROR IN DB2DIAG.LOG UPON LOW PRIORITY AGENT INTERRUPT IS STILL POSSIBLE WITH FIX FOR APAR IC73608 |
| Produkt: |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 |
| Problembeschreibung: |
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-Zusammenfassung: |
****************************************************************
* 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. |
| verfügbare FixPacks: |
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
|
| Lösung |
First fixed in DB2 version 10 fixpack 1 |
| Workaround |
keiner bekannt / siehe Local-Fix |
| Weitere Daten |
Datum - Problem gemeldet :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
| 12.06.2012
31.10.2012
31.10.2012 |
| Problem behoben ab folgender Versionen (IBM BugInfos) |
|
| Problem behoben lt. FixList in der Version |
| 10.1.0.1
|
 |
| 10.5.0.1
|
|
