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: Locally vs dictionary managed tablespaces

Re: Locally vs dictionary managed tablespaces

From: Connor McDonald <connor_mcdonald_at_yahoo.com>
Date: Wed, 08 Aug 2001 18:51:54 +0100
Message-ID: <3B717C3A.4E86@yahoo.com>

Rene Nyffenegger wrote:
>
> Hi
>
> Because of another thread in this NG, I wanted to find out
> about locally managed tablespaces. The key phrase I found is:
>
> Locally managed tablespaces track all extent information in the tablespace
> itself, using bitmaps, resulting in the following benefits:
> <list of benefits, many starting with improved...>
>
> What does it mean, the extent information is in the tablespace itself.
> Where is it stored in dictionary managed tablespaces? What is the
> extent information anyway?
>
> Tnx
>
> Rene
>
> --
> Recherchen im Schweizerischen Handelsamtsblatt:
> http://www.adp-gmbh.ch/SwissCompanies/Search.php3

By default two tables hold all the bits and pieces (UET$, FET$) being a list of used and free extents respectively. Obviously as you add/remove extents, these tables have to be updated. Similarly if you coalesce then these tables could be updated. What you quickly end up with if you're going hard on the extent (de)allocation, is a bottleneck.

A locally managed tablespace plonks this information in a bitmap in each file, thus removing the contention point. I consider dictionary managed tablespace to be virtually obsolete..

hth
connor

-- 
==============================
Connor McDonald

http://www.oracledba.co.uk

"Some days you're the pigeon, some days you're the statue..."
Received on Wed Aug 08 2001 - 12:51:54 CDT

Original text of this message

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