IBM Support

PH19463: SQLCODE100 WAS ISSUED INCORRECTLY BY SQL SELECT USING INDEX ACCESS

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When running SQL SELECT with index access concurrently with
    DELETE and INSERT applications, SQLCODE100 was issued
    incorrectly when the row being searched for existed in the
    table, isolation level CS and currentdata(yes) was used.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * All Db2 12 for z/OS users using indexes                      *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * SQLCODE +100 was issued incorrectly                          *
    * by SQL SELECT using index access                             *
    * with ISOLATION(CS)  and                                      *
    * CURRENTDATA(YES)                                             *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Apply corrective PTF when available                          *
    ****************************************************************
    SQL SELECT using index access with ISOLATION(CS) and
    CURRENTDATA(YES) runs concurrently with DELETE and INSERT
    application. When Db2 reads a pseudo deleted RID
    in the index, it issues a test lock request to check if the
    pseudo deleted RID is committed.
    The DELETE operation creating the pseudo deleted RID
    has committed and a different RID with the same key value has
    been inserted into the index. After the feedback from IRLM
    indicates the DELETE operation is committed, Db2 fails to
    refresh the index page to locate the newly inserted RID.
    The SQL SELECT returns SQLCODE +100 incorrectly.
    

Problem conclusion

  • Db2 code has been updated to refresh the index page after the
    feedback from IRLM indicates that a pseudo deleted RID
    can be skipped during index access. If the page is
    changed after the refresh, Db2 will reposition on the index
    page. This change allows Db2 to return a newly inserted and
    committed RID during index access.
    

Temporary fix

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

Comments

APAR Information

  • APAR number

    PH19463

  • Reported component name

    DB2 OS/390 & Z/

  • Reported component ID

    5740XYR00

  • Reported release

    C10

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    YesHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2019-11-21

  • Closed date

    2019-12-07

  • Last modified date

    2020-01-03

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

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

    UI66854

Modules/Macros

  • DSNKNXT2 DSNKFTCH
    

Fix information

  • Fixed component name

    DB2 OS/390 & Z/

  • Fixed component ID

    5740XYR00

Applicable component levels

  • RC10 PSY UI66854

       UP19/12/17 P F912 Ž

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"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"12.0","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"12.0","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
03 January 2020