A fix is available
APAR status
Closed as program error.
Error description
1) ABEND 0C4 DSNISRTI CE66 - DVV storage overlay due to lack of serialization when getting storage from DVS. Also S0C4 in modules DSNISFS DSNISRID DSNIPHC DSNIVOBD DSNIOST2 DSNIRNXT DSNSVBK and 04E abends 00E20005 or 00E20029 in DSNSVBK and 00E20028 in DSNSTACK (d146780) 2) ABEND 04E 00C90101 DSNIROBD ERQUAL 5003 - new system page is not forced out to group buffer pool, which caused a reader to encounter a zero page on the other data sharing member (d146451) Additional symptom: ABEND0C1 ( ABENDS0C1 ) on a bad branch from DSNKTRAV as IXDCMTCRTP area overlaid with DVVL blocks. ( d147977 ) DB2OVRLAY/K
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All users of DB2 for zOS data versioning * **************************************************************** * PROBLEM DESCRIPTION: 1. ABEND0C4 DSNISRTI+CE66 while * * accessing internal Data * * Versioning control block. * * Similar ABEND0C4 could be in * * DSNISFS,DSNISRID,DSNIPHC,DSNIVOBD, * * DSNIOST2, DSNIRNXT, DSNSVBK and * * ABEND04E RC00E20005 or RC00E20029 * * in DSNSVBK and RC00E20028 in * * DSNSTACK. * * 2. ABEND04E RC00C90101 DSNIROBD * * ERQUAL5003 while reading OBD * * information from system page. * **************************************************************** * RECOMMENDATION: * **************************************************************** 1.When concurrent tasks were trying to build Data Versioning internal control block, a latch is required to get the storage from the storage pool. Currently, there are some code path in DB2 that did not get the latch when the storage is acquired. Without a latch to serialize concurrent tasks will cause the storage overlay and abend. 2.In Data Sharing system, the SYSTEM page should be written out to group buffer pool as soon as release of the page during insert. In some case, DB2 did not write out the page immediately because of some internal flag was incorrectly set. This may result other member from the data sharing system to read a zero page and caused the reported abend.
Problem conclusion
1.DB2 code was changed to get the latch when storage was acquired for building Data Versioning control block. 2.DB2 code was changed to immediately write out the SYSTEM page by correctly setting the internal flag.
Temporary fix
********* * HIPER * *********
Comments
APAR Information
APAR number
PM30611
Reported component name
DB2 OS/390 & Z/
Reported component ID
5740XYR00
Reported release
A10
Status
CLOSED PER
PE
NoPE
HIPER
YesHIPER
Special Attention
NoSpecatt
Submitted date
2011-01-17
Closed date
2011-03-28
Last modified date
2011-08-18
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UK66193 UK66194
Modules/Macros
DSNISEGD DSNISEGF DSNISGRT DSNIVOBD
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:
18 August 2011