PK47244: SQLCODE636 FROM MULTIPLE CHANGE IN LIMITKEY VALUES

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• In DB2 Object Compare Tool, changing multiple limitkey values
  can result in sqlcode636. Problem is seen when new key values
  overlap old key values:
  .
   From  To
   2000  4000
   4000  6000
   6000  8000
  .
  Problem reported occurs in DB2 Administration Tool CM when
  CM update generates OC apply job for CM change in partitioned
  object limitkey values.
  .
  Additional symptoms: 636 sqlcoden636 CM Change Management
  .
  Error messages:
  sqlerror on ALTER      command, EXECUTE    function
   DSNT408I SQLCODE = -636, ERROR:  THE PARTITIONING KEYS FOR
  PARTITION 2 ARE NOT SPECIFIED IN ASCENDING OR DESCENDING ORDER
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: Users of Object Compare/Admin 720 with       *
  *                 Change Management generating updates to the  *
  *                 set of partitioning limitkeys for a table by *
  *                 creating a change using OC                   *
  ****************************************************************
  * PROBLEM DESCRIPTION: If a limitkey change crossed a          *
  *                      partition i.e. the new limitkey were    *
  *                      larger than the limitkey of the next    *
  *                      partition, the ALTER TABLE will fail    *
  *                      with :  DSNT408I SQLCODE = -636, ERROR: *
  *                      THE PARTITIONING KEYS FOR PARTITION n   *
  *                      ARE NOT SPECIFIED IN ASCENDING ORDER    *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  The sequence of ALTER TABLE statements has been changed so each
  limitkey change will be valid.
  

Problem conclusion

• The problem has been fixed.
  

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
  

Fix information

• Fixed component name

  DB2 OBJECT COMP

• Fixed component ID

  5697G6400

Applicable component levels

• R720 PSY UK29840

     UP07/10/18 P F710

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.