PH30903: DB2 ABEND04E RC00C90101 DSNIBHUN ERQUAL5020 AND CRASH WITH MSGDSNV086E RC00D94001

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• DB2 ABEND04E RC00C90101 DSNIBHUN ERQUAL 5020 and produced this
  dump in a non  Data Sharing environment :
  
  DB2P ABND 04E 00C90101 U=SYSOPR   M=C   C=121.DMC 1
  -DSNIARPL,M=DSNTFRCV,LOC=DSNIDM   DSNIBHUN 5020
  
  DSNI014I + DSNIBHUN DATA IN USE DURING ABEND  399
             REASON 00C90101
             ERQUAL 5020
             TYPE 00000302
             NAME DDAD0051.DDAS5144.X'003FB421'
             CONNECTION-ID=DB2P
             CORRELATION-ID=003.RCRSC 02
             LUW-ID=DB2P.DB2PRD.D8B83ED39DF6=0
  
  and then Db2 crashed with RC00D94001 :
  
  DSNV086E + DB2 ABNORMAL TERMINATION REASON 00D94001
  
  Subsequent Db2 RESTART attempts, also failed with ABEND04E
  RC00C90101 in DSNIBHUN 5020, since Db2 was still able to format
  a new spacemap page and data page of a non  segmented tablespace
  in basic format, even though the system had reached the 6 byte
  RBA hard limit. The PGLOGRBA of the pages involved was
  truncated, which caused the DSNIBHUN:5020 abend when Db2 tried
  to backout the changes in either ROLLBACK or RESTART.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * All Db2 12 for z/OS users of basic format                    *
  * pagesets once beyond 6 byte RBA or LRSN                      *
  * limit.                                                       *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * ABEND04E RC00C90101 DSNIBHUN                                 *
  * ERQUAL5020 during rollback of updates                        *
  * against a basic format pageset after                         *
  * 6 byte RBA or LRSN limit reached.                            *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * Apply corrective PTF when available                          *
  ****************************************************************
  When a Db2 subsystem or data sharing group reaches the 6-byte
  logging limit, attempts to update an object that is still in
  basic format will be rejected with reason code 00C2026D when
  the soft limit is reached or 00C2026E when the hard limit is
  reached.
  However Db2 may skip the logging limit check and allow the
  update of a non-segmented tablespace which is still in basic
  format when an insert happens to format a new spacemap page
  and data page, even though the system had reached the 6-byte
  RBA/LRSN hard limit. Since the object is in basic format, the
  page RBA/LRSN PGLOGRBA of the pages involved will be truncated,
  and that can cause abend DSNIBHUN:5020 for subsequent ROLLBACK
  or RESTART backout processing an UNDO log record, followed by
  DB2 ABNORMAL TERMINATION REASON=00D94001.
  Note that this issue can occur in both Db2 data sharing and
  Db2 non-data sharing environments.
  

Problem conclusion

• Db2 code has been modified to perform the logging limit check
  to prevent the initial update of an object under the above
  circumstances.
  

Temporary fix

• *********
  * HIPER *
  *********
  

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

  UI73752

Modules/Macros

• DSNICLAP DSNIFOI  DSNIFOD  DSNOLFOR DSNB1SWS
  

Fix information

• Fixed component name

  DB2 OS/390 & Z/

• Fixed component ID

  5740XYR00

Applicable component levels

• RC10 PSY UI73752

     UP21/02/10 I 1000 ¢

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.