Examine the output of the query that you executed to list the objects in the recycle bin:
You verified that no table named SALES_TAB exists in the schema. Then you executed the
following command to purge the objects in the recycle bin:
SQL> PURGE TABLE sales_tab;
What would be the outcome of this command?
A.
All three tables in the recycle bin are purged
B.
Only the table with the oldest DROPSCN is purged
C.
The command returns an error because multiple entries with the same name exist in the
recycle bin
D.
Only the table with the latest DROPSCN is purged
Explanation:
verified
http://download.oracle.com/docs/cd/B14117_01/server.101/b10759/statements_9018.htm
If you specify the user-specified name, and if the recycle bin contains more than one object of that
name, then the database purges the object that has been in the recycle bin the longest.
Use the PURGE statement to remove a table or index from your recycle bin and release all of the
space associated with the object, or to remove the entire recycle bin, or to remove part of all of a
dropped tablespace from the recycle bin.
When the database purges a table, all table partitions, LOBs and LOB partitions, indexes, and
other dependent objects of that table are also purged.The database object must reside in your own schema or you must have the DROP ANY… system
privilege for the type of object to be purged, or you must have the SYSDBA system privilege.
