IBM Support

IZ23729: Application hang due to file locking on DB2 database directory files

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • You may encounter hang situations within DB2 environment due to
    locking issue on the local DB2 database directory files.
    
    To update the local database directory a process needs to open
    the corresponding files. Unclosed files may then lead to hangs
    due to OS locking on these files.
    
    Many db2 processes are waiting for latch. They have similar call
    stacks as follow:
    ... _global_lock_common ...
    ... _mutex_lock ...
    ... pthread_mutex_lock ...
    ... sqloxltc_app ...
    ... sqljrGetBestSrvAddr ...
    ... sqljrInternalConnect ...
    ... sqljrLookupAddressAndConnect ...
    
    Meanwhile, a db2 process is trying to open the DB2 database
    directory file (i.e. sqllib/sqldbdir/sqldbdir). Its call stack
    might be silimar to:
    ... open64 ...
    ... sqloopenp ...
    ... sqlegopn ...
    ... sqledogd ...
    ... sqledrcv ...
    ... sqledeop ...
    ... sqleUpdateSysDbDirServerInfo ...
    ... sqlexUpdDbDirEntry ...
    ... sqleUpdateActiveAlternateServer ...
    
    Althought the stack indicates that this is special to
    environments which make use of the DB2 client reroute feature
    every DB2 installation is exposed to this issue.
    

Local fix

  • n/a
    

Problem summary

  • AFFECTED USERS:
    
    PROBLEM DESCRIPTION:
    
    You may encounter hang situations within DB2 environment due to
    locking issue on the local DB2 database directory files.
    
    To update the local database directory a process needs to open
    the corresponding files. Unclosed files may then lead to hangs
    due to OS locking on these files.
    
    Many db2 processes are waiting for latch. They have similar call
    stacks as follow:
    ... _global_lock_common ...
    ... _mutex_lock ...
    ... pthread_mutex_lock ...
    ... sqloxltc_app ...
    ... sqljrGetBestSrvAddr ...
    ... sqljrInternalConnect ...
    ... sqljrLookupAddressAndConnect ...
    
    Meanwhile, a db2 process is trying to open the DB2 database
    directory file (i.e. sqllib/sqldbdir/sqldbdir). Its call stack
    might be silimar to:
    ... open64 ...
    ... sqloopenp ...
    ... sqlegopn ...
    ... sqledogd ...
    ... sqledrcv ...
    ... sqledeop ...
    ... sqleUpdateSysDbDirServerInfo ...
    ... sqlexUpdDbDirEntry ...
    ... sqleUpdateActiveAlternateServer ...
    
    Althought the stack indicates that this is special to
    environments which make use of the DB2 client reroute feature
    every DB2 installation is exposed to this issue.
    
    PROBLEM SUMMARY: See Problem Description
    
    LOCAL FIX:
    n/a
    

Problem conclusion

  • First fixed in DB2 UDB Version 9.1, FixPak 7 (build s090308)
    

Temporary fix

Comments

APAR Information

  • APAR number

    IZ23729

  • Reported component name

    DB2 CEE AIX

  • Reported component ID

    5765F3000

  • Reported release

    910

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2008-06-03

  • Closed date

    2009-05-13

  • Last modified date

    2009-05-13

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

    IZ23718

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

Fix information

  • Fixed component name

    DB2 CEE AIX

  • Fixed component ID

    5765F3000

Applicable component levels

  • R810 PSN

       UP

  • R820 PSN

       UP

  • R910 PSN

       UP

  • R950 PSN

       UP

[{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSEPGG","label":"Db2 for Linux, UNIX and Windows"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"910","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
13 May 2009