Re: The simple "Can I extend" question

I think this is another indication of Oracle Corp catering for the black box application with no DBA in sight, the database is on single SAME array, and every file is AUTOEXTEND.

The extent size is small and grows by a factor of 8 or 16 when it grows. So when you install product X with 3,000 tables of which you are going to use 600 and nobody can tell you which ones (e.g. Applications) - then you don't waste a huge amount of space when you install, but the tables you do use grow to suitable sized extents very quickly without leaving a huge mess behind them.

And since all your files will (by default) be AUTOEXTEND, and "disk is cheap", you don't need to know the next extent, because it will always fit. (And if it doesn't, the operation will suspend and page the dba to come and fix things quick. (NB for anyone who hasn't had time to read the manuals yet, that last comment wasn't a joke).

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

Author of:
Practical Oracle 8i: Building Efficient Databases

Next Seminar - Australia - July/August
http://www.jlcomp.demon.co.uk/seminar.html

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



Connor McDonald wrote in message <3CB33EF4.2019_at_yahoo.com>...


>Just wondering what people are doing out there to answer the question

>"Can segment X take a new extent?"...

>

>Seems easy enough....for segments in a tablespace that is:

>

>1) Dictionary-managed:  xxx_SEGMENTS.NEXT_EXTENT versus DBA_FREE_SPACE

>2) Converted LMT:       ditto

>3) Uniform LMT:         trivial (simple existence check in

>DBA_FREE_SPACE)

>4) System-alloc LMT:    hmmmmmmmmmm

>

>(xxx_SEGMENTS.NEXT_EXTENT is null in (4)

>

>--

>==============================

>Connor McDonald

>

>http://www.oracledba.co.uk

>

>"Some days you're the pigeon, some days you're the statue..."