A fix is available
APAR status
Closed as program error.
Error description
DAP6,ABND=04E-00E2000C,U=SDAPROD ,M=C9 ,C=101.RDS -SQL ,M=DSNTFRCV,LOC=DSNXSMRE.DSNSVSVB+0AC2 occurs for a storage unavailable or not enough storage condition for a query using a its access path.
Local fix
Lower the MXDTCACH zparm value or set it to zero. However, this may impact the performance of other queries.
Problem summary
**************************************************************** * USERS AFFECTED: All DB2 9 for z/OS users and DB2 10 for * * z/OS users of queries that can use a sparse * * index. * **************************************************************** * PROBLEM DESCRIPTION: An ABEND04E RC00E2000C can occur at * * location DSNXSMRE.DSNSVSVB+0AC2 from * * storage manager when trying to satisfy * * a storage request for a sparse index. * **************************************************************** * RECOMMENDATION: * **************************************************************** An ABEND04E RC00E2000C can occur at location DSNSVSVB +0AC2 (OFFSET0AC2 or OFFSETAC2) when a (DB2 Sort) storage request for a sparse index can not be satisfied because sufficient storage is not available or because of some other storage constraint. Instead of DB2 failing the query with an abend, Sort should continue, disable sparse index processing, and write the results to a physical workfile. Also, please note, that to avoid these kinds of storage problems for a sparse index, the user might be able to lower their MXDTCACH (max data caching) setting. This may help sort to build the sparse index.
Problem conclusion
DB2 has been modified to check the 'condition' returned (from storage manager) when acquiring storage for a sparse index. This check will determine next processing instead of abending if not enough storage is available. Additional Keywords: SQLSPARSEINDEX SQLPERFORMANCE SQLSORT
Temporary fix
Comments
APAR Information
APAR number
PM76421
Reported component name
DB2 OS/390 & Z/
Reported component ID
5740XYR00
Reported release
A10
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2012-11-02
Closed date
2012-12-04
Last modified date
2013-01-02
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UK83981 UK83982
Modules/Macros
DSNXSMRE DSNXSMRG
Fix information
Fixed component name
DB2 OS/390 & Z/
Fixed component ID
5740XYR00
Applicable component levels
Fix is available
Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.
[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEPEK","label":"Db2 for z\/OS"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"10.1","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"10.1","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
02 January 2013