PH56370: GENERATE INDEXES IN CHRONOLOGICAL ORDER INSTEAD OF ALPHABETICALLY

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• This change will ensure an index originally used for clustering
  is still used for clustering after executing generated DDL to
  create a table's indexes.
  
  When a table has multiple indexes, if none are given the CLUSTER
  attribute when created, the first index created is used for
  clustering. In order to preserve the original clustering index,
  this change will generate CREATE INDEX statements in
  chronological order instead of alphabetic order as is currently
  done. Additionally, this change will ensure an index that was
  originally specifically assigned the CLUSTER attribute is given
  the CLUSTER attribute in generated DDL.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: Users of Db2 Administration Tool for z/OS    *
  *                 who generate DDL to create multiple indexes  *
  *                 on a table                                   *
  ****************************************************************
  * PROBLEM DESCRIPTION: When generating multiple indexes on a   *
  *                      table, they might not be generated in   *
  *                      their original order. Implicitly, the   *
  *                      first index created is used for         *
  *                      clustering. Therefore, unless CLUSTER   *
  *                      is explicitly specified for one         *
  *                      of the indexes, a different index might *
  *                      being used for clustering than the one  *
  *                      originally used.                        *
  ****************************************************************
  This APAR introduces a change when generating CREATE INDEX
  statements: the CREATE INDEX statements are ordered according to
  their creation date and time. This behavior ensures that, when
  CLUSTER is not explicitly specified, the same index is
  used for clustering as was used originally.
  

Problem conclusion

• The problem has been resolved.
  

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:

  UI94587 UI94588

Modules/Macros

• ADB2REM
  

Fix information

• Fixed component name

  DB2 ADMIN TOOL

• Fixed component ID

  568851500

Applicable component levels

• RC10 PSY UI94587

     UP23/11/28 P F311

• RD10 PSY UI94588

     UP23/11/28 P F311

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.