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 IC64038 Status: Geschlossen

FSYNC() ERROR IN DB2DIAG.LOG WHEN BACKING UP TO TAPE DEVICE

Produkt:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problembeschreibung:
db2diag.log reports fsync() error, when a back up is done to a 
tape device The backup is successfull but the error is reported 
in the db2diag.log. 
 
db2diag.log snippet : 
 
2009-05-06-23.26.22.716588-300 E1622483A491       LEVEL: Severe 
(OS) 
PID     : 1368274              TID  : 17137       PROC : db2sysc 
INSTANCE: db2inst2             NODE : 000 
EDUID   : 17137                EDUNAME: db2med.15829.0 (DWPROD) 
FUNCTION: DB2 UDB, oper system services, sqloclose, probe:10 
CALLED  : OS, -, fsync 
OSERR   : EINVAL (22) "Invalid argument" 
DATA #1 : File handle, PD_TYPE_SQO_FILE_HDL, 8 bytes 
0x0700000062FFDC10 : 0000 00FE 0000 0080 
 
The error is fairly benign and does not affect the backup and 
can be ignored.
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* db2 users using tape devices                                 * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* When finishing our write we had been sending a flush signal  * 
* on the close to tape devices.  Some tape devices could not   * 
* handle this signal and generated an error.  See fuller       * 
* description in parent defect and CRM.                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Move up to a version with this fix in it.                    * 
****************************************************************
Local-Fix:
verfügbare FixPacks:
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

Lösung
Problem was first fixed in Version 9.7 FixPak 1
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
22.10.2009
16.03.2010
16.03.2010
Problem behoben ab folgender Versionen (IBM BugInfos)
9.7.
Problem behoben lt. FixList in der Version
9.7.0.1 FixList