DB2 - Problem description
Problem IT28001 | Status: Closed |
"ALTER SEQUENCE SEQUANCE_NAME RESTART WITH" - STATEMENT IN DB2LOOK OUTPUT HAS INCORRECT VALUES | |
product: | |
DB2 FOR LUW / DB2FORLUW / B10 - DB2 | |
Problem 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. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * ALL * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to Db2 11.1 Mod 4 Fixpack 5 or higher * **************************************************************** | |
Local Fix: | |
Use sequences up to 15 digits max. | |
Solution | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 06.02.2019 16.01.2020 16.01.2020 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) |