Basically you should drop the constraints of type 'R' first, then drop the constraints
of type 'P' and 'U'. See the CONSTRAINT_TYPE in the USER_CONSTRAINTS view.
>>> [EMAIL PROTECTED] 05/01/01 05:50PM >>>
Hi -
When dropping and/or re-applying constraints for an entire schema, is there
a dictionary table that can be queried (or some other way) to determine
constraint dependencies - or do you just keep running the script until you
do not get those errors? I would like to be able to identify the order that
the constraints should be dropped (or added) so that I can write a script to
be automated ( for example, to refresh test data from production).
If anyone has any good ideas on how to do this, I'd really be interested in
hearing from you.
Thanks -
Lisa
--
Please see the official ORACLE-L FAQ: http://www.orafaq.com
--
Author: Tim Sawmiller
INET: [EMAIL PROTECTED]
Fat City Network Services -- (858) 538-5051 FAX: (858) 538-5051
San Diego, California -- Public Internet access / Mailing Lists
--------------------------------------------------------------------
To REMOVE yourself from this mailing list, send an E-Mail message
to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in
the message BODY, include a line containing: UNSUB ORACLE-L
(or the name of mailing list you want to be removed from). You may
also send the HELP command for other information (like subscribing).
