Hi everyone,
Although we all database engineers do trust the Oracle optimizer to do its job (and it usually does) there some rare occasions, where the optimizer fails do predict the actual cost of a statement and chooses a sub-optimal plan that has a lower cost than others which do perform faster. This problem is mitigated by using SQL baselines as we all know, but what is missing is the possibility to mark a specific plan as "bad" so that the optimizer can avoid it.
Thank you for your time,
Harris Porgiatzidis
DBA