IBM Support

PH41586: RECOVER UTILITY ENDING WITH RC00 AND LEAVING A NON PARTITIONED INDEX IN PSRBDP STATUS IN PLACE OF ENDING WITH RC08

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • RECOVER BACKOUT YES TOLOGPOINT of a tablespace
    and its indexes (indexes were created with COPY YES) completes
    with RC00 but leaves one of
    the NPIs in PSRBDP status even after the following message:
    DSNU599I -DS1M 260 21:58:34.01 DSNUCATM - INDEXSPACE
    creator.IXname HAS BEEN RECOVERED TO A CONSISTENT POINT IN TIME
    WITH TABLESPACE dbname.TSname
    Further analysis showed an internal abend in index Manager
    DSNKDLE during log phase of the RECOVER.
    The RECOVER utility should have ended with RC08 in this
    scenario.
    

Local fix

  • BYPASS/CIRCUMVENTION:
    RECOVER the Tablespace and run Rebuild index for the NPIs
    
    RECOVERY ACTION:
    Use REBUILD INDEX to rebuild the NPIs
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * All Db2 12 for z/OS users of the RECOVER                     *
    * utility on indexes.                                          *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * RECOVER utility completed with RC0                           *
    * although one of the non-partitioned                          *
    * indexes (NPIs) was in page set                               *
    * REBUILD-pending (PSRBD) status after                         *
    * errors during log processing.                                *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Apply corrective PTF when available                          *
    ****************************************************************
    RECOVER BACKOUT YES TOLOGPOINT of a table space and its indexes
    ended with RC0, but one of the NPIs was in PSRBD status caused
    by errors encountered during Db2 log processing for the utility
    and not all log records could be applied to indexes in the list
    of objects. There was no indication in the job output of this
    error. In addition, the following message was seen in the job
    output for the NPIs in PSRBDP status:
        DSNU599I DSNUCATM - INDEXSPACE creator.IXname HAS BEEN
        RECOVERED TO A CONSISTENT POINT IN TIME WITH TABLESPACE
        dbname.TSname
    The recovery should have ended with RC08 to indicate an error
    occurred. MSGDSNU599I should not have been issued for the
    failing object. New messages should have been issued to report
    log processing errors on indexes, and indexes in page set
    REBUILD-pending when a utility finishes.
    This problem could also occur for recovery to the current
    state, when BACKOUT NO, or LOGONLY is specified.
    

Problem conclusion

  • Code in the RECOVER utility has been modified to issue new
    messages DSNU1577I and DSNU1578I when errors occur during log
    processing for one or more indexes. MSGDSNU599I will no longer
    be issued in this case.
    If you have a process that scans for error messages in the
    RECOVER utility output, then you may need to change your
    process to scan for the new message DSNU1578I which is now
    issued to report log processing errors on indexes.
    You may also need to change your process to look for the new
    message DSNU1577I which is now issued by utilities to report
    indexes in page set REBUILD-pending when a utility finishes.
    DSNU1577I csect-name - obj-type obj-qual.obj-name IS IN PAGE
    SET REBUILD PENDING RESTRICTED STATE
    Explanation
    This message is issued by each utility that operates on a
    non-partitioned (NPI) index and detects page set
    REBUILD-pending (PSRBD) on the NPI at completion.
    If the RECOVER utility issued this message, not all log records
    could be applied during log processing. The non-partitioned
    index was placed in page set rebuild pending status.
    csect-name
    The name of the control section that issued the message.
    obj-type
    The type of the object.
    obj-qual.obj-name
    The name of the object, as a qualified name.
    System programmer response
    If the RECOVER utility issued this message, use the REBUILD
    INDEX utility to rebuild this index.
    If the REBUILD INDEX, LOAD SHRLEVEL NONE or REORG TABLESPACE
    utility issued this message, either duplicate index entries
    existed during the BUILD/SORTBLD phase, or invalid KEY/RIDs
    were detected. Resolve the duplicate index entries or invalid
    KEY/RID entries and run REBUILD INDEX to rebuild the index and
    remove the index from page set rebuild pending status.
    Severity
    4 (warning)
    DSNU1578I csect-name ERROR DURING LOG PROCESSING FOR ONE OR
    MORE INDEXES
    Explanation
    Errors were encountered during Db2 log processing for the
    RECOVER utility and not all log records could be applied to
    indexes or index partitions in the list of objects.
    csect-name
    The name of the control section that issued the message.
    System action
    For the indexes or index partitions in error:
    - Log processing is stopped.
    - REBUILD-pending is set on for index partitions.
    - Page set REBUILD-pending is set on for non-partitioned
      indexes.
    SVC dumps with the ABEND04E abend code may be issued by Db2 for
    errors when the log record could not be applied because the
    contents of an index page is not as expected.
    For indexes in the list without errors, log processing
    continues.
    The utility ends with an error return code of 8.
    System programmer response
    Check the console SYSLOG for Db2 error or resource unavailable
    messages, and for SVC dumps.
    Check the utility job output for these messages to find the
    affected indexes:
    DSNU830I INDEX= index-name IS IN REBUILD PENDING STATE
    DSNU1577I INDEX= object-qualifier.object-name IS IN PAGE SET
    REBUILD PENDING RESTRICTED STATE
    Issue the DISPLAY DATABASE command to check on the status of
    indexes in the list of objects processed by the utility.
    Contact IBM support when an SVC dump with abend code ABEND04E
    was generated.
    Severity
    8 (error)
    

Temporary fix

Comments

APAR Information

  • APAR number

    PH41586

  • 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

    2021-10-26

  • Closed date

    2022-03-30

  • Last modified date

    2022-05-03

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

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

    UI79955

Modules/Macros

  • DSNUCALU DSNFUDIR DSNILOGA DSNUCATM DSNILDOR DSNIREDO DSNKUNR2
    DSNIUNDO DSNUCALA DSNUGSRX DSNUCALC DSNFUDRE DSNUMSGE
    

Fix information

  • Fixed component name

    DB2 OS/390 & Z/

  • Fixed component ID

    5740XYR00

Applicable component levels

  • RC10 PSY UI79955

       UP22/04/07 P F204

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.

[{"Line of Business":{"code":"LOB10","label":"Data and AI"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEPEK","label":"DB2 for z\/OS"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"12.0"}]

Document Information

Modified date:
04 May 2022