IBM Support

PH48537: REORG DIAGNOSTIC LOG RECORD FOR IDAA AND NON PARTITIONED TABLESPACES SUPPORT

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • The Reorg diagnostic log record for IDAA (type 131 and subtype
    33) introduced with serviceability apar PH15002 has an incorrect
    reload count (which is always 0) when REORG is run on a
    non-partitioned table space.
    This might cause IDAA replication to get a message like:
    
    / W2027 / Setting table creator.tbname (dbid: 595, obid: 262)
    due to utility handling error .
    
    because IDAA detects "data movement" after REORG, which is not
    the case when the number of unloaded records is the same as the
    number of reloaded records.
    This apar will correct the externalization of the reload count
    in the diagnostic log record for IDAA.
    (ie.  IBM Db2 Analytics Accelerator with IBM Integrated
    Synchronization or IBM Db2 for z/OS Data Gate).
    
    KEYWORDS IDAAV7R5/K DATAGATE/K
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * All Db2 12 for z/OS and Db2 13 for z/OS                      *
    * users of REORG TABLESPACE on                                 *
    * non-partitioned table space                                  *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * The REORG diagnostic log record                              *
    * reported an incorrect value for the                          *
    * number of records reloaded on a                              *
    * non-partitioned table space                                  *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Apply corrective PTF when available                          *
    ****************************************************************
    User ran a REORG TABLESPACE against a non-empty non-partitioned
    table space, which completed successfully and generated a
    diagnostic log record with type 131 and subtype 33.  But the
    number of records reloaded indicated by the diagnostic log
    record was incorrect and always 0, which resulted in
    operational error for the consumer of this log record (such as
    IBM Db2 Analytics Accelerator with IBM Integrated
    Synchronization or IBM Db2 for z/OS Data Gate).
    
    Additional keywords:
    IDAAV7R5/K DATAGATE/K
    

Problem conclusion

  • Code has been modified to correct the reload count in the
    aforementioned REORG diagnostic log record on a non-partitioned
    table space.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PH48537

  • Reported component name

    DB2 OS/390 & Z/

  • Reported component ID

    5740XYR00

  • Reported release

    C10

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2022-08-09

  • Closed date

    2022-09-19

  • Last modified date

    2023-05-08

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

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

    UI82446 UI82447

Modules/Macros

  • DSNURWT
    

Fix information

  • Fixed component name

    DB2 OS/390 & Z/

  • Fixed component ID

    5740XYR00

Applicable component levels

  • RC10 PSY UI82446

       UP22/09/27 P F209

  • RD10 PSY UI82447

       UP22/09/27 P F209

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":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEPEK","label":"DB2 for z\/OS"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"12.0","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
08 May 2023