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

DB2 UDB Version 8.1 FixPak 16 (also known as Version 8.2 FixPak 9 )

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

• 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
  

Problem conclusion

• Problem was first fixed in Version X FixPak Y (s080111).
  

Temporary fix

Comments

APAR Information

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

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

  LI72900 LI72903

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