DB2 - Problembeschreibung
Problem IC84264 | Status: Geschlossen |
ESTALE FROM READ() OR WRITE() SYSTEM CALL COULD CAUSE LOSS OF DB2AUDIT RECORD | |
Produkt: | |
DB2 FOR LUW / DB2FORLUW / A10 - 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 on LUW V10 users. * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 V10 FixPack 1. * **************************************************************** | |
Local-Fix: | |
Use local file systems for audit log files. | |
verfügbare FixPacks: | |
DB2 Version 10.1 Fix Pack 1 for Linux, UNIX, and Windows | |
Lösung | |
Fixed in DB2 V10 FixPack 1. | |
Workaround | |
keiner bekannt / siehe Local-Fix | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 13.06.2012 29.01.2013 29.01.2013 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
Problem behoben lt. FixList in der Version | |
10.1.0.1 | |
10.5.0.1 |