A fix is available
APAR status
Closed as program error.
Error description
Dump Title: DBH1 ABND 0C7 00000000 M=N C=101 RDS SQL M=DSNTFRCV LOC=DSNXGRDS DSNXRTIM OFFSET7120 Dump Title: DBH1 ABND 04E 00C9007E M=N C=101 DMC DSNIRNXT M=DSNTFRCV LOC=DSNIDM DSNIRNXT OFFSET5D90 ABENDS0C7 - ABEND04E RC00C9007E happened on the first compressed row in a tablespace with compression on insert. UPDATE used the dictionary too early. The row was compressed by the dictionary partially built. Then later, it was decompressed incorrectly. . This may happen if an UPDATE is executed after parallel dictionary build service task inserts the dictionary in the tablespace and before its commit. . An overlay can occur, resulting in various abends, including, but not limited to various ABEND0C4's. . Additional Keywords: DB2STGLK/K
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All DB2 for z/OS users that have * * compressed table spaces. * **************************************************************** * PROBLEM DESCRIPTION: Data record is incorrectly * * compressed using an incomplete * * dictionary resulting in the * * following failure symptoms. * * * * - DB2 abnormal termination * * RC00D94001. * * * * - ABEND0C7 RC00000000 DSNXRTIM * * OFFSET7120 * * * * - ABEND0C7 RC00000000 DSNIOST2 * * OFFSET7740 * * * * - ABEND04E RC00C9007E DSNIRNXT * * OFFSET5D90 * * * * - ABEND04E RC00C9007E DSNISRID * * OFFSET0236 ERQUAL5016 * * * * - ABEND04E RC00C90101 DSNIMOFR * * ERQUAL500B * * * * - ABEND04E RC00E4D5D2 DSNUSTBL * * OFFSET480C * * * * - ABEND0C4 RC00000004 DSNURWBF * * OFFSET55F6 * * * * - INCORROUT * * * * - other unpredictable errors * * * * Storage leak in storage class 20. * **************************************************************** * RECOMMENDATION: Apply PTF when available. * **************************************************************** UPDATE accessed a dictionary that was in an incomplete state. The updated record was not compressed correctly. When the record is subsequently accessed and expanded, the expanded record was not the same as the original record. Depending on the contents of memory when the record was compressed the expanded record can be incorrect in multiple ways; thus resulting in the above failure symptoms. - If the expanded record is shorter than the original garbage may be picked up at the end of the record. - If the record is expanded to a length greater than the maximum record length, a storage overlay occurs. - In some cases the expanded record may be the correct length. - Whether the record is expanded to the correct length, shorter or longer, incorrect results will occur because the wrong dictionary symbols were used to translate the data. - If variable length fields are present in the record, storage overlays can occur when the data is being moved. In addition to the record being corrupted the log record created by UPDATE was also incorrect. The record was then nonrecoverable. UPDATE can access an incomplete dictionary only when concurrent access is allowed during dictionary build. Concurrent access is only allowed during INSERT and LOAD with SHRLEVEL CHANGE. Parallel build of the dictionary was allowed beginning in Version 10. A storage leak occurs because parallel build was allocating storage for two dictionaries, but only one dictionary was being freed. Additional keywords: SQLUPDATE SQLINCORROUT SQLINSERT ABEND0C4 DSNB1REL +2AC due to a bad BBPCB pointer.
Problem conclusion
DB2 is changed to properly serialize with parallel dictionary build. The dictionary will only be exposed to concurrent processes once completely built. DB2 is changed to only allocate storage for one dictionary; and that storage is being freed.
Temporary fix
********* * HIPER * *********
Comments
APAR Information
APAR number
PM96666
Reported component name
DB2 OS/390 & Z/
Reported component ID
5740XYR00
Reported release
A10
Status
CLOSED PER
PE
NoPE
HIPER
YesHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2013-09-09
Closed date
2013-12-23
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:
UI13813 UI13814
Modules/Macros
DSNIZLDL DSNUDCTC DSNUZLCR
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:
14 March 2018