PI69652: ABEND04E RC00C90206 DSNIIDIS ERQUAL5002

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• An abend with the following title occurred:
  DSN ,ABND=04E-00C90206,U=SYSADM  ,M=N  ,C=101.DMC
   -DSNILREP,M=DSNTFRCV,LOC=DSNIDM  .DSNIIDIS:5002
  
  Index inserts from one data sharing member were missing.
  From the archive logs it looked like the index back chain was
  broken.
  From the dump, the BMTR trace showed a long series of page
  P-lock lock and unlock entries, with same PMB address.
  But then an unlock with different PMB address. It looks like
  we thought we held P-lock when we didn't.
  There was a physical close and reopen of the index page set ,
  from a DROP some minutes earlier.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * DB2 data sharing users.                                      *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * Lost updates in data sharing.                                *
  *                                                              *
  * Corrupted data can result in any of                          *
  * the following symptoms:                                      *
  *  - Incorrect output, INCORROUT.                              *
  *  - ABEND04E RC00C90101, RC00C90102,                          *
  *    RC00C90105, or RC00C902xx in                              *
  *    various CSECTs.                                           *
  *  - Data/index inconsistencies reported                       *
  *    by the CHECK INDEX utility.                               *
  *  - Page regression reported by the                           *
  *    DSN1LOGP utility.                                         *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  For DB2 V10 and V11 it is possible, although unlikely, for a
  page in a buffer pool to have a residual page P-lock after the
  table space or index has been physically closed.  If the object
  is physically opened again, the P-lock may be reassigned to a
  new buffer, but the old one is still flagged to indicate that
  the P-lock is held.  If this buffer is reassigned, an unlock
  will be issued for the P-lock, which can release it out from
  under the new page buffer.  This can result in broken data due
  to updates being made without the protection of the P-lock.
  

Problem conclusion

• The page buffer steal logic has been modified to prevent any
  attempt to release a page P-lock associated with a physically
  closed object.
  

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:

  UI42175

Modules/Macros

• DSNB1PPG DSNB1GWB
  

Fix information

• Fixed component name

  DB2 OS/390 & Z/

• Fixed component ID

  5740XYR00

Applicable component levels

• RC10 PSY UI42175

     UP16/11/16 P F611

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.