PI92298: ABEND04E RC00C90105 DSNKINSL ERQUAL 0D59 18/01/10 PTF PECHANGE

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• During Index pseudo delete cleanup processing, Index Manager
  may skip the required p-lock request and thus result in
  potential index page regression. The ptfs for PI88777 are PE
  and introduced this problem. Later index or data inconsistency
  abends like ABEND 04E - 00C90101 in DSNIIDIS ERQUAL5002 or
  00C90105 DSNKINSL ERQUAL0D59 could be seen.
  The other Symptom:
  Storage overlay causing various abends
  DSNKNXT2 5004  DSNKUNR2 5008  DSNKSALO 5002  DSNKTRAV 5021 &
  DSNKISPL 00C90BAD
   Index key length and first byte of key were overlaid on a non
  leaf index page at position 34x starting from the beginning of
  the index page(total 4 bytes), the overlay occurred because
  index pseudo delete cleanup failed to request page plock so a
  leaf page was regressed and pointed to a deleted leaf page as
  its next page.
   The deleted leaf page was allocated again as a non leaf page.
  The regressed leaf page was split and the page split operation
  updated the non leaf page as if it was the next leaf page of the
  splitting page, which overlaid the non leaf page's first key's
  length field. The bad key length caused more storage overlay
  when the non leaf page was split.
   It is also possible that ABEND0C4 in DSNB*, DSNI*
  or DSNK* modules could occur.
  
  Additional keywords: RC00C90101 DSNI011I MSGDSNI011I
                       DSNI012I MSGDSNI012I 5002 ZSA45
                       RC00C90101 DSNKNXT2 5004 ERQUAL5004
                       MSGDSNI014I DSNI014I DSNKFTCH
                       ERQUAL5008 ERQUAL5021 RC00C90BAD
                       SMCOVERLAY DB2OVRLAY DB2OVRLAY/K
                       RC00C90206 MODDSNIDIF ERQUAL5007
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * All DB2 11 and 12 for z/OS users having                      *
  * indexes defined in a Classic Segmented Table                 *
  * Space and INDEX_CLEANUP_THREADS > 0                          *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * ABND=04E-00C90105 in DSNKINSL with                           *
  * ERQUAL 0D59                                                  *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * Apply corrective PTF when available                          *
  ****************************************************************
  During index pseudo-deleted cleanup process, PI88777(UI52674 &
  UI52675) may mistakenly set ON the gross lock flag in the
  index's internal control block (PSCB)for index defined in a
  segmented table space. This will lead index manager to bypass
  the p-lock request when it shouldn't and may be given a down
  level page during its cleanup on the pseudo-deleted index
  entries.
  

Problem conclusion

• Fixes made in DB2 to set gross lock flag correctly and avoid
  building the internal control block for segmented table space
  during index manager automated pseudo-deleted index entries
  cleanup process.
  

Temporary fix

Comments

APAR Information

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

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

  UI53941 UI53942

Modules/Macros

• DSNIPSFI
  

Fix information

• Fixed component name

  DB2 OS/390 & Z/

• Fixed component ID

  5740XYR00

Applicable component levels

• RC10 PSY UI53941

     UP18/03/03 P F803 ­

• RB10 PSY UI53942

     UP18/03/03 P F803 ­

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.