Can't import DDL file that has alter table rename constraint

Question

Hi:
Version 3.1.0.691 on Windows 7 Enterprise 64-bit SP1
I'm trying to import a DDL file with syntax similar to what's below. The <name> notes that I've replaced the actual names for obfuscation purposes.; the real names are in the script.
ALTER TABLE <name>
RENAME CONSTRAINT SYS_C0041150
TO <name2>_CK;
ALTER TABLE <name>
RENAME CONSTRAINT AVCON_1281559518_ACTIV_022
TO <name2>_CK;
I get the following error:
Oracle SQL Developer Data Modeler 3.1.0.691
Oracle SQL Developer Data Modeler Import Log
Date and Time: 2012-01-13 16:29:05 PST
Design Name: <name>
RDBMS : Oracle Database 11g
          All Statements:           819
          Imported Statements:      0
          Failed Statements:           0
          Not Recognized Statements:      819
<<<<< Not Recognized >>>>>
ALTER TABLE <name>
RENAME CONSTRAINT SYS_<name>
TO <name2>_CK
ALTER TABLE <name>
RENAME CONSTRAINT AVCON_1281559518_QVI_A_000
TO <name2>_CK
Thanks for any help you can provide.
Doc

Answer 1

Hi:
The file was indeed comprised of just alter statements. As a test, I trimmed the file down to just one alter statement:
ALTER TABLE <name> RENAME CONSTRAINT SYS_C0041413 TO <name2>_CK;
The output file contained exactly the following, where the <<BEGIN OF FILE>> and <<END OF FILE>> were simply added here for clarity. There was no section called
<<<<< ERRORS >>>>> and the ddl file contained no create table statements.
<<BEGIN OF FILE>>
Oracle SQL Developer Data Modeler 3.1.0.691
Oracle SQL Developer Data Modeler Import Log
Date and Time: 2012-01-16 10:16:42 PST
Design Name: <name>
RDBMS : Oracle Database 11g
          All Statements:           1
          Imported Statements:      0
          Failed Statements:           0
          Not Recognized Statements:      1
<<<<< Not Recognized >>>>>
ALTER TABLE <name> RENAME CONSTRAINT SYS_C0041413 TO <name2>_CK
<<END OF FILE>>
Other info.
When I do an model import, none of the existing check constraint names get captured. Also, if I add names afterwards to two separates models via DM and then compare them. The output DDL shows a drop of the target constraint referencing its name, but the recreation of the not null constraint doesnt reference the source constraint name set for it manually in DM. Here's the example I did and the output ddl.
ALTER TABLE <name>
DROP CONSTRAINT SYS_C0041413
ALTER TABLE <name>
MODIFY ( <column_name> NOT NULL )
That last line should have read as follows due to the constraint_name I added for it in DM.
ALTER TABLE <name>
MODIFY (<column_name> CONSTRAINT <name2>_CK NOT NULL);
In the example directly above, <name2>_CK is the name I explicity set via DM and would have expected the compare to have used to recreated the constraint since it referenced the target constraint name when it constructed the drop constraint syntax.
I believe at least one bug is involved here, most likely two.
The first bug is that model imports are not capturing not null check constraint names.
The second bug is that the source constraint name is not being used when generating the ddl necessary to change the not null constraint name in the target model.
All of this is assuming that I haven't just goofed and forgotten to check a box somewhere telling it to do what I've been talking about here. :-)
Doc