Printable View
I do a 35G data import. Importing the data is Ok. but 80% of the time is spent on enabling constraints..I have 6000 constaints.
I would like to do a constraints=n import and then enable the constraints novalidate
Question. If I do that, would the constraints be created? just not validated/enabled?
Thanks
You are correct.
Import with no constraints then create constraints enable/novalidate which means you trust the data already in the tables but you want Oracle to check constraints from now on.
Try it then query to see if the constraints are there. I imagine that the import won't create the constraints if you say constraint=n on the import command. A better option would be to use transportable tablespaces. That is assuming that your situation qualifies. You basically need each tablespace to have only constraints to objects within that tablespace and you need to move the tablespace to a file system that is compatible with were you took it from. But if it works it would not need to reenable all of the constraints.Quote:
Originally Posted by Tuma
Another option would be to use dbms_metadata to get the ddl for the constraints, and edit that ddl to make it create the constraints with the novalidate flag. You can then run that after the import to create the constraints. Just make sure that the constraints are valid on the source database.
thanks fellows...