IBM Support

PL29953: ABEND04E RC00C90206 VRACE5007 IN DSNITDLE DURING DELETE FOLLOWED BY INSERT.

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • DURING DB2 BACTH APPLICATION DOING DELETES FOLLOWED BY INSERTS,
    INSTEAD OF UPDATES, INDEX GET GLOBBERED. ONE OF HIGH KEYS IN
    INDEX PAGE DIRECTORY CANNOT BE FOUND IN THE CORRESPONDING
    SUBPAGE BUT IN THE NEXT ONE.
    ALSO RC00C90206 VRACE5002 IN DSNIIDIS
    ALSO RC00C90105 VRACE0D21 IN DSNIBROK
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: DB2 USERS WITH UNIQUE INDEXES                *
    *                 AND WITH APAR PL21177 APPLIED.               *
    ****************************************************************
    * PROBLEM DESCRIPTION: ABEND04E RC00C90101 IN MODULE DSNITDLE  *
    *                      VRACE5007 ON AN SQL DELETE STATEMENT.   *
    *                      THIS PROBLEM OCCURS AFTER APPLYING APAR *
    *                      PL21177.                                *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    ABEND04E RC00C90101 IN DSNITDLE VRACE5007 ON A SQL DELETE
    STATEMENT. THE ROW THAT IS BEING DELETED HAS BEEN INSERTED
    INTO THE WRONG MINI PAGE. THIS ROW WILL NOT BE FOUND IN THE
    INDEX CAUSING THE RC00C90101 ON THE DELETE STATEMENT. THIS
    OCCURS WHEN USING AN UNIQUE INDEX AND DELETING ALL OF THE KEYS
    IN THE MINI PAGE, AND REINSERTING THE HIGH KEY FOR THAT MINI
    PAGE. THE HIGH KEY GETS INSERTED INTO THE NEXT MINI PAGE, BUT
    THE HIGH KEY DIRECTORY SHOWS THAT IT IS STILL THE HIGH KEY OF
    THE PREVIOUS MINI PAGE. THE HIGH KEY SHOULD HAVE BEEN INSERTED
    INTO THE SAME MINI PAGE THAT IT WAS DELETE FROM.
    THIS PROBLEM OCCURS AFTER APPLYING APAR PL21177.
    

Problem conclusion

  • APPLICABLE PTFS: PE25061 R302 TF803
                     PE25062 R202 TF803
    APAR PL21177 IS IN ERROR. DSNKFIND HAS BEEN CHANGE TO REMOVE
    THE FIX FOR PL21177 AND CORRECTLY POSITION ON A REINSERT OF A
    HIGH KEY OF A MINI PAGE. DSNKFIND WILL ALSO POSITION ON THE
    CORRECT MINI PAGE WHICH CONTAINS A KEY OF BINARY ZEROS.
    AFTER APPLYING APAR PL29953 THE INDEX MUST BE RECOVERED,
    RECOVER INDEX UTILITY SHOULD BE USED TO RECOVER THE INDEX.
    

Temporary fix

Comments

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

APAR Information

  • APAR number

    PL29953

  • Reported component name

    5740 IBM DATABA

  • Reported component ID

    5740XYR00

  • Reported release

    302

  • Status

    CLOSED PER

  • PE

    YesPE

  • HIPER

    YesHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    1988-07-20

  • Closed date

    1988-08-25

  • Last modified date

    1989-12-04

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

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

    UL36378 UL36379 UL37923 UL39883 UL40586 UL40596 UL41259 UL42178
    UL43813 UL44363

Modules/Macros

  •    DSNKFIND
    

Fix information

  • Fixed component name

    5740 IBM DATABA

  • Fixed component ID

    5740XYR00

Applicable component levels

  • R210 PSY UL36379

       UP88/08/30 P F807

  • R302 PSY UL36378

       UP88/08/31 P F807

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"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"302","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
01 August 2023