Re: optimizer uses objects in Recyclebin or not!- Bug?

It is not only the index name which is not flashed back but a couple of other table objects as I explained in this blog post

https://hourim.wordpress.com/2012/11/14/recycle-bin-whats-going-on/

And things become interesting in this context when you are using a SPM baseline. Dropping and flashing back a table can preempt the CBO from using that SPM plan if this one uses an index from that dropped & flashed back table

https://hourim.wordpress.com/2014/01/24/sql-plan-management-and-table-flashback/

*Bottom line*: when you drop and flashback a table, then think about the following points

   1.

   the foreign key constraints are not flashed back    2.

   the original index name, the trigger name and constraint name are not flashed

   back <https://hourim.wordpress.com/?s=recycle>    3.

   any SQL plan baseline based on an index created on a table that has been    dropped and flashed back will not be reproducible until you give that index    its original name

But I haven't tested this in recent releases.

Best regards

Mohamed Houri

--
http://www.freelists.org/webpage/oracle-l