User runs a job in the Batch Optimizer. The Batch Optimizer was not able to find a better alternative for the batch, but suggests optimizer can still run on each individual SQL. When the user tries to optimize the SQL statement, it processes the SQL for a while then they eventually get the error:
Failed to optimize.
Out of memory
Afterwards trying to delete the Job from the Batch Optimizer crashes SQL Optimizer.
SQL Optimizer ran out of memory while trying to optimize the SQL statement after trying to optimize it in the Batch Optimizer. Be sure there is memory available for the SQL Optimizer to continue working. Try closing out some of your other applications.
This issue has been addressed in version 7.4 of Quest SQL Optimizer for Oracle.
Most current version available here: https://support.quest.com/Search/SearchDownloads.aspx?ActiveTab=1