Re: Moving databases and adding table partitions in process

If you have 8.1.5 you would be able to
do the export with a WHERE clause
to bypass the redundant data.

Your best strategy is probably to do a
Create table as as select nologging to
create a new table holding the desired
data. Create the partitioned table on
the new server, muck about with object
names and import the new table 'ignoring errors'.

Alternatively, export the entire table,
create a partitioned table with its lowest boundary set to exclude the data you
don't want, import the table 'ingore errors'.

The data you don't want can then be eliminated by dropping the bottom partition.

--

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

CA wrote in message <39592FF1.99010FDD_at_yahoo.com>...


>Running Oracle 8.0.5.2 on Solaris 2.7

>We are moving our databases to a new server, and one of the databases

>has some pretty large tables that we have decided need to have data

>purged from them, only keeping a quarters worth of data online.

>

>The best approach appears to me to build the tables with partittions,

>thus my question:

>

> Will export / import be able to accomplish this?  i.e.  The approach I

>would like to take, would be to build the new partitons for the tables

>on the new database / server, and then import the data, hopefully only a

>quarters worth.  Can this be accomplished via export/import? (will the

>data values not within the specified partiton be rejected?).

>

>I"ve looked thru the books, and haven't found the answer yet, but I'll

>keep digging.

>TIA

>

>