DB2 - Problem description
| Problem IT05282 | Status: Closed |
DB2_COMPATIBILITY_VECTOR REGISTRY VARIABLE VALUE SET TO ORA CAN GENERATE WRONG MIN AND MAX VALUES FOR CREATE SEQUENCES DDL | |
| product: | |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 | |
| Problem description: | |
When the DB2_COMPATIBILITY_VECTOR registry variable is set to
ORA then the CREATE SEQUENCE DDL generated by the DB2LOOK
command can contains wrong MIX and MAX values.
Example:
db2set DB2_COMPATIBILITY_VECTOR=ORA
db2stop force
db2start
db2 create db oradb
db2 connect to oradb
db2 "CREATE SEQUENCE "TEST"."JOB_TEST_SEQ1" AS DECIMAL(27, 0)
MINVALUE 10 "
db2 "CREATE SEQUENCE "TEST"."JOB_TEST_SEQ2" AS DECIMAL(27, 0)
MINVALUE -1"
db2look -d oradb -e
---------------------------------
-- DDL Statements for Sequences
---------------------------------
CREATE SEQUENCE "TEST"."JOB_TEST_SEQ2" AS DECIMAL(27, 0)
MINVALUE -1 MAXVALUE 999999999999999999999999999
START WITH -1 INCREMENT BY 1
CACHE 20 NO CYCLE NO ORDER;
CREATE SEQUENCE "TEST"."JOB_TEST_SEQ1" AS DECIMAL(27, 0)
MINVALUE -10 MAXVALUE 999999999999999999999999999
START WITH -10 INCREMENT BY 1
CACHE 20 NO CYCLE NO ORDER;
As can be seen from DDL output generated by the db2look command,
the DDL for "TEST"."JOB_TEST_SEQ1" is incorrect, while the
expected DDL is as below.
CREATE SEQUENCE "MHISSMSB"."JOB_DEFN_PARAM_SEQ" AS DECIMAL(27,
0)
MINVALUE 10 MAXVALUE 999999999999999999999999999
START WITH 10 INCREMENT BY 1
CACHE 20 NO CYCLE NO ORDER; | |
| Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * ALL * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * First Fixed in DB2 10.5 Fix Pack 7 * **************************************************************** | |
| Local Fix: | |
db2set db2set DB2_COMPATIBILITY_VECTOR= | |
| Solution | |
First Fixed in DB2 10.5 Fix Pack 7 | |
| Workaround | |
not known / see Local fix | |
| Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 30.10.2014 09.05.2017 09.05.2017 |
| Problem solved at the following versions (IBM BugInfos) | |
| Problem solved according to the fixlist(s) of the following version(s) | |
| 10.5.0.7 |
|