IBM Support

PH33457: unload in native mode from ancient tablespaces can produce incorrect data or stop and report INZRE40 and/or INZU362E

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Db2 HPU can unload incorrect data or stop the
    unload of a tablespace after having issued one or both following
     messages:
    - INZRE40 PAGE NO. page-number IN LDS NO. n OF PAGESET pageset
    IS NOT IN SEQUENCE
    - INZU362E UNLOAD nnnnn FROM TABLESPACE dbanme,tsname FAILED
              POS(1, 2). RC = 0x13fc004 avec ce RC
    
    This occurs when processing, in native mode, the data from a
    table space created with a Db2 version prior to V5.1 and never
    reorganized or loaded in REPLACE mode since then.
    
    The concerned table spaces are non-LARGE tablespaces that have
    both:
    - data pages with a page number(PGNUM) with non-zero leftmost
    byte (aka PgLogID field)
    - data pages with a page number with a zero leftmost byte.
    
    This situation can occur for the following reason. As DB2 has
    not used the PgLogID field since V3, a non-zero value there for
    a non-LARGE pageset would indicate that the page hasn't been
    updated, and the pageset not rebuilt by a DB2 utility, since V3.
    

Local fix

  • To prevent Db2 HPU to unload inccorrect data in such a
    situation, set the VUX038/CHECKINT parmlib parameter to LEVEL1
    so that Db2 HPU fails with ABENDUU1021 and REASON=0000000C
    instead. Reorganizing the concerned tablespace or unloading then
    loading it back in REPLACE mode solves the issue. See technote
    for more details about the determination of the list of affected
    tablespaces and the implementation of the solution.  Technote
    link https://www.ibm.com/support/pages/node/6406218
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: Users of Db2 High Performance Unload         *
    *                 for z/OS                                     *
    ****************************************************************
    * PROBLEM DESCRIPTION: Db2 HPU can unload incorrect data or    *
    *                      stop the unload of a tablespace after   *
    *                      having issued one or both following     *
    *                      messages:                               *
    *                      - INZRE40 PAGE NO. page-number IN LDS   *
    *                      NO. n OF PAGESET pageset IS NOT IN      *
    *                      SEQUENCE                                *
    *                      - INZU362E UNLOAD nnnnn FROM TABLESPACE *
    *                      dbanme,tsname FAILED                    *
    *                        POS(1, 2). RC = 0x13fc004  avec ce RC *
    *                                                              *
    *                      This occurs when processing, in native  *
    *                      mode, the data from a table space       *
    *                      created with a Db2 version prior to     *
    *                      V5.1 and never reorganized or loaded in *
    *                      REPLACE mode since then.                *
    *                                                              *
    *                      The concerned table spaces are          *
    *                      non-LARGE tablespaces that have both:   *
    *                      - data pages with a page number(PGNUM)  *
    *                      with non-zero leftmost byte             *
    *                      (aka PgLogID field)                     *
    *                      - data pages with a page number with a  *
    *                      zero leftmost byte.                     *
    *                                                              *
    *                      This situation can occur for the        *
    *                      following reason. As DB2 has not used   *
    *                      the PgLogID field since V3, a non-zero  *
    *                      value there for a non-LARGE pageset     *
    *                      would indicate that the page hasn't     *
    *                      been updated, and the pageset not       *
    *                      rebuilt by a DB2 utility, since V3.     *
    ****************************************************************
    * RECOMMENDATION: Apply the PTF                                *
    ****************************************************************
    Unload in native mode from ancient tablespaces can produce
    incorrect data (incorrout) or stop and report inconsistency
    through INZRE40 and/or INZU362E with RC = 0x13fc004.
    

Problem conclusion

  • Code has been changed to fix this problem
    

Temporary fix

Comments

APAR Information

  • APAR number

    PH33457

  • Reported component name

    DB2 HI PERF UNL

  • Reported component ID

    5697F4400

  • Reported release

    510

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2021-01-18

  • Closed date

    2021-04-26

  • Last modified date

    2021-06-01

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

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

Modules/Macros

  • INZ$$PRM INZTDSC  INZTVAR  INZUTILK
    

Fix information

  • Fixed component name

    DB2 HI PERF UNL

  • Fixed component ID

    5697F4400

Applicable component levels

  • R510 PSY UI75101

       UP21/05/07 P F105

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.

[{"Line of Business":{"code":"LOB10","label":"Data and AI"},"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":"5.1.0"}]

Document Information

Modified date:
03 June 2021