Re: migrating to locally managed tablespaces

How much of the database is still read-write ?

If this is a data warehouse with large amounts of read-only data, I don't think I would bother to migrate the read-only bits.

To migrate the read-write bits, the best strategy is simply to create new tablespaces, and move data segments into them. Don't bother to use the dbms_space_admin migration procedure as it does only half the job - the tablespaces become bitmapped, but they are still "user-managed" rather than locally managed.

It would probably be best to sort out one tablespace at a time, then drop the old empty tablespace before doing the next one, as this may keep the size of the ts# cluster down.

--
Regards

Jonathan Lewis
http://www.jlcomp.demon.co.uk

Coming soon a new one-day tutorial:
Cost Based Optimisation
(see http://www.jlcomp.demon.co.uk/tutorial.html )

Next Seminar dates:
(see http://www.jlcomp.demon.co.uk/seminar.html )

____England______January 21/23
____USA_(CA, TX)_August


The Co-operative Oracle Users' FAQ
http://www.jlcomp.demon.co.uk/faq/ind_faq.html





Frederic Payant wrote in message ...


>Hi,

>

>Oracle 8.1.7.0 on Solaris 8 (big) box

>I'll have to drive a migration on a huge production database (2

>instances, 700 GB) from dictionary managed TBS to localy managed

>tablespaces.

>

>It's the first time I've to do such a job on a production

environment,


>so :

>How can I proceed, are they tools to help, is there an order to

follow


>?

>What kind of troubles can I meet ?

>Is there any documentation on this task ?

>

>Thanks for your help

>Regards

>Frederic PAYANT - junior DBA ;-)