IBM Support

PK27069: REORG M MANDATORY DOES NOT CREATE A REORG WHEN ALTER INDEX IS DONE IN OBJECT COMPARE PROCESS

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • User has  DDL of table with related partioned index to compare
    against the catalog and change the limit keys of the unique
    index while also specifying REORG = M or Mandatory . Output of
    Compare generates the alter index but REORG is missing. When
    they use the GENERATED WSL the index goes into REORG
    PENDING state because of the alter of the partitioned index
    and the only way out of this state is to do a manual REORG.
     Customer gets :
       .
    DSNT404I SQLCODE = 610, WARNING:  A CREATE/ALTER ON OBJECT
             xxxxxxx.yyyyyyyy HAS PLACED OBJECT IN REORG PENDING
    DSNT418I SQLSTATE   = 01566 SQLSTATE RETURN CODE
    DSNT415I SQLERRP    = DSNXIAIX SQL PROCEDURE DETECTING ERROR
    .
    Additional symptoms: sqlcode610 sqlcoden610
    

Local fix

  • Please apply ptf when available.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: Users  of  DB2  Object  Comparison Tool, who *
    *                 change  the  limit keys  of the unique index *
    *                 while also specifying REORG = M (Mandatory), *
    *                 may be affected.                             *
    *                 .* PK27069 requires PK31691                  *
    ****************************************************************
    * PROBLEM DESCRIPTION: When  having  DDL of table with related *
    *                      partitioned  index  to  compare against *
    *                      the  catalog  and  changing  the  limit *
    *                      keys  of  the  unique  index while also *
    *                      specifying  REORG  =  M  or  Mandatory, *
    *                      output  of  Compare generates the alter *
    *                      index  but REORG is missing. When using *
    *                      the  generated WSL  the index goes into *
    *                      REORG  PENDING  state  because  of  the *
    *                      alter  of the partitioned index and the *
    *                      only  way  out of this state is to do a *
    *                      manual REORG.                           *
    *                      .* DSNT404I  SQLCODE = 610,  WARNING: A *
    *                      CREATE/ALTER ON OBJECT xxxxxxx.yyyyyyyy *
    *                      HAS PLACED OBJECT IN REORG PENDING      *
    *                      .*                                      *
    *                      A REORG is not created even when  REORG *
    *                      is set to M ( Mandatory ) when altering *
    *                      the partition key of index.  Using  the *
    *                      generated WSL gives SQLWARNING ON ALTER *
    *                      COMMAND, EXECUTE FUNCTION  DSNT404I     *
    *                      SQLCODE = 610                           *
    *                      .* Scenario:                            *
    *                      Source is  DDL and has one CREATE INDEX *
    *                      statement.  Target  is  Automatic  (DB2 *
    *                      catalog extract). The result of Compare *
    *                      is  alter  statement   of   the   index *
    *                      partition keys,  which  puts tablespace *
    *                      into REORG PENDING status.              *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    See Problem Description.
    

Problem conclusion

  • Apply the fix.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PK27069

  • Reported component name

    DB2 OBJECT COMP

  • Reported component ID

    5697G6400

  • Reported release

    710

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2006-06-23

  • Closed date

    2006-10-12

  • Last modified date

    2006-11-02

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

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

Modules/Macros

  •    GOC2CMF
    

Fix information

  • Fixed component name

    DB2 OBJECT COMP

  • Fixed component ID

    5697G6400

Applicable component levels

  • R710 PSY UK18812

       UP06/10/19 P F610

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":"SSAUVH","label":"IBM Db2 Object Comparison Tool for z\/OS"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"710","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
12 February 2021