suche 36x36
Neueste VersionenFixList
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Haben Sie Probleme? - Kontaktieren Sie uns.
Kostenlos registrieren anmeldung-x26
Kontaktformular kontakt-x26

DB2 - Problembeschreibung

Problem IT28001 Status: Geschlossen

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

Produkt:
DB2 FOR LUW / DB2FORLUW / B10 - DB2
Problembeschreibung:
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-Zusammenfassung:
****************************************************************
* 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.
Lösung
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
06.02.2019
16.01.2020
16.01.2020
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version