Re: BIN$ tables still exist after DROP and/with PURGE in tablespace.

limyujeen_at_gmail.com wrote:
> I'm facing a very unique problem and I say unique because I can't seem
> to find a duplicate case as the one I am facing.
>
> -> Oracle, Release 10.1.0.4.0
>
> The situation is like this... some very large tables have been dropped
> and the recycle bin for that schema has been purged.
>
> When viewing the objects in the tablespace, I can still see "BIN
> $LZWEAt3ATFngRAASeZ5J1Q==$0" with the OWNER of the schema which I have
> just purged!
>
> I've queried the recyclebin. And no rows were returned. I've queried
> the dba_recyclebin, some rows were returned, but the specific BIN$
> table that I've mentioned above did not exist.
>
> The big catch is that the tablespace is full. The tables that were
> dropped consisted mainly of table partitions. They were purged but
> still use up space in the tablespace having the names such as BIN$...
>
> Is there a way I can purge these system files from the tablespace?
>
> There's no data in the recycle bin, what else can I do to drop the
> unwanted data from the tablespace?
>

You might want to try to sign on as SYSDBA and issue "purge dba_recyclebin;". See if that gets rids of those objects. Be warned that this command will purge all recyclebins of all owners.

HTH,
Brian

-- 
===================================================================

Brian Peasland
dba_at_nospam.peasland.net
http://www.peasland.net

Remove the "nospam." from the email address to email me.


"I can give it to you cheap, quick, and good.
Now pick two out of the three" - Unknown

-- 
Posted via a free Usenet account from http://www.teranews.com