home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
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 IC64038 Status: Closed

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

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
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 Summary:
**************************************************************** 
* 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:
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
Problem was first fixed in Version 9.7 FixPak 1
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
22.10.2009
16.03.2010
16.03.2010
Problem solved at the following versions (IBM BugInfos)
9.7.
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.1 FixList