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

ADDING RETRY LOGIC WHEN WE ENCOUNTER AN INTERRUPT (EINTR) DURING ACCESS()
CALL TO QP CONFIGURATION FILE IN SQLLIB/CTRL/QP.

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
Getting SQL29007N error message which caused Query Patroller 
(QP) jobs to fail as a result. 
 
For example, you will see the following db2diag.log entries - 
 
2008-07-05-13.42.32.581226-240 I36788637A347      LEVEL: Error 
(OS) 
PID     : 1466706              TID : 1 
FUNCTION: DB2 Common, OSSe, ossPathExists, probe:20 
MESSAGE : ECF=0x9000000F Interrupted by a signal 
CALLED  : OS, -, access                           OSERR: EINTR 
(4) 
ARG  #1 : String, 44 bytes 
/home/db2inst1/sqllib/ctrl/qp/xxxx.cfg 
 
2008-07-05-13.42.33.207592-240 E36788985A569      LEVEL: Error 
(OS) 
PID     : 1466706              TID  : 1           PROC : 
db2agent (PRD1) 17 
INSTANCE: db2inst1             NODE : 017         DB   : xxxx 
APPHDL  : 17-164               APPID: xxxxxxxx.xxxx.xxxxxxxxxxxx 
FUNCTION: DB2 UDB, Query Patroller Server, qcConnection, 
probe:50 
CALLED  : DB2 UDB, Query Patroller Common, connectToQC 
OSERR   : EINTR (4) "Interrupted system call" 
MESSAGE : QP alternate attempt at connection failed (4) 
DATA #1 : File name, 44 bytes 
/home/db2inst1/sqllib/ctrl/qp/xxxx.cfg 
 
This APAR will add retry logic if we do encounter an interrupt 
EINTR during access() call where we try to open the QP 
configuration file.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* Same as ERROR DESCRIPTION                                    * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 9.7 Fix Pack 1                                * 
****************************************************************
Local Fix:
available fix packs:
DB2 Version 9.7 Fix Pack 1 for Linux, UNIX, and Windows
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 9a 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 10 for Linux, UNIX, and Windows

Solution
Fixed in DB2 9.7 Fix Pack 1
Workaround
n/a
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
19.08.2009
23.02.2010
23.02.2010
Problem solved at the following versions (IBM BugInfos)
9.7.FP1
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.1 FixList