PI08029: SQLINCORR SQLCODE100 FOR SELECT FROM XML TABLE WITH ISO(UR)

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• Customer occasionally got an SQLCODE 100 on retrieving a row of
  a XML table for ISO(UR). The row was inserted and the
  insert UR already committed.
  This happened due to another UR insert new row on the same
  base data page while DB2 retrieve the XML data, DB2 detect the
  base data page changed and skip current row for ISO(UR).
  

Local fix

• N/A
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: DB2 11 for z/OS users of XML                 *
  ****************************************************************
  * PROBLEM DESCRIPTION: This APAR addresses the following       *
  *                      problems that may occur when accessing  *
  *                      XML data                                *
  *                      1. Concurrency issue because base page  *
  *                      latch was held while acquiring          *
  *                      unconditional IS lock against XML table *
  *                      , XML table space or partition of XML   *
  *                      table space                             *
  *                      2. Reader with isolation level UR might *
  *                      skip committed record                   *
  *                                                              *
  *                      Additional keyword: DB2INCORR/K, XML    *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  When issuing an IS lock on an XML table, XML table space or
  partition of XML table space, DB2 didn't release the latch on
  the base data page. Since the locking request was unconditional,
  the latch could be held for as long as the locking request was
  suspended waiting for a lock. Other concurrent agents requesting
  access to the base page might be blocked.
  
  ISO(UR) reader accessing XML data might erroneously skip
  committed rows if the base data page was changed after
  XML locking was done.
  

Problem conclusion

• DB2 code has been modified as follows:
  1. DB2 no longer holds a latch while requesting an
     unconditional lock on an XML table, XML table space or
     partition of an XML table space.
  2. For an ISO(UR) reader, if the base page changes when locking
     the XML table space, DB2 will recheck the base record to
     determine if it still qualifies rather than skipping the
     record.
  

Temporary fix

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

Comments

APAR Information

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

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

  UI23676

Modules/Macros

• DSNIACCH DSNIADR  DSNILRBK DSNIONXP DSNIONX2
  DSNIOST2 DSNIRNXT DSNIRPRE DSNIRPRV DSNIRSET DSNISRID
  

Fix information

• Fixed component name

  DB2 OS/390 & Z/

• Fixed component ID

  5740XYR00

Applicable component levels

• RB10 PSY UI23676

     UP14/12/23 P F412

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.