Restrictions on Oracle flashback table Deletion

Talking about the restrictions on Oracle flash-Back table deletion, Oracle10g began to provide the recycle bin function similar to the windows system. When you delete a table, it is not directly deleted, but moved back

Talking about the restrictions on Oracle flash-Back table deletion, Oracle 10 Gb has provided the recycle bin function similar to windows system. When you delete a table, it is not directly deleted, but moved back

Oracle 10 Gb has provided the recycle bin function similar to windows. When you delete a table, it is not directly deleted, but moved to the recycle bin. If you need to retrieve the original table from the recycle bin, you can use flashback to delete a table to quickly retrieve the deleted table without importing the original table from the backup! However, this recycle bin function is also prerequisite. You can not use flashback to delete tables under any circumstances. In summary, in 10 Gb, tables cannot be deleted using flashback in the following scenarios, if there is any improvement on the 11g, you can refer to the method in this article to test it! By the way, the recycle bin adopts a fifo, first-in-first-out mechanism! For example, if there are two tables with the same name in the recycle bin, you can find the table that was first flashed back Based on the sequence of the deletion time. Therefore, the "rename to" option is provided for the "flashback Delete table" command;

1: the recycle bin function is not enabled (this does not need to be tested)
2: The table's storage tablespace cannot be system
3: The purge parameter cannot be included when the table is deleted.
4: when there is space pressure
5: fine-grained audit is enabled on the table
6: VPD is enabled for the table.

I. test whether the table space is stored as system flash-back Deletion
1.1 create a test user and grant corresponding permissions to enable the database recycle bin function.

1.2 use the test user to create two tables, one of which is stored in the system tablespace

1.3 Delete two tables without the purge parameter. Check that the recycle bin only has the drop_2 table. The table's storage tablespace is users, as a result, it is proved that tables stored in the tablespace as system cannot be flashed back and deleted.

1.4 test whether the drop_2 table can be deleted with sys user.