PI47610: UNLOADED RECORDS SORTED INCORRECTLY IN NATIVE MODE

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• The order of the data unloaded by DB2 HPU is incorrect if the
  following conditions apply:
  - a logical unload with an ORDER CLUSTER clause is requested
  - the unload is performed in native mode
  - the data are to be unloaded from an image copy
    (COPYDDN option) and the DDLDDN option is specified
  - in the definition of the clustering index provided to DB2 HPU,
    the sort attribute of one of the columns involved in the
    index key is not specified explicitly
    (none of ASC/DESC/RANDOM is specified)
  
  For example: If the clustering index is defined as follows:
  
  CREATE UNIQUE INDEX
  ME.MYCLUSTIX
  ON
  ME.MYRTABLE
  (COL00001 ASC,COL00002 DESC,COL00003    ) CLUSTER;
  
  according to  COL00001 ASC,COL00002 DESC
  (the COL00003  column is ignored).
  
  Other keywords follow:
  PB12847  SORT SORTING ASCENDING DESCENDING ASC DSC reverse
  expected unexpected
  

Local fix

• In the DDLDDN data set, add the ASC attribute to the columns
  where no order attribute is set.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: Users of DB2 High Performance Unload.        *
  ****************************************************************
  * PROBLEM DESCRIPTION: The order of the data unloaded by DB2   *
  *                      HPU is incorrect if the following       *
  *                      conditions apply:                       *
  *                      - a logical unload with an ORDER        *
  *                       CLUSTER clause is requested            *
  *                      - the unload is performed in native     *
  *                       mode                                   *
  *                      - the data are to be unloaded from an   *
  *                      image copy (COPYDDN option) and the     *
  *                      DDLDDN option is specified              *
  *                      - in the definition of the clustering   *
  *                      index provided to DB2 HPU, the sort     *
  *                      attribute of one of the columns         *
  *                      involved in the index key is not        *
  *                      specified explicitly (none of           *
  *                      ASC/DESC/RANDOM is specified)           *
  *                      For example: If the clustering index    *
  *                      is defined as follows:                  *
  *                      CREATE UNIQUE INDEX                     *
  *                      ME.MYCLUSTIX                            *
  *                      ON                                      *
  *                      ME.MYRTABLE                             *
  *                      (COL00001 ASC,COL00002 DESC,            *
  *                      COL00003    ) CLUSTER;                  *
  *                      the data unloaded by the following      *
  *                      unload:                                 *
  *                      UNLOAD TABLESPACE                       *
  *                      COPYDDN IMAG DDLDDN DDL                 *
  *                      SELECT * FROM ME.MYTABLE                *
  *                      ORDER CLUSTER                           *
  *                      OUTDDN(SYSREC)                          *
  *                      is not sorted according to the          *
  *                      clustering key (COL00001 ASC,COL00002   *
  *                      DESC,COL00003) but only according to    *
  *                      COL00001 ASC,COL00002 DESC (the         *
  *                      COL00003  column is ignored).           *
  *                      PB12847                                 *
  ****************************************************************
  * RECOMMENDATION: APPLY the PTF.                               *
  ****************************************************************
  The inzctrl and oddlx2y modules were changed.
  

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

•    INZUTILK
  

Fix information

• Fixed component name

  DB2 HI PERF UNL

• Fixed component ID

  5697F4400

Applicable component levels

• R420 PSY UI32342

     UP15/11/26 P F511

• R430 PSY UI32343

     UP15/11/28 P F511

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.