IBM Support

PK87243: ABND=04E-00C90101 WITH DSNKUNR2:500F

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Index mgr abended during rollback when applying an index space
    map page log record to UNDO the change. Index mgr first thinks
    the thread had exclusive control over the index, so there was no
    dummy clr for the delete page log records. Later the same thread
    inserted into the table and index, index mgr thinks it doesn't
    have exclusive control, so it wrote dummy clr for the split log
    records. This inconsistency causes certain log records on space
    map page being skipped during the rollback and caused the abend.
    
    Another problem that will be fixed in this apar could be
    seen with the following steps
    1) Using SPUFI (isolation CS, auto commit OFF)
    LOCK TABLE TB1 IN EXCLUSIVE MODE ;
      DELETE FROM TB1 WHERE COL1='5' ;
    Don't commit it !!
    2) Using DSNTEP2 (isolation CS)
      SELECT * FROM TB1 WHERE COL1='5';
      The stmt ends with "SUCCESSFUL RETRIEVAL OF   0 ROW(S)".
      This is not acceptable since the DELETE has not been committed
    yet.
    

Local fix

  • n/a
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All DB2 users with type 2 indexes.           *
    ****************************************************************
    * PROBLEM DESCRIPTION: ABND=04E-00C90101 with ERQUAL500F       *
    *                      at DSNKUNR2:500F during roll back.      *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    When in selective data set locking, index manager was
    mis-informed that it had exclusive access to an index
    and caused the roll back to fail and some index keys
    being physically removed from the page when it should
    be pseudo deleted.
    

Problem conclusion

  • Fixes made to properly check the locking state before
    granting index manager the exclusive access to an index.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PK87243

  • Reported component name

    DB2 OS/390 & Z/

  • Reported component ID

    5740XYR00

  • Reported release

    910

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2009-05-24

  • Closed date

    2009-09-17

  • Last modified date

    2009-11-04

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

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

    UK50209 UK50210

Modules/Macros

  • DSNIPTLK DSNKDLE  DSNKFLRR DSNKFTRR DSNKINSL
    DSNKTRAV
    

Fix information

  • Fixed component name

    DB2 OS/390 & Z/

  • Fixed component ID

    5740XYR00

Applicable component levels

  • R810 PSY UK50209

       UP09/10/02 P F910

  • R910 PSY UK50210

       UP09/10/02 P F910

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":"9.1","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":"9.1","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
04 November 2009