Optimizer time out summary

Provides information on any optimizer time outs. Choosing the best access plan for a very complex query can be time consuming. As the optimizer evaluates different possible access plans a better estimate of how long a query takes shape. At some point, for dynamic SQL statements, the optimizer may decide that further time spent optimizing is no longer reasonable and use the best access plan up to that point. This may or may not be the best plan available. If the SQL statement is only run a few times or if the performance of the query is good, an optimizer time out is not a concern. However, if the SQL statement is long running or if it is run many times and the optimizer times out, a better plan may be possible by enabling extended dynamic package support or by using static SQL in a procedure or program. Since many dynamic SQL statements can be cached in the system-wide statement cache, optimizer timeouts are not common.