PI25434: SELECT UR DIDN'T CLAIM AUX INDEX TIMELY AND RESULTED IN 00C90D01

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• There's a timing window that base row was fetched and saved in
  the workfile, while the aux index was not claimed timely.
  
  The lob needed by the select UR was already deleted by
  other URs when the select UR tried to fetch it.
  SELECT UR abended with RC00C90D01
  

Local fix

• n/a
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: All LOB users of DB2 10 for z/OS             *
  ****************************************************************
  * PROBLEM DESCRIPTION: SQLCODE -904 with reason code           *
  *                      RC00C90D01 during a SELECT of a LOB     *
  *                      column when using isolation(UR)         *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  When selecting a LOB column using isolation(UR), the matching
  index entry in the auxiliary index for the LOB could not be
  found.  This occurred because the entry in the index has been
  physically deleted.  The index entry was physcially deleted
  because the SELECT did not claim the auxiliary index in time.
  

Problem conclusion

• DB2 code is changed to claim the aux index earlier to narrow
  down this window.
  

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:

  UI24056

Modules/Macros

•    DSNISELL
  

Fix information

• Fixed component name

  DB2 OS/390 & Z/

• Fixed component ID

  5740XYR00

Applicable component levels

• RA10 PSY UI24056

     UP15/01/03 P F501

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.