A fix is available
APAR status
Closed as program error.
Error description
ABEND04E RC00E20009 DSNXSMRE DSNSVSFB +0806 OR OFFSET0806 WHEN EXECUTING A SQL STATEMENT WITH SPARSE INDEX AND WORKFILE
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All DB2 10 for z/OS users of queries that * * can use a sparse index. * **************************************************************** * PROBLEM DESCRIPTION: An ABEND04E RC00E20009 at location * * DSNXSMRE DSNSVSFB +0806 can occur when * * executing an SQL statement which uses a * * sparse index where the result of the * * sparse index goes to a physical * * workfile. * **************************************************************** * RECOMMENDATION: * **************************************************************** An ABEND04E RC00E20009 can occur at location DSNSVSFB OFFSET0806 (or DSNXSMRE DSNSVSFB +0806) when executing an SQL statement that uses a sparse index if the result of the sparse index goes to a physical workfile. The failure can occur as follows. When calculating the size of the storage needed for a sparse index, DB2 initially calculates the size that would be needed assuming that the information will be placed to an in-memory workfile. But, if this size is not allowable, DB2 will then default to a physical workfile using this same calculated space. However, since there is a problem with this calculation for physical workfiles, it needs to be re- done so that the storage request for physical workfiles is correct and does not request more storage than is feasible which can result in the above error.
Problem conclusion
DB2 has been modified to re-calculate the amount of storage needed if the sparse index is to be placed to a physical workfile. Once the storage request is corrected, the reported abend will no longer occur. Additional Keywords: SPARSEINDEX SQLSTORAGE
Temporary fix
Comments
APAR Information
APAR number
PM74883
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-10-11
Closed date
2012-11-06
Last modified date
2012-12-04
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UK83278
Modules/Macros
DSNXSMRE DSNXSMRG
Fix information
Fixed component name
DB2 OS/390 & Z/
Fixed component ID
5740XYR00
Applicable component levels
RA10 PSY UK83278
UP12/11/21 P F211
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:
04 December 2012