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 IC84385 Status: Closed

THE SQLOWAITINTERRUPT SUFFERS FROM 6 OSERR CAUSING DB2DIAG.LOG TO BE FILLED
WITH 'INVALID HANDLE' ERRORS.

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
The issue can occur when TM is using non-zero value of 
xa_timeout, if so the following message occurs very often in 
db2diag.log: 
 
2012-11-28-10.22.31.240000+120 E8567247F441       LEVEL: Error 
(OS) 
PID     : 1580                 TID  : 999         PROC : 
db2syscs.exe 
INSTANCE: DB2INST1             NODE : 000 
APPHDL  : 0-8 
EDUID   : 954                  EDUNAME: db2resync 
FUNCTION: DB2 UDB, oper system services, sqloWaitInterrupt, 
probe:10 
MESSAGE : ZRC=0x83000006=-2097151994 
CALLED  : OS, -, unspecified_system_function 
OSERR   : 6 "The handle is invalid." 
 
The error indicates that there's something wrong with 
IPC(Inter-Process Communication), however in the scenario the 
error is harmless. 
 
A characteristic flow is present when gathering db2trc flw 
traces, like an example below: 
 
| | sqljcSend exit 
| | sqljrRecv entry [eduid 999 eduname db2agent] 
 
... 
 
| | | | | | | sqloWaitInterrupt SYSTEM ERROR [probe 10] [ ZRC = 
0x83000006 = -2097151994] 
| | | | | | | | | | sqloclose entry [eduid 999 eduname db2agent] 
| | | | | | | | | | sqloclose exit 
| | | | | | | | | pdLogInternal exit 
| | | | | | | | pdLogSysRC exit 
| | | | | | | sqloWaitInterrupt exit [rc = 0x83000006 = 
-2097151994] 
| | | | | | sqloSSemP exit [rc = 0x83000006 = -2097151994]
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* Users of DB2 for Linux, UNIX and Windows                     * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* Problem was first fixed in Version 9.7 Fix Pack 7            * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* No local fix available.                                      * 
****************************************************************
Local Fix:
available fix packs:
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
See Error Description.
Workaround
not known / see Local fix
BUG-Tracking
forerunner  : APAR is sysrouted TO one or more of the following: IC88317 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
14.06.2012
02.01.2014
02.01.2014
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.7 FixList