IBM Support

PI87838: THE PHYSICAL PARTITION NUMBER CONTAINED IN THE MESSAGE TEXT OF SQLCODE -636 ON ALTER TABLE OF LIMIT KEY IS NOT CORRECT IN V12.

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • In V12, when sqlcode -636 is issued on ALTER TABLE of limit key,
    the physical partition number in the error description is not in
    accordance with the number in the ALTER statement.
    

Local fix

  • N/A
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * All DB2 12 for z/OS users of ALTER TABLE                     *
    * ALTER PARTITION.                                             *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * ALTER TABLE ALTER PARTITION of a                             *
    * limit key value issues SQLCODE -636                          *
    * with incorrect token partition 0                             *
    * instead of the correct partition                             *
    * number.                                                      *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Apply corrective PTF when available                          *
    ****************************************************************
    When executing ALTER TABLE ALTER PARTITION where the specified
    limit key value overlaps the range of adjacent logical
    partitions, SQLCODE -636 is issued with incorrect token
    partition number 0 instead of the correct partition number.
    

Problem conclusion

  • DB2 has been modified such that SQLCODE -636 issued with the
    correct partition number for an ALTER TABLE ALTER PARTITION of
    limit key statement where an invalid limit key specified
    overlaps the range of adjacent logical partitions.
    
    ADDITIONAL KEYWORDS:
    SQLALTER
    SQLCODE636
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI87838

  • 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

    2017-09-25

  • Closed date

    2017-10-30

  • Last modified date

    2017-12-02

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

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

    UI51547

Modules/Macros

  • DSNXIAB7
    

Fix information

  • Fixed component name

    DB2 OS/390 & Z/

  • Fixed component ID

    5740XYR00

Applicable component levels

  • RC10 PSY UI51547

       UP17/11/14 P F711

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"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"12.0","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"12.0","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
02 December 2017