Fixes are available
DB2 Version 9.1 Fix Pack 7 for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 5 for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 6 for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 6a for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 7a for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 8 for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 9 for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 10 for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 11 for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 12 for Linux, UNIX and Windows
APAR status
Closed as program error.
Error description
Load pre-partitioning (db2lpprt) agents may receive a signal 11 after a message queue related error, such as hitting the limit imposed by MSGTQL, has been hit. This APAR addresses only the segmentation violation, not the preceeding error.
Local fix
Problem summary
Users affected: Users using the load functionality in DB2. Problem Description: Load pre-partitioning sub agents may receive a signal 11 after a message queue related error has been encountered. Problem Summary: Load pre-partitioning agents may SEGV after hitting a message queue error.
Problem conclusion
First fixed in DB2 UDB Version 9, fix pack 5
Temporary fix
Comments
APAR Information
APAR number
IY98368
Reported component name
DB2 UDB ESE HP-
Reported component ID
5765F4103
Reported release
910
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2007-05-11
Closed date
2009-06-09
Last modified date
2009-06-09
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 UDB ESE HP-
Fixed component ID
5765F4103
Applicable component levels
R910 PSY
UP
Document Information
Modified date:
09 June 2009