You probably can coalesce ur tablespace if it is fragmented and then try
resizing.
--
Murali
"If u haven't crashed your server you haven't worked enough"
Sybrand Bakker <postbus_at_sybrandb.demon.nl> wrote in message
news:950044344.10183.0.pluto.d4ee154e_at_news.demon.nl...
> They can be resized, yes, but that means there most be no data beyond the
> new highwatermark of that file. You will need dba_extents to see which
space
> is actually used and which not. If sys is non-contiguous in your database
> you have bad luck, because that can be resolved only when rebuilding the
> database.
> To resize the database use alter database datafile '<your filename>'
resize
> <x> M.
>
> Hth,
>
> Sybrand Bakker, Oracle DBA
>
> Jay Scheiner <jxs_at_wolpofflaw.com> wrote in message
> news:38a0af56.1875588735_at_news.erols.com...
> > Perhaps I was not clear enough. I have moved the tables to another
> > tablespace (well, I'm working on it, and learning as I go). I dropped
> > the tables in the SYSTEM tablespace, but the files on the disk drive
> > are still huge. Can the files be compated/purged of data that is no
> > longer logically there but perhaps still physically present?
> >
> > On Tue, 08 Feb 2000 12:16:50 -0800, rockcogar
> > <rock_cogarNOroSPAM_at_my-deja.com.invalid> wrote:
> >
> > >I assume that you are referring to data that does not belong in
> > >the system tablespace, like that of another user ?
> > >
> > >If so, make sure "that user" has their default tablespace set
> > >for their own tablespace (use ALTER USER ..., to fix it). The
> > >(re)CREATE newtable as select * from oldtable' the table(s)
> > >{using different names} so they will go in the correct
> > >tablespace. DROP tables that are in the old tablespace. RENAME
> > >the tables.
> > >
> > >
> > >* Sent from RemarQ http://www.remarq.com The Internet's Discussion
> Network *
> > >The fastest and easiest way to search and participate in Usenet - Free!
> > >
> >
>
>
>
Received on Tue Feb 08 2000 - 20:02:25 CST
