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 IC70039 Status: Closed

DB2 OCCASIONALLY REPORTS FILE SHARING ERROR

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
The file sharing error may be reported in db2diag.log as 
follows: 
 
2010-03-20-00.32.08.610456-240 E2411252A945       LEVEL: Error 
(OS) 
PID     : 235432               TID  : 3857        PROC : db2sysc 
8 
INSTANCE: db2apdw              NODE : 008         DB   : 
XXXXXXXXX 
EDUID   : 3857                 EDUNAME: db2loggr (DWDB) 8 
FUNCTION: DB2 UDB, oper system services, sqloopenp, probe:80 
MESSAGE : ZRC=0x870F0016=-2029060074=SQLO_SHAR "File sharing 
violation." DIA8519C A file sharing violation has occurred, 
filename was "". 
CALLED  : OS, -, open 
OSERR   : ETXTBSY (26) "Text file busy" 
 
 
The error may be observed during log file archiving, data 
movement, and others file operations when DB2 attempts to open 
the file in question. The end result is that the file operation 
will fail. 
 
This error is typically caused when a software component outside 
of DB2 accesses database directories and files. These software 
components may include file system backup, disk utilities and 
anti-virus programs among others. No software other than DB2 
should be accessing files under database directory. This may not 
be feasible all the times. To help mitigate this condition, DB2 
will slightly increase the retry interval for file open 
operation, thereby llowing the conflict situation to 
potentially expire.
Problem Summary:
APAR fix was provided in Fixpack 4.
Local Fix:
Users should work with their system administrator or IT team to 
determine which component of their system is accessing DB2 
files. The method of determination will depend on the platform. 
For example, on Linux users may employ fuser and lsof commands. 
On AIX, in addition to the former, the OS tracing mechanism or 
security audit may help. On Windows, file access auditing tool 
may be of use.
available fix packs:
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 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

Solution
To help mitigate this condition, the retry interval for file 
open operation was increased, thereby allowing the conflict 
situation to potentially expire.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
21.07.2010
09.05.2011
09.05.2011
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.4 FixList
This site uses cookies to make it easier for us to provide you with our services. By using our site you agree to the use of cookies.