IBM Support

PL37164: DSNKFPNT ABEND04E RC00C90101 VRACE5003 WHEN DOING BIND CMD. 89/02/03 PTF PECHANGE

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • BINDING A PLAN ABENDS AND GIVES A DUMP WITH TITLE :
    ABND04E-00C90101,U=DB2VHAL,COMP=XYR00.DMC -DSNITDLE,M=DSNTFRCV.
    LOC=DSNKDM  .DSNKFPNT:5003.
    WE ALSO RECEIVE MSGDSNI014I.
    AFTER THIS HAPPENED ONCE, THE PROBLEM IS SOLID UNTIL BYPASSED
    BY DOING RECOVER INDEX OF SYSIBM.DSNATX02 AND SYSIBM.DSNGGX01.
    NOTE HOWEVER THAT CHECK UTILITY DOES NOT FIND ANY ERROR IN
    THESE INDEXES.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: ALL DB2 USERS.                               *
    ****************************************************************
    * PROBLEM DESCRIPTION: ABEND04E RC00C90101 IN DSNKFPNT         *
    *                      VRACE5003 DURING SQL INSERTS/DELETES    *
    *                      INTO INDEX DSNATX02 OR ANY DB2          *
    *                      GENERIC NON-UNIQUE SYSTEM INDEX.        *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    ABEND04E RC00C90101 IN DSNKFPNT VRACE5003(ERQUAL5003) DURING
    SQL INSERTS/DELETES INTO GENERIC NON-UNIQUE SYSTEM INDEXES.
    APAR PL31361 CHANGED DSNKFIND TO CONTINUE SEARCHING LEAF PAGES
    FOR NON-UNIQUE INDEXES. THIS ALLOWED DB2 TO POSITION ON THE
    WRONG LEAF PAGE FOR A SPLIT OF A GENERIC NON-UNIQUE INDEX
    PAGE. AFTER THE SPLIT WE ARE NOT ABLE TO FIND THE CORRECT
    NON-LEAF OR PARENT PAGE TO UPDATE WHICH CAUSES THE ABEND04E.
    

Problem conclusion

  • DSNKFIND HAS BEEN CHANGED TO POSITION ON THE CORRECT GENERIC
    NON-UNIQUE INDEX LEAF PAGE BEFORE DOING A LEAF PAGE SPLIT.
    THIS WILL ALLOW THE CORRECT PARENT PAGE(NON-LEAF) PAGE TO
    BE UPDATED.
    DSNKFIND HAS ALSO BEEN CHANGED TO FIND THE CORRECT INDEX MINI
    PAGE WHEN INSERTING A KEY VALUE OF ZEROS FOR BOTH NON-UNIQUE
    AND UNIQUE INDEXES. THIS WILL ALLOW SUBSEQUENT INSERTS TO BE
    PUT INTO THE CORRECT INDEX MINI PAGE.
    DSNKSNCH HAS BEEN CHANGED TO CHECK ALL ENTRIES IN THE NON-LEAF
    PAGE INCLUDING THE LAST LEAF PAGE ENTRY TO FIND THE CORRECT
    LEAF PAGE.
    

Temporary fix

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

Comments

APAR Information

  • APAR number

    PL37164

  • Reported component name

    5740 IBM DATABA

  • Reported component ID

    5740XYR00

  • Reported release

    210

  • Status

    CLOSED PER

  • PE

    YesPE

  • HIPER

    YesHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    1989-01-11

  • Closed date

    1989-02-08

  • Last modified date

    1989-11-06

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

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

    UL45892 UL47941 UL48568 UL48906 UL49155 UL49758 UL50135 UL50942
    UL51735 UL52502 UL53319 UL53975

Modules/Macros

  •    DSNKFIND DSNKSNCH
    

Fix information

  • Fixed component name

    5740 IBM DATABA

  • Fixed component ID

    5740XYR00

Applicable component levels

  • R210 PSY UL45892

       UP89/02/14 P F903 {

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":"210","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
01 August 2023