PK14204: SQLCODE636 FROM ALTER / VALUES ON MULTIPLE INDEX KEY VALUES IN ONE OPERATION

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• In DB2 Administration Tool an AL command followed by VALUES
  command allows change of limitkey values for index objects. An
  sqlcode636 can occur if more than one value is changed at once,
  causing overlap of limitkey values. For example, changing keys:
  .
   From  To
   2000  4000
   4000  6000
   6000  8000
  .
  Additional symptoms: 636 sqlcoden636 adb21x adb21xa adb21xav
  DSNT408I SQLCODE = -636, ERROR:  THE PARTITIONING KEYS FOR
     PARTITION 2 ARE NOT SPECIFIED IN ASCENDING OR DESCENDING
     ORDER
  

Local fix

• Use PROMPT ON to execute ALTER statements individually.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: Users of DB2 Administration Tool R710, who   *
  *                 change  Limitkey  values  for  indexes and   *
  *                 table  controlled  tables in DB2 R810, may   *
  *                 be affected.                                 *
  ****************************************************************
  * PROBLEM DESCRIPTION: When changing values for Limit Keys one *
  *                      gets -636, rather then a -610.          *
  *                      .*                                      *
  *                      An AL followed by VALUES command allows *
  *                      change  of  limitkey  values  for index *
  *                      objects. An  SQL CODE -636 can occur if *
  *                      more than one value is changed at once, *
  *                      causing overlap of limitkey values.     *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  See Problem Description.
  

Problem conclusion

• When update  Limitkey for indexes the customer would sometimes
  get a -636. That says that the limit key values for successive
  partitions are in strictly ascending or descending order.
  .*
  Code has been changed so that when limitkeys are changed and
  they are higher than the originals. The ALTER statement will
  be in descending order rather than ascending order.
  

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

•    ADB21TAV ADB21X   ADB21XAV
  

Fix information

• Fixed component name

  DB2 ADMIN TOOL

• Fixed component ID

  568851500

Applicable component levels

• R510 PSY UK09412

     UP05/12/14 P F512

• R710 PSY UK09413

     UP05/12/06 P F512

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.