IBM Support

JR34098: FILE SHARING VIOLATION (AS IN SOMETHING EXTERNAL TO DB2 HOLDING A LOCK ON WINDOWS FOR THE DB2AUDIT FILE)

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • The audit facility has a defect which could cause the DB2
    server or application to hang.
    
    The following events will lead to the hang:
    
    1) A process/application has opened one of the audit log
       files.  The audit log file could be either the instance
       or database level audit log file.
    2) You start the DB2 audit log archive process while the
       file is still being held opened by the other process.
    3) The audit archive procedure will fail because the file
       was held opened by the other process.
    4) The failed archive processing will leave the audit log
       file in an 'archive' state which causes subsequent audit
       events to hang.
    
    The following are symptoms of the hang:
    1) There will exists a file with the same name as one of
       the audit log file but ends with a '.bk' extension.
    2) The db2diag.log log file will contain an error log similiar
       to the following:
    
    2009-07-28-12.01.36.814000+600 I10320966F587      LEVEL: Sever
    PID     : 5032                 TID  : 5508        PROC :
    db2syscs.exe
    INSTANCE: DB2                  NODE : 000
    APPHDL  : 0-12201              APPID: *LOCAL.DB2.090728020133
    AUTHID  : CIFADMIN
    EDUID   : 5508                 EDUNAME: db2agent (instance) 0
    FUNCTION: DB2 UDB, bsu security, sqlexDb2auditArchiveRename,
    probe:450
    CALLED  : DB2 UDB, bsu security, sqlexUpdateAuditLogHeader
    RETCODE : ZRC=0x870F0025=-2029060059=SQLO_INVH "invalid file
    handle"
              DIA8534C An invalid file handle was encountered.
    
    
    2009-07-28-12.01.36.830000+600 I10321555F1222     LEVEL: Error
    PID     : 5032                 TID  : 5508        PROC :
    db2syscs.exe
    INSTANCE: DB2                  NODE : 000
    APPHDL  : 0-12201              APPID: *LOCAL.DB2.090728020133
    AUTHID  : CIFADMIN
    EDUID   : 5508                 EDUNAME: db2agent (instance) 0
    FUNCTION: DB2 UDB, bsu security, sqlexDb2auditArchiveRename,
    probe:400
    RETCODE : ZRC=0x870F0016=-2029060074=SQLO_SHAR "File sharing
    violation."
              DIA8519C A file sharing violation has occurred,
    filename was "".
    DATA #1 : Hexdump, 118 bytes
    0x000000000EC53F50 : 433A 5C44 4F43 554D 457E 315C 414C 4C55
    C:\DOCUME~1\ALLU
    0x000000000EC53F60 : 5345 7E31 5C41 5050 4C49 437E 315C 4942
    SE~1\APPLIC~1\IB
    0x000000000EC53F70 : 4D5C 4442 325C 4442 3243 4F50 5931 5C44
    M\DB2\DB2COPY1\D
    0x000000000EC53F80 : 4232 5C73 6563 7572 6974 795C 6175 6469
    B2\security\audi
    0x000000000EC53F90 : 7464 6174 615C 6462 3261 7564 6974 2E64
    tdata\db2audit.d
    0x000000000EC53FA0 : 622E 504F 5254 414C 2E6C 6F67 2E30 2E32
    b.PORTAL.log.0.2
    0x000000000EC53FB0 : 3030 3930 3732 3831 3230 3133 3337 3230
    0090728120133720
    0x000000000EC53FC0 : 3030 302E 626B
    000.bk
    
    3) A db2 trace will show a thread repeatedly calling sqloopenp
       on the audit log file, from sqlexAuditOpenAdjust.
    
    The hang would only occur where the event is being audited.
    For example, if you audit database connections then the hang
    could occur during a connect.   If you only audit operations
    performed by user Joe then only Joe will experience the hang.
    
    A fix for this APAR will not fix a hang problem directly. With a
    fix,
    DB2 will set the status of archiving audit log in the audit log
    file
    correctly.
    
    
    The offending audit log must be removed in order to fix a hang
    problem even if a fix for this APAR is applied on your system.
    

Local fix

  • - Stop DB2
    - Remove/rename the offending audit log file
    - Start DB2
    

Problem summary

  • close
    

Problem conclusion

  • First fixed in DB2 Version 9.5, Fixpack 6a.
    

Temporary fix

Comments

APAR Information

  • APAR number

    JR34098

  • Reported component name

    DB2 UDB ESE WIN

  • Reported component ID

    5765F4101

  • Reported release

    950

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2009-09-01

  • Closed date

    2010-07-13

  • Last modified date

    2011-08-12

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

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

    JR34155 IC66984 IC67907

Fix information

  • Fixed component name

    DB2 UDB ESE WIN

  • Fixed component ID

    5765F4101

Applicable component levels

  • R950 PSY

       UP

[{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSEPGG","label":"DB2 for Linux, UNIX and Windows"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"950","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
12 August 2011