PK88657: BINDER.PLAN_TABLE POPULATED VS. OWNER.PLAN_TABLE WHEN INDEX ON WHEN INDEX ON EXPRESSION IS CREATED ON PLAN_TABLE

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• Wrong PLAN_TABLE is populated when INDEX on expression exists on
  PLAN_TABLE.  Auth-ID of BINDer vs. Auth-ID of plan/package owner
  is used for PLAN_TABLE qualifier.
  
  additional symptoms: SQLCODE551, SQLCODE219 during BIND
  abend04E rc00e20002 LOC=DSNICMT2.DSNSVSVB+06CC
  DB2INCORR/K
  

Local fix

• drop index on PLAN_TABLE
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: All DB2 for z/OS users who created an        *
  *                 index-on-expression on an Explain table      *
  *                 (for example PLAN_TABLE, DSN_PREDICAT_TABLE, *
  *                 etc).                                        *
  ****************************************************************
  * PROBLEM DESCRIPTION: When there is an index-on-expression    *
  *                      created on Explain tables (e.g.,        *
  *                      PLAN_TABLE, DSN_PREDICAT_TABLE, etc.),  *
  *                      the wrong Explain tables might be       *
  *                      populated.  I.e., Explain tables under  *
  *                      the BINDER authorization ID is used     *
  *                      instead of the current owner ID.        *
  *                      Also, some storage abends may occur     *
  *                      due to a storage allocation problem.    *
  *                                                              *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  When there is an index on expression created on Explain tables
  (e.g., PLAN_TABLE, DSN_PREDICAT_TABLE, etc.), and when DB2
  tries to populate these Explain tables, the wrong authorization
  ID is used to qualify the Explain tables.  Thus, the wrong
  Explain tables may be populated.  The storage used for
  calculating an index on expression is allocated from the wrong
  storage pool, which will finally lead to some storage related
  abend at commit time.
  

Problem conclusion

• When there is an index on expression created on Explain tables
  (e.g., PLAN_TABLE, DSN_PREDICAT_TABLE, etc.), DB2 might need
  to switch between run time and bind time for calculating
  the expression and populating the Explain tables.
  DB2 will now save and restore the environment before and
  after switching between run time and bind time.  Also,
  DB2 will now allocate storage from the correct pool
  depending on whether it is run time or bind time.
  

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:

  UK51202

Modules/Macros

• DSNIKESR DSNKEDLE DSNKEINS DSNKSDLE DSNKSINS
  DSNKSKYG DSNUCINT DSNUCLGR DSNUCRUL DSNUKINT DSNUKIUL DSNURFBR
  DSNURFIT DSNURLXL DSNURPUI DSNURSCN DSNURWBF DSNURWIK DSNUSTBL
  DSNUULXA DSNXEIXR DSNXEIXS DSNXESES DSNXREES
  

Fix information

• Fixed component name

  DB2 OS/390 & Z/

• Fixed component ID

  5740XYR00

Applicable component levels

• R910 PSY UK51202

     UP09/11/04 P F911

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.