IBM Support

PH60874: MISSING UNLOADED ROWS WHEN USING ORDER BY CLAUSE AND UNLDDN CLAUSE. 24/04/18 PTF PECHANGE

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Regression introduced by HPU 5.1 APAR PH35906.
    
    Randomly, expected unloaded rows are missing when the following
    conditions are fulfilled:
    
     - unload in native mode
    
     - unload all rows from a tablespace using the UNLDDN feature
    
     - in the same UNLOAD command, a SELECT clause on a table from
    the tablespace unloaded by UNLDDN is specified with an ORDER BY
    clause.
    

Local fix

  • If it is not mandatory, remove the ORDER BY clause.
    
    If the ORDER BY clause is mandatory, consider splitting the
    unload request in two distinct requests in two distinct HPU
    steps as indicated below:
    
    step 1:
    
    //HPU1 EXEC PGM=INZUTILB,
    
    ...
    
    //SYSIN  DD *
    
    
    
    UNLOAD TABLESPACE dbname.tsname
    
    UNLDDN ddn
    
    
    step 2
    
    
    //HPU2 EXEC PGM=INZUTILB,
    
    ...
    
    //SYSIN  DD *
    
    
    UNLOAD TABLESPACE
    
    
    SELECT col
    
    FROM table
    
    ORDER BY col
    
    OUTDDN ddn
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: Users of Db2 High Performance Unload for     *
    *                 z/OS                                         *
    ****************************************************************
    * PROBLEM DESCRIPTION: An output dataset containing the        *
    *                      unloaded data (UNLDDN, OUTDDN or both)  *
    *                      is incomplete. This occurs when all     *
    *                      the following conditions are fulfilled: *
    *                      - the unload is run either in Db2 HPU   *
    *                        5.1 with the fix for APAR PH35906     *
    *                        applied or in Db2 HPU 5.2             *
    *                      - the unload is processed in native     *
    *                        mode                                  *
    *                      - the same unload command requests both *
    *                      - a physical unload of the whole data   *
    *                        from a tablespace with the UNLDDN     *
    *                        option                                *
    *                      - a logical unload with an ORDER        *
    *                        clause against a table from           *
    *                        tablespace involved in the physical   *
    *                        unload                                *
    *                      - a timing condition regarding the      *
    *                        concurrent unload processes           *
    *                        (physical and logical) is fulfilled   *
    *                                                              *
    *                      Local fix: If applicable, remove the    *
    *                      ORDER clause. Otherwise, consider       *
    *                      splitting the unload request in two     *
    *                      distinct requests, one to create the    *
    *                      UNLDDN output and another one to        *
    *                      create the OUTDDN dataset, as in the    *
    *                      example below:                          *
    *                                                              *
    *                      Step 1                                  *
    *                                                              *
    *                         //HPU1 EXEC PGM=INZUTILB,            *
    *                                                              *
    *                         //SYSIN DD *                         *
    *                                                              *
    *                         UNLOAD TABLESPACE dbname.tsname      *
    *                         UNLDDN ddn                           *
    *                                                              *
    *                      Step 2                                  *
    *                                                              *
    *                         //HPU2 EXEC PGM=INZUTILB,            *
    *                                                              *
    *                         //SYSIN DD *                         *
    *                                                              *
    *                         UNLOAD TABLESPACE                    *
    *                                                              *
    *                         SELECT col                           *
    *                         FROM table                           *
    *                         ORDER BY col                         *
    *                         OUTDDN ddn                           *
    ****************************************************************
    * RECOMMENDATION: Apply the PTF                                *
    ****************************************************************
    missing rows from the unloaded data if physical unload (UNLDDN)
    and logical unload (OUTDDN) with ORDER clause against the same
    tablespace
    

Problem conclusion

  • Code has been changed to fix this problem
    

Temporary fix

Comments

APAR Information

  • APAR number

    PH60874

  • Reported component name

    DB2 HI PERF UNL

  • Reported component ID

    5697F4400

  • Reported release

    520

  • Status

    CLOSED PER

  • PE

    YesPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2024-04-12

  • Closed date

    2024-07-01

  • Last modified date

    2024-08-01

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

Modules/Macros

  • INZ$$CCQ INZ$$PRM INZMQRY  INZPARM  INZTDSC  INZTOOLS INZTVAR
    INZUTIB1 INZUTIB2 INZUTILC INZUTILD INZUTILK
    

Fix information

  • Fixed component name

    DB2 HI PERF UNL

  • Fixed component ID

    5697F4400

Applicable component levels

  • R510 PSY UI97393

       UP24/07/01 P F406 {

  • R520 PSY UI97541

       UP24/07/03 P F407 {

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.

[{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSZJXP","label":"DB2 Tools for z\/OS"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"520","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
01 August 2024