Fixes are available
APAR status
Closed as program error.
Error description
When DB2 instance panics due to this issue, you will see panic messages in the db2diag.log and the trap file generated by the panicking EDU would have the top of the stacks similar to below: sqle_panic sqleRelAppGroupMemSeg sqleGetNextAppForDatabase ... This panic is caused by a timing hole issue when DB2 is traversing the application list for the database inside the function sqleGetNextAppForDatabase. The issue doesn't exist in DB2 UDB FOR LUW V95 or above.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: * * ALL * **************************************************************** * PROBLEM DESCRIPTION: * * See Problem Description above. * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 Version 9.1 Fix Pack 11 * ****************************************************************
Problem conclusion
First fixed in Version 9.1 Fix Pack 11.
Temporary fix
Comments
APAR Information
APAR number
IZ89287
Reported component name
DB2 UDB QP AIX
Reported component ID
5724E2500
Reported release
910
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2010-11-16
Closed date
2011-12-21
Last modified date
2011-12-21
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 QP AIX
Fixed component ID
5724E2500
Applicable component levels
R910 PSN
UP
[{"Line of Business":{"code":"LOB10","label":"Data and AI"},"Business Unit":{"code":"BU053","label":"Cloud \u0026 Data Platform"},"Product":{"code":"SSEPGA","label":"DB2 Query Patroller"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"910"}]
Document Information
Modified date:
06 October 2021