Unless you have optimizer statistics on the data dictionary (which is most unlikely) then the optimizer mode/goal is not going to be have any effect on the performance of a drop table command. If it takes a long time to drop a table, then it is probably because the table has too many extents, or the data dictionary has been damaged, or both. The ways in which the data dictionary can be damaged are explained in the Ixora web tip on Planning Extents.

Sorry to bother you again but there is strange problem coming in mine application. Problem is when PL/SQL module generate DROP TABLE statement. This tables are something like temporary tables - created and droped inside module.

If we use optimizer mode (CHOOSE - FIRST ROW) and after ANALYZE TABLE...ESTIMATE STATISTICS everything works well except DROP TABLE statement.

If we use default optimizer mode, everything works slower except DROP TABLE statement.

I really appreciate your views