IC70039: DB2 OCCASIONALLY REPORTS FILE SHARING ERROR

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

APAR status

• Closed as program error.

Error 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.
  

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.
  

Problem summary

• APAR fix was provided in Fixpack 4.
  

Problem conclusion

• To help mitigate this condition, the retry interval for file
  open operation was increased, thereby allowing the conflict
  situation to potentially expire.
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

  IZ80732

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  DB2 FOR LUW

• Fixed component ID

  DB2FORLUW

Applicable component levels

• R970 PSY

     UP