PH09352: ABEND04E RC00E2000F AT DSNXSMRE DSNSVSFB OFFSET00A2A WITH SPARSE INDEX ACCESS

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• ABEND04E RC00E2000F at DSNXSMRE DSNSVSFB OFFSET00A2A with sparse
  index access and the only VARCHAR column which is the only key
  in the sparse index has a maximum varchar length of 0 (no data).
  
  This is an extremely rare problem as none of the varchar fields
  came into Db2 actually had any data in it which caused the
  problem.
  
  Additional keywords:
  SQLSPARSEINDEX SPARSEINDEX
  

Local fix

• set MXDTCACH=0 to avoid sparse index access
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * All Db2 12 for z/OS users of sparse index                    *
  * where the last column of the sort key is a                   *
  * VARCHAR column.                                              *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * A possible ABEND04E RC00E2000F at                            *
  * DSNXSMRE DSNSVSFB OFFSET00A2A can                            *
  * occur with sparse index access if the                        *
  * only VARCHAR column is also the only                         *
  * sort key has a maximum varchar length                        *
  * of 0 (no data) and sparse index                              *
  * processing performs common suffix                            *
  * removal to save storage.                                     *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * Apply corrective PTF when available                          *
  ****************************************************************
  A possible ABEND04E RC00E2000F at DSNXSMRE DSNSVSFB OFFSET00A2A
  can occur with sparse index access and the only VARCHAR column
  is also the only sort key has a maximum varchar length of 0 (no
  data) and sparse index processing performs common suffix
  removal to save storage.
  
  The cause of this error occurs when sort tries to copy this
  zero length buffer to temp storage (which can result in an
  overlay). Later,  sort needs to free this storage and when it
  is to be freed, it is found to have been overlaid.
  
  Additionally, other sparse index suffix enhancements have been
  added with this APAR as well.
  
  Please note. The use of a sparse index can be identified from
  EXPLAIN by checking the PLAN_TABLE PRIMARY_ACCESSTYPE
  column for a value of 'T'.
  

Problem conclusion

• Db2 has been modified to correct the sparse index suffix
  checking which includes this rare occurrence scenario
  (which is when the maximum VARCHAR length for all the rows
  is zero length) and add additional suffix verification
  enhancements.
  
  Additional keywords: SQLSPARSEINDEX SPARSEINDEX DB2SORT/K
                       SMCOVRLY DB2OVRLAY DB2OVRLAY/K
  

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:

  UI62288

Modules/Macros

• DSNXSORI DSNXSMRG DSNXSZK  DSNXSMRE DSNXSTSE DSNXSTSG
  

Fix information

• Fixed component name

  DB2 OS/390 & Z/

• Fixed component ID

  5740XYR00

Applicable component levels

• RC10 PSY UI62288

     UP19/04/18 P F904 ¢

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.