A fix is available
APAR status
Closed as program error.
Error description
Various abends and/or a DB2 crash can occur because of a storage overlay that is the result of a partition that contains a Basic-Row-Format (BRF) row even though the partition is in Reordered-Row-Format (RRF). This may occur, if all of the following are true: 1) A partitioned object 2) An SQL UPDATE that causes a row to change partitions 3) The new (target) partition (after the UPDATE) is in RRF 4) The partitions use count goes to zero on target partition, and it is closed while the SQL UPDATE is in process. This is a small timing window. It is less likely to occur on objects defined as CLOSE(NO), but it is still possible, if all of the above conditions are true. Abends that has been seen include --> 00E20002 DSNSFSTG+08F2 00D94001 with DB2 crash Various 0C4 abends Additional Keywords: DB2OVRLAY/K
Local fix
REPAIR or Delete any BRF row(s) to prevent further overlays/abends.
Problem summary
**************************************************************** * USERS AFFECTED: All DB2 9, 10 , 11 for z/OS users of UPDATE * * statements. * **************************************************************** * PROBLEM DESCRIPTION: DB2 crashed after storage overlap dump * * occurred at: ABEND0C4 RC00000011 in * * module DSNSVBK offset 100A. * **************************************************************** * RECOMMENDATION: * **************************************************************** DB2 crashed after a storage overlap dump is taken at DSNSVBK. The storage overlap occurs when a BRF table row is mistakenly inserted and later being handled as a normal RRF format which resulted in a wrong data length.
Problem conclusion
The DB2 for z/OS code was modified to fix the abend problem caused by inserting a wrong BRF row into a RRF table.
Temporary fix
********* * HIPER * *********
Comments
APAR Information
APAR number
PM93348
Reported component name
DB2 OS/390 & Z/
Reported component ID
5740XYR00
Reported release
910
Status
CLOSED PER
PE
NoPE
HIPER
YesHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2013-07-18
Closed date
2013-09-25
Last modified date
2018-03-14
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UK97783 UK97850 UK97865
Modules/Macros
DSNILREP
Fix information
Fixed component name
DB2 OS/390 & Z/
Fixed component ID
5740XYR00
Applicable component levels
RA10 PSY UK97783
UP13/10/11 P F310 ¢
RB10 PSY UK97850
UP13/10/11 P F310 ¢
R910 PSY UK97865
UP13/10/11 P F310 ¢
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":"9.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":"9.1","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
14 March 2018