Oracle FAQ | Your Portal to the Oracle Knowledge Grid |
![]() |
![]() |
Home -> Community -> Usenet -> c.d.o.misc -> Re: Temporarely disabeling constraints
Be alert to the fact that when you disable primary key and unique key constraints, the associated index Oracle built gets blown away. When you re-enable these constraints, if you don't include the name of the constraint and its index storage parameters Oracle will name it SYS_C* and use default storage values for the tablespace. - djc
Ian Cary <cary_at_gatwick.geco-prakla.slb.com> wrote in article
<34461F51.E180018F_at_gatwick.geco-prakla.slb.com>...
> I believe the syntax your are looking for is;
>
> alter table <table_name> disable constraint <constraint_name>;
>
> with enable replacing disable for the reverse operation.
>
> If you are unsure of the constraint_name you require, al list of all the
> constraints for the current user can be found in the user_constraints
view,
> alternatively if the current user is not the table ower the
all_constraints
> view lists all constraints accessible by the user.
>
> Hope this helps,
>
> Ian
>
>
Received on Fri Oct 17 1997 - 00:00:00 CDT
![]() |
![]() |