PUBLIC:Re: Duplicate check constraints on the same column

The problem is (or might be...) that Oracle creates the constraint names with a sequence number if there is no name supplied. If you do now an export of the schema (or table) without constraints=No, and you do an import into the same schema (without prior drop of the tables or constraints in this case), Oracle adds the same constraints again with a different sequence number (the reason is , is guess, that Oracle writes only the alter table statement add constrain(..) to the export file). in cases of named constraints Oracle would get an error during import when the name already exists.

Hope not to confusing..

eugen ;-) Received on Fri Nov 28 1997 - 00:00:00 CST