PI49688: CUBD FOR IPROC IS NOT REUSED AND LEFT WHEN INVALIDATING CUB FOR XML DUE TO DUPLICATE KEY, CAUSING ABEND04E DSNSVSVB 00E2000C

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• INSERT needs to create a savepoint if a base table has a XML
  column, and restores to the savepoint and invalidates the cub
  (CUBINV=YES) after getting duplicate key (RCDUPKEY). CUBD
  Storage for IPROC is not returned back to free SMFB chain
  started because CUBKEEP=YES was set due to RELEASE(DEALLOCATE).
  Therefore previously allocated storage for CUBD IPROC is not
  reused because it is not in free chain and new CUBD is allocated
  again and again.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: DB2 10 for z/OS and DB2 11 for z/OS users of *
  *                 XML and RELEASE(DEALLOCATE).                 *
  ****************************************************************
  * PROBLEM DESCRIPTION: Storage leak by Insert Proc for XML     *
  *                      table. Following is one symptom         *
  *                      ABEND04E RC00E2000C AT DSNSVSVB         *
  *                         OFFSET+0B06                          *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  If a package is bound with RELEASE(DEALLOCATE), during executing
  insert execution to a table containing XML columns, DB2 might
  create Insert Proc (IProc) for both base table and XML table(s)
  at run time to get performance benefit. If there are some error
  occurred, such as duplicated key, DB2 needs to rebuild some
  internal control blocks including the run-time Insert Proc, but
  it forgot to release storage for older IProc against XML table.
  As the consequence, storage leak occurred.
  

Problem conclusion

• DB2 code has been modified to make sure in such error handling
  case, storage for older Insert Proc against XML table will be
  released correctly.
  

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:

  UI35366 UI35367

Modules/Macros

• DSNIRSVP
  

Fix information

• Fixed component name

  DB2 OS/390 & Z/

• Fixed component ID

  5740XYR00

Applicable component levels

• RA10 PSY UI35366

     UP16/03/02 P F603

• RB10 PSY UI35367

     UP16/03/02 P F603

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.