IBM Support

IT28001: "ALTER SEQUENCE SEQUANCE_NAME RESTART WITH" - STATEMENT IN DB2LOOK OUTPUT HAS INCORRECT VALUES

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 

APAR status

  • Closed as program error.

Error description

  • DDL for sequence (db2look.mimic_sequence.sql)
    
    CREATE SEQUENCE "MYSEQ" AS BIGINT
            MINVALUE 100000000000000000 MAXVALUE 199999999999999999
            START WITH 100000000000000000 INCREMENT BY 1
            NO CACHE CYCLE NO ORDER;
    
    ALTER SEQUENCE "MYSEQ" RESTART WITH
    100000000000522496;
    
    
    
    Steps to reproduce this problem :
    
    db2 "ALTER SEQUENCE "MYSEQ" RESTART WITH
    10000000000555555"
    
    $ db2look -d sample -e | grep 'ALTER SEQUENCE'
    ..
    ALTER SEQUENCE  "MYSEQ" RESTART WITH
    10000000000555556;
    ---
    $ db2 "ALTER SEQUENCE "MYSEQ" RESTART WITH
    10000000000333333"
    
    
    $ db2look -d sample -e | grep 'ALTER SEQUENCE'
    
    ALTER SEQUENCE "MYSEQ" RESTART WITH
    10000000000333332;
    ..
    
    Db2look is not handling DECIMAL(31,0) datatype properly. When
    the sequence is too large, calculations are done incorrectly,
    and precision is lost.
    

Local fix

  • Use sequences up to 15 digits max.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * ALL                                                          *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * See Error Description                                        *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Upgrade to Db2 11.1 Mod 4 Fixpack 5 or higher                *
    ****************************************************************
    

Problem conclusion

  • First fixed in Db2 11.1 Mod 4 Fixpack 5
    

Temporary fix

Comments

APAR Information

  • APAR number

    IT28001

  • Reported component name

    DB2 FOR LUW

  • Reported component ID

    DB2FORLUW

  • Reported release

    B10

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2019-02-06

  • Closed date

    2020-01-16

  • Last modified date

    2020-01-16

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

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

Fix information

  • Fixed component name

    DB2 FOR LUW

  • Fixed component ID

    DB2FORLUW

Applicable component levels

  • RB10 PSN

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSEPGG","label":"Db2 for Linux, UNIX and Windows"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"11.1","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
16 January 2020