Re: Locally Managed Tablespace and ASSM

From: joel garry <joel-garry_at_home.com>
Date: Wed, 23 Jan 2008 16:33:26 -0800 (PST)
Message-ID: <77b182a9-39b8-4bb1-bbda-a88e91ad9418@1g2000hsl.googlegroups.com>


On Jan 22, 5:33 pm, Peter Teoh <htmldevelo..._at_gmail.com> wrote:
> In my 10gR2:
>
> SQL> select extent_management, segment_space_management,
> tablespace_name from dba_tablespaces;
> LOCAL      MANUAL SYSTEM
> LOCAL      MANUAL UNDOTBS1
> LOCAL      AUTO   SYSAUX
> LOCAL      MANUAL TEMP
> LOCAL      AUTO   USERS
> LOCAL      AUTO   EXAMPLE
> LOCAL      AUTO   ART_TS
>
> In spite of all the big stories and advantages of ASSM, why is Oracle
> 10gR2 still using MANUAL for segment_space_management?
>
> Why is PCTUSED, NEXT, FREELISTS is not needed in LMT?   The main
> feature of LMT is bitmap managed freelists, vs the dictionary managed
> freelists in prior version.   But I cannot understand why the PCTUSED,
> NEXT, FREELISTS feature can be taken away with the availability of a
> new feature, as they can surely co-exists.   If it is taken away for
> simplification of management - then it is fine.
>
> I had to agree that all these parameters are really very
> complicated.   Now that it is removed, good - it has been replaced by
> some internal formula.   So how are these PCTUSED, NEXT, FREELISTS etc
> formula implemented?   Can it be customized or modified by us - in
> future?

Also see http://www.orafaq.com/maillist/oracle-l/2003/11/11/0847.htm and the thread it is in.

jg

--
@home.com is bogus.
http://news.bbc.co.uk/1/hi/business/7181741.stm
Received on Wed Jan 23 2008 - 18:33:26 CST

Original text of this message