Re: SQL*Loader question

For direct load, the constraints that remain enabled are the not null, unique and primary keys. Not nulls get rejected at runtime, and the unique constraints get checked after the load. If there are repeat values after the load in a unique column, the rows stay, however the constraint (index) does not enable. Check constraints and foreign keys are disabled prior to the load, and you must re-enable them after (I think there is some syntax you can use in the control file to do this automatically, look ou 'reenable'). Your indexes should be fine after the load.

Mike

• Original Message ----- From: "Oak, Sameer" <Sameer.Oak_at_CWUSA.COM> To: "Multiple recipients of list ORACLE-L" <ORACLE-L_at_fatcity.com> Sent: Tuesday, June 13, 2000 5:50 PM Subject: SQL*Loader question

> Hi gurus
>
> This might be simple question for gurus..
>
> When one users direct load in SQL*loader what happens to the constraints
on
> that particular table????
> What I mean is do we have to reapply the constraints & rebuild the
> indexes????
>
> Also what about triggers on the table????
>
> Tia
> $ameer
>
>
> --
> Author: Oak, Sameer
> INET: Sameer.Oak_at_CWUSA.COM
>
> 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: ListGuru_at_fatcity.com (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).
Received on Wed Jun 14 2000 - 08:23:26 CDT