A fix is available
APAR status
Closed as program error.
Error description
A Runstats at part level or a Reorg with inline stats on a tablespace partition gets abend04E RC00E2000F in DSNSVSFB+08C6 and eventually DB2 crashes with abend04E RC00E50079 in DSNUGRAR +1DEC . Analysis of the dump showed that the problem happened when freeing a DB2 storage block that had been overlayed with data; the issue can happen when catalog table SYSIBM.SYSCOLSTATS was containing invalid data having incorrect length. Runstats code should be enhanced to RUNSTATS enhancement to check the actual data lengths of HIGHKEY, HIGH2KEY, LOWKEY, LOW2KEY in SYSCOLSTATS catalog table. Additional Keywords: DB2OVRLAY/K
Local fix
Run a RUNSTATS on the whole tablespace.
Problem summary
**************************************************************** * USERS AFFECTED: All DB2 11 for z/OS RUNSTATS or inline * * STATISTICS utility users gathering * * column statistics at the partition level. * **************************************************************** * PROBLEM DESCRIPTION: ABEND04E RC00E2000F in * * DSNSVSFB + x'08C6' or RC00E50079 in * * DSNUGRAR + x'1DEC' during a RUNSTATS * * or REORG with inline STATISTICS * **************************************************************** * RECOMMENDATION: Apply corrective PTF when available * **************************************************************** When a RUNSTATS utility or REORG with inline STATISTICS was executed at the part level, the utility abended with ABEND04E RC00E2000F in DSNSVSFB OFFSET08C6 or RC00E50079 in DSNUGRAR OFFSET1DEC. A storage overlay occurred as a result of the invalid catalog statistics retrieved from the SYSIBM.SYSCOLSTATS catalog table during RUNSTATS aggregation processing. This problem can also occur during any inline STATISTICS partlevel invocation.
Problem conclusion
A sanity check was added to check lengths of the HIGHKEY, HIGH2KEY, LOW2KEY and LOWKEY statistics in the SYSCOLSTATS catalog table. When invalid data is encountered, a new message DSNU1384I will be issued and the utility will abend with a new reason code RC00E40231. The PTF for APAR PI34029 has added the following documentation for MSGDSNU1384I to the Messages manual and '00E40231'X to the Codes manual. DSNU1384I INVALID CATALOG DATA FOUND FOR COLUMN column-name IN TABLE creator.table-name. Explanation: Invalid catalog data found in SYSIBM.SYSCOLSTATS catalog table for the named table. System action: Utility abends User Response : Correct the data in the catalog table or delete the rows in SYSCOLSTATS and rerun RUNSTATS or inline statistics at the table space or table level instead of at the partition level. Severity : 8 (error) 00E40231 Explanation: Invalid data was detected while accessing the statistics in the SYSIBM.SYSCOLSTATS catalog table. System action: Utility processing abends. Message DSNU1384I will accompany this abend. User response: Message DSNU1384I will indicate the invalid column data found in the catalog table. Correct the catalog data identified by the message. Terminate the utility, and start it again from the beginning.
Temporary fix
Comments
APAR Information
APAR number
PI34029
Reported component name
DB2 OS/390 & Z/
Reported component ID
5740XYR00
Reported release
B10
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2015-02-03
Closed date
2015-04-14
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:
UI26738
Modules/Macros
DSNFUDIR DSNFUDRD DSNUMSGD DSNUSACO DSNUSEF2
Fix information
Fixed component name
DB2 OS/390 & Z/
Fixed component ID
5740XYR00
Applicable component levels
RB10 PSY UI26738
UP15/04/29 P F504
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"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Line of Business":{"code":"LOB10","label":"Data and AI"}}]
Document Information
Modified date:
06 May 2020