Although they have been dropped, they are still available for flashback. The
index cannot be recovered by itself (its CAN_UNDROP column value is ???NO??™, while the AUTHOR
table??™s CAN_UNDROP value is ???YES??™).
You can use the flashback table to before drop command to recover the table from the
recycle bin:
SQL> flashback table AUTHOR to before drop;
Flashback complete.
The table has been restored, along with its rows, indexes, and statistics.
What happens if you drop the AUTHOR table, re-create it, and then drop it again? The recycle
bin will contain both the tables. Each entry in the recycle bin will be identified via its SCN and
the timestamp for the drop.
NOTE
The flashback table to before drop command does not recover
referential constraints.
To purge old entries from the recycle bin, use the purge command. You can purge all your
dropped objects, all dropped objects in the database (if you are a DBA), all objects in a specific
tablespace, or all objects for a particular user in a specific tablespace. You can use the rename to
clause of the flashback table command to rename the table as you flash it back
By default, the recycle bin is enabled in Oracle Database 10g and 11g. You can use the
initialization parameter RECYCLEBIN to turn the recycle bin on and off; you can also turn the
recycle bin on and off at the session level, as in this example:
alter session set recyclebin = off;
498 Oracle Database 11g DBA Handbook
Temporarily disabling the recycle bin functionality does not affect objects currently in the
recycle bin; even when the recycle bin is disabled, you can still recover objects currently in
the recycle bin.
Pages:
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753