PK08811: DETERMINING CLUSTERING VS NON-CLUSTERING INDEXES NOT DONE PROPERLY

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• Currently when a tablespace is tested and determined to have a
  clustering index, the entire space is flagged as clustering.
  This is incorrect. If one of the tables in the tablespace does
  not have a clustering index, the NOSYSREC keyword is not allowed
  and all data will be placed in the SYSREC DD.
  
  Counters have been added to determine the number of tables vs.
  the number of clustering indexes in a tablespace. If the
  counters do not match, the space is not flagged as clustered.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: Users of DB2 Automation Tool.                *
  ****************************************************************
  * PROBLEM DESCRIPTION: Currently when a tablespace is tested   *
  *                      and determined to have a clustering     *
  *                      index, the entire space is flagged as   *
  *                      clustering. This is incorrect. If one   *
  *                       of the tables in the tablespace does   *
  *                      not have a clustering index, the        *
  *                      NOSYSREC keyword is not allowed and     *
  *                      all data will be placed in the SYSREC   *
  *                      DD. Counters have been added to         *
  *                      determine the number of tables vs.      *
  *                      the number of clustering indexes in a   *
  *                      tablespace. If the counters do not      *
  *                      match, the space is not flagged as      *
  *                      clustered.                              *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  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

•    HAA$BMSG
  

Fix information

• Fixed component name

  DB2 AUTOMATION

• Fixed component ID

  5697G6300

Applicable component levels

• R220 PSY UK06242

     UP05/08/18 P F508

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.