IBM Support

LI73244: TIMING HOLE CAN CAUSE SEGMENTATION FAULT WHILE ATTEMPTING TO ACQUIRE LOCK INFORMATION FOR LOCK SNAPSHOT.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When acquiring lock information for a lock snapshot, a timing
    hole could cause a segmentation fault (SIGSEGV).
    
    The potential stack trace might include the following functions:
    0        sqldGetTableName
    1        sqlpm_lock_obj_info
    2        sqlpm_write_locks
    3        sqlpm_write_appl_locks
    4        sqm_snap_appl_locks
    5        sqm_snap_db_locks
    6        sqlmonssagnt
    

Local fix

Problem summary

  • As above.
    

Problem conclusion

  • First fixed in DB2 UDB Version 9.5, FixPak 1 (s080328).
    

Temporary fix

Comments

APAR Information

  • APAR number

    LI73244

  • 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

    2008-03-26

  • Closed date

    2008-05-06

  • Last modified date

    2008-05-06

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

    LI72900

  • 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

  • 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"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"950","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
15 October 2021