DB2 - Problembeschreibung
Problem IC62644 | Status: Geschlossen |
ADDING RETRY LOGIC WHEN WE ENCOUNTER AN INTERRUPT (EINTR) DURING ACCESS() CALL TO QP CONFIGURATION FILE IN SQLLIB/CTRL/QP. | |
Produkt: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
Problembeschreibung: | |
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-Zusammenfassung: | |
**************************************************************** * USERS AFFECTED: * * ALL * **************************************************************** * PROBLEM DESCRIPTION: * * Same as ERROR DESCRIPTION * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 9.7 Fix Pack 1 * **************************************************************** | |
Local-Fix: | |
verfügbare FixPacks: | |
DB2 Version 9.7 Fix Pack 1 for Linux, UNIX, and Windows | |
Lösung | |
Fixed in DB2 9.7 Fix Pack 1 | |
Workaround | |
n/a | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 19.08.2009 23.02.2010 23.02.2010 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
9.7.FP1 | |
Problem behoben lt. FixList in der Version | |
9.7.0.1 |