PK07144: TABLE CONTROLLED PARTITIONING ALTER OF LIMITKEY CAUSES DROP CREATE INSTEAD OF ALTER - OR SQLCODE669 ON DROP TABLE

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• In DB2 Object Compare Tool a difference between source and
  target limitkey values for a table controlled partitioned table
  can produce two different problems.
  .
  When compare is run at tablespace level, a drop / create is
  the result, when an ALTER would suffice.
  .
  When compare is run at table level, a DROP TABLE results in
  sqlcode669 ( -669 ).
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: Users of DB2 Object Comparison Tool, who     *
  *                 have table-controlled  partitioning, may     *
  *                 be affected.                                 *
  ****************************************************************
  * PROBLEM DESCRIPTION: A difference between Source and Target  *
  *                      Limitkey values for a table controlled  *
  *                      partitioned table can produce two       *
  *                      different problems.                     *
  *                      .* When compare is run at tablespace    *
  *                      level, a drop / create is the result,   *
  *                      when an ALTER would suffice.            *
  *                      .* When compare is run at table level,  *
  *                      a DROP TABLE results in SQLCODE -669.   *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  Changing  the  limit key  for a table with table-controlled
  partitioning   results  in  the  object  being  dropped and
  recreated  rather  then  ALTER'ed,  and  if  the compare is
  done at the table level, Object Compare generates incorrect
  DDL, DROP TABLE, resulting in DSNT408I SQLCODE = -669.
  

Problem conclusion

• Apply the fixes.
  

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

•    GOC2CMF  GOC2DTC
  

Fix information

• Fixed component name

  DB2 OBJECT COMP

• Fixed component ID

  5697G6400

Applicable component levels

• R310 PSY UK07472

     UP05/09/30 P F509

• R710 PSY UK07473

     UP05/09/30 P F509

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.