IZ80732: DB2 OCCASIONALLY REPORTS FILE SHARING ERROR

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

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:
    
    - Linux/UNIX: users may employ fuser and lsof commands.
    
    - AIX: same as above, plus the OS tracing mechanism or
      security audit may help.
    
    - Windows: file access auditing tool may be of use.
    

Problem summary

  • APAR fix was provided in Fixpack 7.
    

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 number

    IZ80732

  • Reported component name

    DB2 UDB ESE AIX

  • Reported component ID

    5765F4100

  • Reported release

    950

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2010-07-21

  • Closed date

    2010-12-22

  • Last modified date

    2010-12-24

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

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

    IC70039 IC71282

Fix information

  • Fixed component name

    DB2 UDB ESE AIX

  • Fixed component ID

    5765F4100

Applicable component levels

  • R950 PSY

       UP



Rate this page:

(0 users)Average rating

Document information


More support for:

DB2 for Linux, UNIX and Windows

Software version:

950

Reference #:

IZ80732

Modified date:

2010-12-24

Translate my page

Machine Translation

Content navigation