Re: How to disable ALL constraints ?

From: DI Karl Heinz Hörmann <kh.hoermann_at_penta.at>
Date: Tue, 25 Jan 2000 04:07:23 +0100
Message-ID: <86j3nf$b2$1@newsmaster01.magnet.at>

Jerry Gitomer wrote <388BDF7A.BC8AAA01_at_erols.com>...
>Jannette wrote:
>>
>> From Oracle documentation:
>> "Suggestion: ... it is a good idea to disable referential constraints
>> when importing into an existing table. You can then re-enable the
>> constraints after the import is completed."
>
>Regardless of how you disable them be sure to check for inalid
>constraints before you start and fix them before you do your import.
>Also after you enable constraints after the import check for valid
>constraints again since Oracle will not enable a constraint that is
>invalid. So if you find one you have to fix it.

why not use the exception clause ??
If you enable a constraint, Oracle enforces it by applying it to all data in the table. All table data must satisfy an enabled constraint.

exceptions_clause:

EXCEPTIONS INTO
specifies a table into which Oracle places information about rows that violate the integrity constraint. The table must exist on your local database before you use this option. If you omit schema, Oracle assumes the exception table is in your own schema.

regards Received on Mon Jan 24 2000 - 21:07:23 CST