PM49537: D147461. ABEND0C4-4 AT LOCATION DSNKSINS +048C WHEN USING A SPATIAL INDEX IN DB2 CO-EXISTENCE DB2 V9 N 11/11/30 PTF PECHANGE

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• D147461. ABEND0C4-4  at location DSNKSINS +048C when using a
  spatial index in DB2 co-existence DB2 v9 NFM and DB2 v10 CM.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: All DB2 9 for z/OS users of Spatial indexes  *
  *                 who are migrating from DB2 9 for z/OS to DB2 *
  *                 10 for z/OS.                                 *
  ****************************************************************
  * PROBLEM DESCRIPTION: An unexpected ABEND0C4 rc4 can occur at *
  *                      location dsnk2dm.dsnksins+048c when     *
  *                      using a Spatial index which was created *
  *                      or regenerated on a DB2 V10 CM          *
  *                      subsystem either in a V10 CM/V9 co-     *
  *                      existence environment or in a V10 CM    *
  *                      fallback to V9 environment.             *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  An unexpected ABEND0C4 RC4 can occur at location
  dsnk2dm.dsnksins offset048c when DB2 exploits a Spatial index in
  an INSERT statement.  The index was created on a DB2 V10
  subsystem in either a V10 CM / V9 NFM co-existence environment
  or in a V10 CM fallback to V9 environment.
  
  The abend occurs because the DB2 v9 execution code path does not
  recognize the internal execution structure generated and saved
  from DB2 V10 CM when the Spatial index was created.
  
  Please note that other abends are also possible.
  

Problem conclusion

• The code in DB2 is modified to correct the problem.
  
  With the fix provided in this apar, DB2 will perform an internal
  regeneration of the V10 Spatial index to produce a V9 internal
  execution structure which can then be recognized and executed on
  the V9 subsystem.
  
  Please note that once PM49664 is applied, all existing spatial
  indexes should be dropped and recreated.  This includes spatial
  indexes that are not created in V10.
  
  Also, please reference the ++HOLD for additional information.
  
  Additional Keywords: SQLSPATIAL SQLINSERT SQLDELETE SQLUPDATE
  

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:

  UK74479

Modules/Macros

• DSNGDVAI DSNKSDLE DSNKSINS DSNKSKYG DSNXIAX2
  DSNXIIKY DSNXISB7 DSNXOSV
  

Fix information

• Fixed component name

  DB2 OS/390 & Z/

• Fixed component ID

  5740XYR00

Applicable component levels

• R910 PSY UK74479

     UP11/12/21 P F112

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.