PK53370: REBUILD INDEX UTILITY ON DSNDB06.SYSALTER INDEXES RECEIVES ABEND04E RC00E4001F

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• During a disaster recovery test in V8 compatibility mode (CM),
  the rebuild of the indexes over catalog tablespace
  DSNDB06.SYSALTER failed with ABEND04E RC00E4001F.  This occurs
  when the indexes are explicitly named in the REBUILD INDEX
  utility statement:
  REBUILD INDEX (SYSIBM.DSNDBOB01,SYSIBM.DSNDB0B02)-or-
  REBUILD INDEX (SYSIBM.DSNDBOB01)   -or-
  REBUILD INDEX (SYSIBM.DSNDBOB02)
  The job output shows msgDSNT500I RC00C90094 on DSNDB06.DSNDXX01.
  ...
  Instead of the abend and resource unavailable condition on
  DSNDB06.DSNDXX01, which is a catalog index that has not been
  rebuilt yet, msgDSNU055I (INDEX NOT FOUND) with RC8 should be
  issued.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: All DB2 for z/OS V8 & V9 utility users.      *
  ****************************************************************
  * PROBLEM DESCRIPTION: During a disaster recovery scenario in  *
  *                      DB2 Version 8 Compatibility Mode (CM),  *
  *                      a REBUILD INDEX on the indexes in the   *
  *                      DSNDB06.SYSALTER catalog table space    *
  *                      (DSNDOB01 and DSNDOB02) received an     *
  *                      ABEND04E RC00E4001F abend.              *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  During a DB2 Version 8 compatibility mode (CM) disaster
  recovery scenario an attempt was made to recover the indexes
  in the SYSALTER catalog table space by explicitly specifying
  either of the two index names: DSNDOB01 or DSNDOB02.
  
  The indexes on the SYSDBASE catalog table space had not yet
  been rebuilt (since they're done in a later recovery step)
  and so the user received the following when they attempted
  to rebuild the DSNDOB01 catalog index that's on the
  SYSALTER.SYSOBDS catalog table:
  
     RESOURCE UNAVAILABLE
     REASON 00C90094
     TYPE 00000201
     NAME DSNDB06 .DSNDXX01
  
  DSNDXX01 is a catalog index on the SYSINDEXES catalog table.
  
  The job then abended with the reported problem:
  
     ABEND04E RC00E4001F
  
  
  The same thing would happen in the following scenarios if the
  catalog was unavailable for some reason:
  
  - In V8 CM if the DSNDOB02 catalog index name was specified on
    a REBUILD INDEX utility.
  - In V8 ENFM or NFM if the DSNKCX01 catalog index name was
    specified on a REBUILD INDEX utility.
  - In V9 CM if the DSNRTX03 catalog index name was specified on
    a REBUILD INDEX utility.
  
  Additional notes on catalog indexes that do not exist in all
  DB2 modes in Version 8 and Version 9.
  
  In DB2 Version 8 there are 3 catalog indexes on DB2 catalog
  tables that do not exist in all 3 Version 8 modes (CM, ENFM,
  and NFM). This can cause problems when the DB2 catalog is
  unavailable for some reason as was the case in the reported
  problem (a REBUILD INDEX in a disaster recovery situation).
  
  In Version 8 CM the DSNDOB01 and DSNDOB02 SYSALTER.SYSOBDS
  catalog table indexes are not available because they have
  yet to be created (they are created at the beginning of the
  Enabling New Function Mode (ENFM) process).
  
  At the beginning of the V8 ENFM process the SYSPROCEDURES
  catalog table is dropped. This also drops the DSNKCX01 index
  that is on the SYSPROCEDURES catalog table. So the DSNKCX01
  catalog index exists in V8 CM but not in V8 ENFM or V8 NFM.
  
  In Version 9 CM the DSNRTX03 catalog index is not available
  because it has not yet been created (it is created at the
  beginning of the Version 9 Enabling New Function Mode (ENFM)
  process).
  

Problem conclusion

• DB2 code was modified in Version 8 and Version 9 so that
  it will no longer do the DB2 catalog existence checking
  lookup for any index that does not exist in all modes of
  a DB2 release. Instead, we will now check the mode we are
  in and the specified index name and do the following if the
  index does not exist:
  
    - Set the job return code to 8 (RC8)
    - Issue message MSGDSNU055I to indicate that the specified
      index was not found.
  
  Because the catalog is no longer queried in these cases, we will
  no longer receive the resource unavailable situation or the
  reported abend (ABEND04E RC00E4001F) on a REBUILD INDEX job
  where the catalog is unavailable for some reason and a catalog
  index does not exist.
  

Temporary fix

Comments

APAR Information

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

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

  UK31736 UK31737

Modules/Macros

• DSNUGMAP
  

Fix information

• Fixed component name

  DB2 OS/390 & Z/

• Fixed component ID

  5740XYR00

Applicable component levels

• R810 PSY UK31736

     UP07/12/14 P F712

• R910 PSY UK31737

     UP07/12/14 P F712

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.