PK14499: OBJECT COMPARE DOES NOT GENERATE RUNSTATS FOR ALL INDEXES

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• FOr INDEXes that were added during a compare, no RUNSTATS was
  generated
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: Users of DB2 Object Comparison Tool          *
  *                 are affected.                                *
  ****************************************************************
  * PROBLEM DESCRIPTION: Issues reported by PK14499  are related *
  *                      to  the  observation  that  "DB2 Object *
  *                      Comparison   Tool   does  not  generate *
  *                      RUNSTATS for all indexes".              *
  *                      .* Note:                                *
  *                      Currently,  per  PK05668, " No  RUNSTAT *
  *                      utility  was  created for newly created *
  *                      indexes when the table was also new."   *
  *                      (see PK05668/UK05389).                  *
  *                      .* Note:                                *
  *                      The following two issues are addreessed *
  *                      in PK14499:                             *
  *                      * Unnecessary UTILINFO was created when *
  *                      masking  was  used for new indexes when *
  *                      table was also new.                     *
  *                      * Index name was not masked in UTILINFO *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  Currently, per PK05668, "No RUNSTAT utility was created for
  newly created indexes when the table was also new."
  (see PK05668/UK05389).
  .* The following two issues are addreessed in PK14499:
   * Unnecessary  UTILINFO was created when masking  was used
     for new indexes when table was also new.
   * Index name was not masked in UTILINFO
  

Problem conclusion

• Apply the fix.
  

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

•    GOC2CMR
  

Fix information

• Fixed component name

  DB2 OBJECT COMP

• Fixed component ID

  5697G6400

Applicable component levels

• R310 PSY UK12028

     UP06/03/01 P F602

• R710 PSY UK12029

     UP06/03/01 P F602

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.