Using SQL Developer Data Modeler run into DDL Check Constraint Import Issue Results in Portions of the Check Constraint Added as Columns in the Model
(Doc ID 2763454.1)
Last updated on JUNE 24, 2021
Applies to:
Oracle SQL Developer Data Modeler - Version 20.3 and laterInformation in this document applies to any platform.
Symptoms
Environment
---------------------
SQL Developer Data Modeler 20.3
Database 12.2.0.1.0
Windows 10 64-bit
Problem
-------------
Importing this DDL in Data Modeler 20.3 results in portions of the check constraint added as columns in the model.
Returns
------------------
Then see Relational Model showing
test_tab2
*col1 VARCHAR2 (20)
*col2 VARCHAR2 (20)
*col3 VARCHAR2 (20)
col4 VARCHAR2 (32)
col5 VARCHAR2 (60)
'xxxxxx UNKNOWN
'xxxx UNKNOWN
Works
-----------------
Working via DDL file import if the parenthesis in the constraint values are removed.
Changes
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Symptoms |
Changes |
Cause |
Solution |
References |