weird table names

[BeefStu]

I have some weird table names associted with some partitions (see below),
can somebody explain what this means or how I can get real table_name if
possible.

FYI, I am running Oracle 10.2.0.4 on AIX 5.3

select table_owner, table_name from dba_tab_partitions where partition_name = 'BATCH_REQUEST_20110126';

TABLE_OWNER TABLE_NAME
XXX BIN$mYQZdH7ecLzgQwqqGERwvA==$0
XXX BIN$mYQZdH7jcLzgQwqqGERwvA==$0
XXX BIN$mYQZdH7ZcLzgQwqqGERwvA==$0
XXX BIN$mYPfw33oIBrgQwqqGEQgGg==$0
XXX BIN$mYWxVX064cTgQwqqGEThxA==$0
XXX BIN$mZfa5Sgv0TTgQwqqGETRNA==$0

[LKBrwn_DBA]

Those are from the "recycle bin", you can purge if not needed.

[BeefStu]

Am I missing something?

sqlplus '/ as sysbda'

SQL> SELECT * FROM RECYCLEBIN;

no rows selected

SQL> SELECT * FROM USER_RECYCLEBIN;

no rows selected

SQL> PURGE RECYCLEBIN;

Recyclebin purged.


There were no rows in the recyle bin as you can see fron the above
queries. Is there another approach I can take to remove these entries
or corrletate them back to a table than drop the table.

I am not using FRA. Thanks you all for your input

[stecal]

Whose recyclebin are you trying to clear? Sys or XXX?

http://download.oracle.com/docs/cd/E...htm#ADMIN11681

Users can purge the recycle bin of their own objects, and release space for objects, by using the following statement:

PURGE RECYCLEBIN;
If you have the SYSDBA privilege, then you can purge the entire recycle bin by specifying DBA_RECYCLEBIN, instead of RECYCLEBIN in the previous statement.

[BeefStu]

Stecal, PURGE DBA_RECYCLEBIN did the trick and cleaned up the
items for me.

The following query gives me this result

select TABLESPACE_NAME, sum(BYTES)/1024/1024/1024 Total_free_space_GB, max(BYTES)/1024/1204 largest_free_extent_GB
from dba_free_space group by TABLESPACE_NAME


Tablespace Total free space Largest Free Extent
GB GB

DE10M_2 105.6640625 11.6279070

Is there a way I can compress all the space in the tablespace other
than moving each paritition of a table or exporting, dropping objects,
re-creating tablespace? What I am looking to do is have my largrest free
extent equal to total free space or is this really not worth the effort.

Thanks in advance to all who answer

[stecal]

Not worth the effort. Let Oracle manage extents (or use uniform).

A locally managed tablespace can have either uniform extent sizes or variable extent sizes determined automatically by the system:

For uniform extents, you can specify an extent size or use the default size of 1 MB. All extents in the tablespace are of this size. Locally managed temporary tablespaces can only use this type of allocation.

For automatically allocated extents, Oracle Database determines the optimal size of additional extents.