BIN$ Rows In Sys.obj$ After Purge Of Recyclebin
(Doc ID 1506286.1)
Last updated on JULY 29, 2019
Applies to:
Oracle Database - Enterprise Edition - Version 10.2.0.4 to 11.2.0.2.0 [Release 10.2 to 11.2]Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Cloud Exadata Service - Version N/A and later
Information in this document applies to any platform.
Symptoms
After partitioned table dropped, and recyclebin purged obj$ and dba_segments show the dropped table as BIN$...., and space is not released.
select owner,object_name from dba_recyclebin;
no rows selected
SQL> select owner#,name,status from sys.obj$ where name like '%BIN$%';
OWNER# NAME STATUS
---------- ------------------------------ ----------
92 BIN$iF05x2CIYJbgQwoJMvpglg==$0 1
92 BIN$iF05x2CIYJbgQwoJMvpglg==$0 1
92 BIN$iF05x2CIYJbgQwoJMvpglg==$0 1
....
SQL> select owner,segment_name,segment_type from dba_segments where segment_name like 'BIN$%';
OWNER SEGMENT_NAME SEGMENT_TYPE
------------------------------ --------------------------------------------------------------------------------- ------------------
SYSADM BIN$iF05x2CIYJbgQwoJMvpglg==$0 TABLE PARTITION
SYSADM BIN$iF05x2CIYJbgQwoJMvpglg==$0 TABLE PARTITION
SYSADM BIN$iF05x2CIYJbgQwoJMvpglg==$0 TABLE PARTITION
........
Same entries in dba_tab_partitions.
Changes
Partitioned table dropped.
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Changes |
| Cause |
| Solution |