Re: Locally Managed Tablespaces - any cons???

On Tue, 7 Aug 2001 21:20:37 -0600, "Ron Gardiner" <rongardiner_at_powersurfr.com> wrote:

>New for 8i (I believe) is locally managed tablespaces...
>
>From what I've read, sounds like there is no reason NOT to use them. Can
>they be used for all types of TS?... rollback segs, temporary, how about
>system itself?
>
>Any feedback would be appreciated!
>
>

I've used them extensively and found two problems.

1. If you undersize the extents in a uniformly sized LMT, it can be very difficult to change if you're dealing with large segments. We use the extent size to determine when we report on segments that cannot allocate their next extent. We try to size the extents so that each one will last several days, giving us several days warning when we need to increase the size of the tablespace. One table with nearly 200 million rows was underestimated in the growth rate. It's grabbing several extents per day and our daily report is now inadequate. Changing the extent size on this tables tablespace has proved nearly impossible because of it's size and 24x7 usage.
2. If a LMT has multiple datafiles with autoextend turned on, and oracle cannot extend one, it won't try to extend another. Inserts simply fail. I beleive this is a bug. The same did NOT happen with DMTs. -- Chuck Hamilton chuck_hamilton_at_yahoo.com

"Do not be deceived, God is not mocked; for whatever a man sows, this he will also reap." (Gal 6:7 NASB) Received on Wed Aug 08 2001 - 07:58:09 CDT