A fix is available
APAR status
Closed as program error.
Error description
ABEND04E RC00C90101 at DSNIRSET ERQUAL53C1 during CURSOR SELECT with ISOLATION(CS) and CURRENTDATA(NO): . DSNI014I -CB2A DSNIRSET DATA IN USE DURING ABEND REASON 00C90101 ERQUAL 53C1 TYPE 00000302 NAME FECADB .USWKU01 .X'00208B5F' CONNECTION-ID=CI2BCAB4 CORRELATION-ID=ENTRNSU20033 LUW-ID=VTAM1.CB2BLU.D5F479D902DE=117159 DSNI014I -CB2A DSNIRSET DATA IN USE DURING ABEND REASON 00C90101 ERQUAL 53C1 TYPE 00000303 NAME FECADB .UIWKU011.X'004000FE' CONNECTION-ID=CI2BCAB4 CORRELATION-ID=ENTRNSU20033 LUW-ID=VTAM1.CB2BLU.D5F479D902DE=117159 . The object is LOCKSIZE PAGE, while the CURSOR SELECT with ISOLATION(CS) and CURRENTDATA(NO) will have LOCK AVOIDANCE in effect, therefore, the CURSOR SELECT will not lock the data page. Log shows a page compaction took place between the latches, thus the relate offset of the page/records has been changed in the buffer. However, one of the offset value in the control block is not refreshed after the change. As such, Db2 enter the path of default value checking process which is unnecessary for a column and abend at DSNIRSET:53C1 afterwards.
Local fix
Avoid the LOCK AVOIDANCE
Problem summary
**************************************************************** * USERS AFFECTED: All Db2 for z/OS users. * **************************************************************** * PROBLEM DESCRIPTION: ABEND04E RC00C90101 * * LOC=DSNIDM.DSNIRSET ERQUAL53C1 * **************************************************************** * RECOMMENDATION: Apply corrective PTF when available. * **************************************************************** When a query uses Data Partition Secondary Index (DPSI) to access data with lock avoidance in effect, after Db2 establishes the record position in the index, Db2 detects a change in the page and refreshes the address to the record in MSAPREC(1), a field in an internal control block. Db2 incorrectly skips refreshing a related field MSAPDATA(1) in the same control block. MSAPDATA(1) contains the address where the actual data begins within the record. Db2 encounters an unexpected error when it uses a bad address MSAPDATA(1) to locate and examine the validity of the data in the record.
Problem conclusion
Db2 has been fixed to keep MSAPREC(1) and MSAPDATA(1) in sync. These two fields hold the address of the record and the starting address of the data portion within the record respectively. When MSAPREC(1) is updated, MSAPDATA(1) will also be updated.
Temporary fix
Comments
APAR Information
APAR number
PH11211
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
2019-04-21
Closed date
2019-05-17
Last modified date
2019-07-01
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UI63097 UI63098
Modules/Macros
DSNIRSET
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":"11.0","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":"11.0","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
01 July 2019