User is trying to run SQL Optimizer on a SQL statement that consists of an UPDATE statement followed by multiple columns with the SET clause and using table aliases.
When clicking on the Optimize icon, the SQL Optimizer will incorrectly prompt to enter bind variables where the name of the bind variable is the same as the aliases used in the SQL.
The same SQL statement runs fine in SQL Plus or Toad Editor without need for any bind variables. The SQL statement can be Optimized in version 7.4 without being prompted for bind variables.
You need to be signed in and under a current maintenance contract to view premium knowledge articles.