Re: tablespace full problem

Hi,

you asked for sum(bytes), but you have to asked for max(bytes) too and compare it to your next_extent.
if max(bytes) < next_extent, do 'alter tablespace ... coalesce;'. If it dosn't fix your problem,

you must - reorganize your schema( or only this schema objects)
         - or resize datafiles
         - or add datafiles.

Torsten

Lee Ming Fai wrote:
>
> I use the following sql to check the free space in each tablespace datafile
> :
>
> select t1.file_id, t1.tablespace_name, ti.bytes,sum(t2.bytes)
> from dba_data_files t1,dba_free_space t2
> where t1.file_id=t2.file_id
> group by t1.file_id, t1.tablespace_name, t1.bytes
> order by t1.tablespace_name, t1.file_id;
>
> FILE_ID TABLESPACE_NAME BYTES FREE BYTES
> ------- --------------- ------------- ----------------
> 11 CIND_TS 1,048,576,000 149,708,800
>
> and found that one of the tablespace call CIND_TS has 149,708,800 bytes
> free.
>
> The problem is I found an error message in the alert log, an index which the
> next extent is only 25M was unable to entend in this tablespace!
>
> can anyone tell me how to solve this problem? Thanks!
Received on Fri Jul 09 1999 - 06:24:29 CDT