home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Neueste VersionenFixList
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
Haben Sie Probleme? - Kontaktieren Sie uns.
Kostenlos registrieren anmeldung-x26
Kontaktformular kontakt-x26

DB2 - Problembeschreibung

Problem IC80140 Status: Geschlossen

ESTALE FROM READ() OR WRITE() SYSTEM CALL COULD CAUSE LOSS OF DB2AUDIT
RECORD

Produkt:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problembeschreibung:
db2audit archive option will rename/copy/delete the existing 
audit log files. 
If the audit log files are on NFS, deleting of audit log files 
from NFS server may not notify all NFS clients 
on time, so some NFS clients may receive ESTALE error message 
from read() or write() system call, after the file is reopened. 
 
A typical db2diag.log message may look like following: 
 
PID : 407004 TID : 1 PROC : db2bp 
INSTANCE: db2inst1 NODE : 025 
EDUID : 1 
FUNCTION: DB2 UDB, oper system services, sqloread, probe:60 
MESSAGE : ZRC=0x860F0003=-2045837309=SQLO_DERR "disk error 
occurred (DOS)" 
DIA8402C A disk error has occurred. 
CALLED : OS, -, read 
OSERR : ESTALE (52) "Missing file or filesystem" 
DATA #1 : File handle, PD_TYPE_SQO_FILE_HDL, 8 bytes 
File Handle = 4 
File System Block Size = 0 bytes 
File System Type = UNKNOWN 
File Handle Flags : 
Require Sector Align = No 
 
Once db2audit receive ESTALE, it will tolerate the error but 
this will cause loss of audit record. 
 
This APAR allows db2audit to reopen the file and rewrite the 
audit record once it receives ESTALE error message from system 
calls. 
 
Note that users may still see ESTALE errors in db2diag.log. It 
is recommended to use local file systems for audit log files.
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All DB2 V9.7 users.                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* db2audit archive option will rename/copy/delete the existing * 
* audit log files.                                             * 
* If the audit log files are on NFS, deleting of audit log     * 
* files  from NFS server may not notify all NFS clients        * 
* on time, so some NFS clients may receive ESTALE error        * 
* message from read() or write() system call, after the file   * 
* is reopened.                                                 * 
*                                                              * 
* Once db2audit receive ESTALE, it will tolerate the error but * 
* this will cause loss of audit record.                        * 
*                                                              * 
* This APAR fix allows db2audit to reopen the file and rewrite * 
* the audit record once it receives ESTALE error message from  * 
* system                                                       * 
* calls.                                                       * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to V9.7 FP6                                          * 
****************************************************************
Local-Fix:
Use  local file systems for audit log files.
verfügbare FixPacks:
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

Lösung
First fixed in V9.7 FP6.
Workaround
keiner bekannt / siehe Local-Fix
Bug-Verfolgung
Vorgänger  : APAR is sysrouted TO one or more of the following: IC84264 
Nachfolger : 
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
01.12.2011
18.06.2012
18.06.2012
Problem behoben ab folgender Versionen (IBM BugInfos)
9.7.FP6
Problem behoben lt. FixList in der Version
9.7.0.6 FixList