DB2 FOR LUW / DB2FORLUW / 970 - DB2

A low priority agent e.g. one running auto runstats , can be 
interrupted by other agents if this agent is holding locks that 
the higher priority agent requires. 
This behaviour is normal, but it leads to an "error" level 
db2diag.log message 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". 
 
 
This message should be reported in the db2diag.log as an 
Informational message only i.e. only visible at DIAGLEVEL 4 
 
Note, the fix for this apar only partially addresses the 
problem. 
To fully fix the problem, apar IC78736  ( in v9.7 ) also needs 
to be fixed. 
This is scheduled to be fixed in V9.7 Fix Pack 6

**************************************************************** 
* USERS AFFECTED:                                              * 
* all                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* the db2diag.log may contain misleading error messages        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* upgrade to V9.7 Fix Pack 5                                   * 
****************************************************************

none. The message as such is harmless, but it may lead to 
confusion given the high severity level of the message.

DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
 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
 

The problem has first been fixed in DB2 V9.7 Fix Pack 5

keiner bekannt / siehe Local-Fix

Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:

05.04.2011
13.02.2012
12.03.2012

9.7.FP5