Re: LMT not listed in DBA_FREE_SPACE

From: NoResult <dj_noresult_at_hotmail.com>
Date: 18 Feb 2003 22:08:09 GMT
Message-ID: <Xns9326EB1169948djnoresult@194.109.133.20>

"Niall Litchfield" <niall.litchfield_at_dial.pipex.com> wrote in news:3e52ab5c$0$371$cc9e4d1f_at_news.dial.pipex.com:

> "NoResult" <dj_noresult_at_hotmail.com> wrote in message
> news:Xns9326CD42EE529djnoresult_at_194.109.133.20...

>> Please note that this does not include auto extend. If a datafile is
>> set to auto extend you should look in dba_data_files for the maximum
>> size of the data file.

>
>
> which is one reason not to use autoextend?
>

>> Also exents should fit entirely in free blocks. In locally managed
>> tablespaces the next extent of a segment (table, index, etc.) can
>> grow up to 64 M.

>
> which, more to the point is a perfect reason to use locally managed
> tablespaces, with the uniform extent size clause. then you know that
> if space is free a object can extend.
>
>
> --
> Niall Litchfield
> Oracle DBA
> Audit Commission UK
> *****************************************
> Please include version and platform
> and SQL where applicable
> It makes life easier and increases the
> likelihood of a good answer
> ******************************************
>
>
>

Previous post was not ment to prevent people from using it. Locally managed tablespaces make life easir in many ways...

Greetz, NoResult :-) Received on Tue Feb 18 2003 - 16:08:09 CST