You executed the following commands in a database session:
SQL> SELECT object_name, original_name FROM user_recyclebin;
OBJECT_NAME ORIGINAL_NAME
——————————– ————-
BIN$QJwA1dMyB1LgQJYK+xUptw= = $0 MYSPACE
SQL> CREATE TABLE myspace AS SELECT * FROM my region;
Table created.
SQL> SELECT object_name, original_name FROM user_recyclebin;
No rows selected
What could have caused the recycle bin to clean up?
A.
There is demand for space from the new table
B.
The undo tablespace does not have sufficient free space
C.
The new table name is the same as the table name in the recycle bin
D.
The temporary tablespace that is assigned to you does not have sufficient free space
Explanation:
http://download.oracle.com/docs/cd/B19306_01/backup.102/b14192/flashptr004.htm#i1019426
Recycle Bin Capacity and Space Pressure
There is no fixed amount of space preallocated for the recycle bin. Therefore, there is no guaranteed minimum amount of time during which a dropped object will remain in the recycle bin.
The rules that govern how long an object is retained in the recycle bin and how and when space is reclaimed are explained in this section.