IBM Support

LI72947: APM SEQ lockname will conflict, if 2 similarly named packages are bound at the same time.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • APM SEQ lockname may conflict for two different packages of the
    similar names.   This could result in unexpected lock symptoms,
    including lock timeouts, waits, deadlocks.
    
    As an example, this could happen from the Development Center
    like so:
    
    1. Launch Development Center.
    2. Select StoredProcedure name in StoredProcedure folder.
    3. Choose Build.
    
    Another Machine
    1. Launch Development Center.
    2. Select StoredProcedure name(Different name above
    StoredProcedure name) in StoredProcedure folder.
    3. Choose Build.
    
    If the package names used are similar, a lock contention will
    occur and db2pd will output something like below:
    Locks:
    Address            TranHdl Lockname                   Type
    Mode Sts Owner      Dur HldCnt Att    ReleaseFlg
    0x0000000160E881C0 14      554C4C4E554C4C473444435053 APM Seq
    ..X  G   14         1   0      0x0000 0x40000000
    0x0000000160E905C0 4       554C4C4E554C4C473444435053 APM Seq
    ..X  W   14         1   0      0x0000 0x40000000
    
    As a result, the creation of one or the other Stored Procedure
    might fail with a -911 (reason code 2 or 68).
    

Local fix

Problem summary

  • APM SEQ lockname may conflict for two different packages of the
    similar names.   This could result in unexpected lock symptoms,
    including lock timeouts, waits, deadlocks.
    
    As an example, this could happen from the Development Center
    like so:
    
    1. Launch Development Center.
    2. Select StoredProcedure name in StoredProcedure folder.
    3. Choose Build.
    
    Another Machine
    1. Launch Development Center.
    2. Select StoredProcedure name(Different name above
    StoredProcedure name) in StoredProcedure folder.
    3. Choose Build.
    
    If the package names used are similar, a lock contention will
    occur and db2pd will output something like below:
    Locks:
    Address            TranHdl Lockname                   Type
    Mode Sts Owner      Dur HldCnt Att    ReleaseFlg
    0x0000000160E881C0 14      554C4C4E554C4C473444435053 APM Seq
    ..X  G   14         1   0      0x0000 0x40000000
    0x0000000160E905C0 4       554C4C4E554C4C473444435053 APM Seq
    ..X  W   14         1   0      0x0000 0x40000000
    
    As a result, the creation of one or the other Stored Procedure
    might fail with a -911 (reason code 2 or 68).
    

Problem conclusion

  • First fixed in DB2 UDB Version 9.5, FixPak 2
    

Temporary fix

Comments

APAR Information

  • APAR number

    LI72947

  • Reported component name

    DB2 UDE ESE LIN

  • Reported component ID

    5765F4104

  • Reported release

    950

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2007-12-17

  • Closed date

    2008-08-26

  • Last modified date

    2008-08-26

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

    LI72806

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

Fix information

  • Fixed component name

    DB2 UDE ESE LIN

  • Fixed component ID

    5765F4104

Applicable component levels

  • R950 PSN

       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:
26 August 2008