A fix is available
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 number
LI72043
Reported component name
DB2 UDE ESE LIN
Reported component ID
5765F4104
Reported release
820
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2007-02-13
Closed date
2008-02-07
Last modified date
2008-02-07
APAR is sysrouted FROM one or more of the following:
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":"820","Line of Business":{"code":"LOB10","label":"Data and AI"}}]
Document Information
Modified date:
16 October 2021