A fix is available
APAR status
Closed as program error.
Error description
D2PE,ABND=0C4-00000010,U=IRIPRD01,M=N ,C=101..RDS -RSCTCACH, M=DSNTFRCV,LOC=DSNXGRDS.DSNXOTDA+0926 occurs for a query that references a complex view.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All DB2 9 and 10 for z/OS users of * * views that contain UNION/UNION ALL. * **************************************************************** * PROBLEM DESCRIPTION: ABEND0C4 RC00000010 DSNXOTDA OFFSET0926 * * may occur for an SQL statement that * * references to a view that satisfies * * the following conditions: * * 1. The view contains UNION/UNION ALL * * 2. The statement that references to * * this view contains predicates that * * can cause some of the branches of the * * UNION/UNION ALL inside the view to be * * pruned. * **************************************************************** * RECOMMENDATION: * **************************************************************** ABEND0C4 RC00000010 DSNXOTDA OFFSET0926 may occur for an SQL statement that references to a view that satisfies the following conditions: 1. The view contains UNION/UNION ALL 2. The statement that references to this view contains predicates that can cause some of the branches of the UNION/UNION ALL inside the view to be pruned. An example of the possible failing case is like : CREATE VIEW V1 (VC1) AS SELECT C1 FROM T1 WHERE C1 = 1 UNION ALL SELECT C2 FROM T2 WHERE C2 = 2 UNION ALL SELECT C3 FROM T3 WHERE C3 = 3 UNION ALL SELECT C4 FROM T4 WHERE C4 = 4; SELECT * FROM V1 WHERE VC1 IN (1,4); An abend may occur for the SELECT statement above because DB2 does not handle the view correctly after the branches of the UNION/UNION ALL inside the view are pruned.
Problem conclusion
DB2 was fixed to handle the view correctly when some of the branches of the UNION/UNION ALL inside view are pruned. Additional KeyWords: SQLUNION SQLUNIONALL SQLVIEW SQLPRUNING
Temporary fix
Comments
APAR Information
APAR number
PM78551
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-12-05
Closed date
2013-02-11
Last modified date
2013-03-04
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UK91561 UK91562
Modules/Macros
DSNXOTDA
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:
04 March 2013