PK38017: PLAN_TABLE ALIAS OF TYPE='A' IS NOT BEING CREATED.

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• When implementing PLAN_TABLE, DSN_STATEMNT_TABLE,
  DSN_FUNCTION_TABLE via one large table with an alias receives:
  EEE100I
  DSNT408I SQLCODE = -601, ERROR: THE NAME OF THE OBJECT TO BE
  CREATED OR THE TARGET OF A RENAME STATEMENT IS IDENTICAL TO THE
  EXISTING NAME
  When checking for the existance of these tables only table
  Type = 'T' is being recognized. This APAR will also include
  Type = 'A' for alias.
  ADDITIONAL SYMPTOMS
  1. When running batch ANLEEE plan of a package that has WITH
     HOLD syntax the following error message is received only
     if ANLEEE does the dynamic explain:
     EEE538E EXPLAIN of supplied SQL-statement failed, SQL-code:
     -199
  
  2) SQLPA Dynamic Explain using Using COALESCE DSNT408I SQLCODE =
     -401, ERROR.
  3) EEE572E Conversion from Unicode to EBCDIC failed - RC =0004
     RSN=07 for both R220 and R310 running the Easy Explain EEE
     component of SQLPA. MSGEEE572E.
  4) ANLEEE may loop while writing records in report output.
  5) Negative SQL errors are only reported in the COST report.
     Any query that results in a negative SQL error will show
     up on the QLIMIT report.
  6) An enhancement to the SQLPA COST report is made via this
     apar. When the DB2 Optimizer returns a code that not all info
     needed to make a complete cost estimate is available SQLPA
     adds a message to the COST report output. Before this APAR it
     reads:
       SQL is Category B (NO STATS), so costs may be incomplete!
     After this APAR the message will read:
       SQL is Category B (NO STATS), so costs might be incomplete.
       Category B indicates that some condition exists for which
       DB2 was forced to use default values for its  estimate.
       In these cases, the DB2 optimizer cannot give a complete
       assessment of cost.
     In addition, DB2 APAR PK21222 CLOSED FIN would add a new
     reason code to distinguish a Catagory B request caused by
     a materialized table. If this new function is adopted in a
     future DB2 release, SQLPA development will revisit the
     category B message to help the user distinguish this cause.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: Users of DB2 SQL Performance Analyzer.       *
  ****************************************************************
  * PROBLEM DESCRIPTION: When implementing PLAN_TABLE,           *
  *                      DSN_STATEMNT_TABLE, DSN_FUNCTION_TABLE  *
  *                      via one large table with an alias       *
  *                      receives: EEE100I DSNT408I SQLCODE =    *
  *                      -601, ERROR: THE NAME OF THE OBJECT TO  *
  *                      BE CREATED OR THE TARGET OF A RENAME    *
  *                      STATEMENT IS IDENTICAL TO THE           *
  *                      EXISTING NAME When checking for the     *
  *                      existance of these tables only table    *
  *                      Type = 'T' is being recognized. This    *
  *                      APAR will also include Type = 'A' for   *
  *                      alias.                                  *
  *                      ADDITIONAL SYMPTOMS                     *
  *                      1. When running batch ANLEEE plan of a  *
  *                      package that has WITH HOLD syntax the   *
  *                      following error message is received     *
  *                      only if ANLEEE does the dynamic         *
  *                      explain: EEE538E EXPLAIN of supplied    *
  *                      SQL-statement failed, SQL-code: -199    *
  *                      2. SQLPA Dynamic Explain using Using    *
  *                      COALESCE DSNT408I SQLCODE = -401,       *
  *                      ERROR.                                  *
  *                      3. EEE572E Conversion from Unicode to   *
  *                      EBCDIC failed - RC =0004 RSN=07 for     *
  *                      both R220 and R310 running the Easy     *
  *                      Explain EEE component of SQLPA.         *
  *                      MSGEEE572E.                             *
  *                      4. ANLEEE may loop while writing        *
  *                      records in report output.               *
  *                      5. Negative SQL errors are only         *
  *                      reported in the COST report. Any query  *
  *                      that results in a negative SQL error    *
  *                      will show up on the QLIMIT report.      *
  ****************************************************************
  * RECOMMENDATION: APPLY the PTF.                               *
  ****************************************************************
  Code has been changed to correct this condition.
  

Problem conclusion

• APPLY the PTF.
  

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:

Modules/Macros

•    ANLALL   ANLHEX3  ANLMAIN  ANLNEW2  ANLPARM
  ANLPGME7 ANLPGME8 ANLPGM3N ANLPGM31 ANLPLAN  ANLPRC3C ANLPRC3R
  ANLPRE3C ANLPRE3R ANLPROCC ANLPROCR ANLQMF22 ANLQMF31 ANLSERV
  ANLSHOW  ANLSQ2M  ANLTABS  ANLUNIC  ANLUOPT  ANLVER8  ANLWIF31
  ANL34    EEEMAIN  EEEPLAN  EEESERV  EEESQ2M  EEETABS  EEEUNIC
  EEEVER8
  

Fix information

• Fixed component name

  DB2 SQL PERF AN

• Fixed component ID

  5697F5701

Applicable component levels

• R220 PSY UK22291

     UP07/02/21 P F702

• R310 PSY UK22292

     UP07/02/21 P F702

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.