Re: First time Table reorganize procedure

A couple of details:

1. compress=y is probably a bad idea. This will leave the table as a single, potentially very large, segment, which you may be unable to create at the import stage.

As a longer-term strategy you should consider migrating your tablespace to a uniform extent size, and create the table prior to import specifying that size (initial = next, pctincrease = 0 if default for tablespace is not zero).

2) If this table is the parent table in parent/child relationship, then the cascade constraints will eliminate the foreign key constraints from the child tables. Nothing in your process will rebuild them. List them from the user_constraints view before dropping and rebuild them by hand afterwards.

--

Jonathan Lewis
Yet another Oracle-related web site: www.jlcomp.demon.co.uk

Kevin A Lewis wrote in message
<0eS53.154$pl3.2651_at_newreader.ukcore.bt.net>...
>I need to check my procedure for reorganizing a single table.
>
>1 :- Export the table
>
> exp user/password tables=(XXX) file=table.dmp compress=y indexes=y;
>
>2 :- Drop the table
>
> Drop table XXX cascade constraints
>
>3 :- Import the table data
>
> imp user/password file=table.dmp indexes=n indexfile=index.dmp
>
>4 :- Import the index data (subsequent to the table create)
>
> sqlplus user/password_at_dbase
> @index.dmp;
> exit
>
>Never having done this before I want to be extra sure this works, allows
for
>all possible situations and for inter object dependencies.
>
>Regards
>--
>Kevin A Lewis (BOCM PAULS LTD - Animal Feed Manufacturer - Ipswich England)
> <KevinALewis_at_HotMail.com>
>
>The views expressed herein by the author of this document
>are not necessarily those of BOCM PAULS Ltd.
>
>
Received on Fri Jun 04 1999 - 11:20:37 CDT