Oracle FAQ | Your Portal to the Oracle Knowledge Grid |
![]() |
![]() |
Home -> Community -> Usenet -> c.d.o.server -> Re: Locally Managed vs Dictionary managed tablespaces
I guess you're after doing the 'where a segment's next extent is bigger than
the largest piece of free space left in a tablespace' test?
True, that can't be done, even in 9i, because the next extent field is null there too. But I've always thought it was bit late to be wondering about such things when there's only one new extent to go before disaster!
Hence, I use this:
SELECT TABLESPACE_NAME,
ROUND(SUM(TOTAL_MB)-SUM(FREE_MB)) MB_USED, ROUND(SUM(TOTAL_MB)) MB_SIZE, ROUND((SUM(TOTAL_MB)-SUM(FREE_MB))/SUM(TOTAL_MB)*100) PCT_FULL, ROUND(SUM(MAX_MB) - (SUM(TOTAL_MB)-SUM(FREE_MB))) MB_FREE, ROUND(SUM(MAX_MB)) MB_MAXSIZE, ROUND((SUM(TOTAL_MB)-SUM(FREE_MB))/SUM(MAX_MB)*100) PCT_UTILFROM
Full details at the link below (Tips, Administration, under 'tablespaces').
Regards
HJR
-- Oracle Resources : http://www.geocities.com/howardjr2000 ======================================== "Raymond" <r_h_at_hetnet.nl> wrote in message news:9rsabv$pe5$1_at_news1.xs4all.nl...Received on Thu Nov 01 2001 - 14:30:18 CST
>
> One disadvantage of LMTS's I noticed: it is hard to predict the
> space needed for the next extent of segments in such a tablespace.
> The next_extent column in dba_segments is NULL (at least in V8.1.7 it is,
> don't know about 9.0.1).
> Monitoring this vital space requirement is much easier on DMTS's.
>
> Anyone with a query that reports the free space deficit in LMTS's ?
>
> Raymond.
> Oracle DBA.
>
>
![]() |
![]() |