Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Usenet -> c.d.o.server -> Re: migrating to locally managed tablespaces

Re: migrating to locally managed tablespaces

From: Karen Abgarian <abvk_at_ureach.com>
Date: Mon, 20 Jan 2003 05:17:10 GMT
Message-ID: <3E2B8658.A39A45F@ureach.com>


> 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.
>
>

It would definitely be best to keep the size of c_ts# cluster down, because things get complicated if a large amount of free extents is released as result of relocation from DMT to LMT. I would check the number of extents to be released in the source DMT tablespace and if the number is too large, I would do one or several objects at a time, coalescing the source tablespace in between.

Interestingly, tomorrow I will have to deal with results of such a reorg. There is about million of rows in fet$ and if I were to fire drop on a tablespace, it would take about two weeks with major impact on the database performance. As result, the source tablespace is still there, the monitoring (packaged application which checks dba_free_space) is not working, and I probably have to rebuild the whole database. Ideas how to deal with this are appreciated, by the way.

The funny part about it is that the project to move to LMT from DMT has already completed and reported as successful. Received on Sun Jan 19 2003 - 23:17:10 CST

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US