A fix is available
APAR status
Closed as program error.
Error description
Abend 04E Reason 00C90101 at Csect DSNIRFNX Erqual 5399 is received during execution of a Rebuild Index after a Redirected Recovery of base+xml tables. The DSNIRFNX abends, because the rebuild index is trying to unload the record which is in V1. The current obdrec is in V0. DM DSNIRFNX is trying to retrieve the OBDREC from system page. However, the page set does not have system page so it abend. When XML table space at source was converted to large RBA format via REORG, Db2 needs to extend XML column 4 and column 5 from 8 bytes binary data type to 10 bytes. To distinguish the different data length of these two columns has been changed, the table version number for the XML is incremented by 1 internally. This is why the source table has version 1. When a new XML table is created as the target table for Redirect Recovery(RR), the column 4 and column 5 of XML table already in 10 bytes, the table version stays 0. During the RR process, the OBDREC field definition for both sourc and target are validated and match. Therefore, no issue on how to interpreted data after RR. However, since the table version is different and the data record in the source table already flagged as V1. Therefore, after RR to the target, the query of any data record would need V1 OBDREC to translate the data. In this case, if page set has system page, it may be ok for the XML. Unfortunately, there is no system page for V1 obdrec so the abend occurred.
Local fix
N/A
Problem summary
**************************************************************** * USERS AFFECTED: * * All Db2 12 for z/OS & Db2 13 for z/OS Users * * of XML tables in conjunction with RECOVER * * with the FROM option, DSN1COPY, REPAIR * * INSERTVERSIONPAGES, and REORG. * **************************************************************** * PROBLEM DESCRIPTION: * * When running DSN1COPY or RECOVER with * * the FROM option on an XML table a 0C4 * * abend occurs. * **************************************************************** * RECOMMENDATION: * * Apply corrective PTF when available * **************************************************************** During RECOVER with the FROM option when running on an XML table, an 0C4 abend can occur when there is differing XML table versions on the source and target table.
Problem conclusion
RECOVER with the FROM option is modified as well as some other proceses to store additional XML versioning information to elegantly handle errors rather than abending.
Temporary fix
Comments
APAR Information
APAR number
PH51434
Reported component name
DB2 OS/390 & Z/
Reported component ID
5740XYR00
Reported release
C10
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2022-12-13
Closed date
2024-03-08
Last modified date
2024-04-01
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UI96016
Modules/Macros
DSNUCATM DSNISCHV DSNIFOD DSNINTRA DSNFUDRE DSNIPPHO DSN1DFPG DSNUCASV DSNUMSGE DSNUCBVR DSNFUDIR
Fix information
Fixed component name
DB2 OS/390 & Z/
Fixed component ID
5740XYR00
Applicable component levels
RD10 PSY UI96016
UP24/03/20 P F403
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":"BU048","label":"IBM Software"},"Product":{"code":"SSEPEK","label":"DB2 for z\/OS"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"12.0","Line of Business":{"code":"LOB10","label":"Data and AI"}}]
Document Information
Modified date:
04 April 2024