home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
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 IC66602 Status: Closed

UNNECESSARY DB2DIAG.LOG MESSAGES MAY GET LOGGED DURING INTERRUPTS

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
Interrupts (internal or user driven) can result in some extra 
db2diag logging.  These messages are flagged as 'ERROR' but they 
are not an error when the root cause is an Interrupt.  If the 
cause is an Interrupt there is no concern and the messages 
should be ignored.  This APAR eliminates these db2diag.log 
messages. 
 
Some Examples: 
 
2010-01-25-17.09.49.134278-360 I6181181A8313 LEVEL: Error 
PID : 1183844 TID : 7492 PROC : db2sysc 6 
INSTANCE: dmdiadm1 NODE : 006 DB : DEV103 
APPHDL : 0-297 APPID: *N0.dmdiadm1.100125230808 
AUTHID : ESHIRLE 
EDUID : 7492 EDUNAME: db2agntp (UHCBET01) 6 
FUNCTION: DB2 UDB, data management, sqldFetchDictionary, 
probe:3112 
MESSAGE : ZRC=0x80040003=-2147221501=SQLD_INTRP "USER INTERRUPT 
DETECTED" 
DIA8003C The interrupt has been received. 
DATA #1 : String, 24 bytes 
Fetch Dictionary Failed. 
DATA #2 : String, 12 bytes 
fetch Phase: 
DATA #3 : unsigned integer, 4 bytes 
0 
DATA #4 : String, 14 bytes 
Fetch Options: 
DATA #5 : Hex integer, 4 bytes 
0x00000003 
DATA #6 : String, 8 bytes 
RecType: 
DATA #7 : unsigned integer, 4 bytes 
0 
DATA #8 : String, 6 bytes 
dmsWA: 
DATA #9 : Hexdump, 1416 bytes 
0x0700000008FFC370 : 0000 0000 0000 0000 0000 0000 0000 0000 
................ 
0x0700000008FFC380 : 0000 0000 2010 0000 0000 0000 0000 0000 
.... ........... 
:: 
:: 
0x0700000008FFC8E0 : 0700 0000 08FF CA30 0700 0000 7177 F280 
.......0....qw.. 
0x0700000008FFC8F0 : 0000 0036 4DF4 0333 ...6M..3 
DATA #10: String, 7 bytes 
recptr: 
DATA #11: Hexdump, 2 bytes 
0x070000002B4BBA44 : 0000 .. 
DATA #12: String, 6 bytes 
recid: 
DATA #13: zrid, PD_TYPE_SQLZ_RID, 8 bytes 
Page=197; Slot=1; Dpid=0 
 
2010-01-25-17.09.49.608662-360 I6189495A514 LEVEL: Error 
PID : 1183844 TID : 7492 PROC : db2sysc 6 
INSTANCE: dmdiadm1 NODE : 006 DB : DEV103 
APPHDL : 0-297 APPID: *N0.dmdiadm1.100125230808 
AUTHID : ESHIRLE 
EDUID : 7492 EDUNAME: db2agntp (UHCBET01) 6 
FUNCTION: DB2 UDB, trace services, sqlt_logerr_string (secondary 
logging fu, probe:0 
MESSAGE : SQLD_TCB: 
DATA #1 : String, 41 bytes 
Perm Table(163:4)=TBSPACEID=163.TABLEID=4 
 
2010-01-25-17.09.49.626623-360 I6190010A170 LEVEL: Error 
PID:1183844 TID:7492 NODE:006 Title: SQLD_TCB 
Dump File:/dmdiadm1/sqllib/db2dump/1183844.7492.006.dump.bin
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* all                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* Interrupts (internal or user driven) can result in some      * 
* extra                                                        * 
* db2diag logging.  These messages are flagged as 'ERROR' but  * 
* they                                                         * 
* are not an error when the root cause is an Interrupt.  If    * 
* the                                                          * 
* cause is an Interrupt there is no concern and the messages   * 
*                                                              * 
* should be ignored.  This APAR eliminates these db2diag.log   * 
*                                                              * 
* messages.                                                    * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 version 9.7.002                               * 
****************************************************************
Local Fix:
Ignore these extraneous msgs when root cause is an Interrupt.
available fix packs:
DB2 Version 9.7 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
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 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows

Solution
These DB2diag messages have been removed for the Interrupt case. 
 First fixed in DB2 version 9.7.002
Workaround
not known / see Local fix
BUG-Tracking
forerunner  : APAR is sysrouted TO one or more of the following: IC66852 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
23.02.2010
30.06.2010
30.06.2010
Problem solved at the following versions (IBM BugInfos)
9.7.002
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.2 FixList