We often use SQL tasks to automate processes, this is quite flexible. During the process of task building you sometimes run into problems, and a query fails. It gives a neat ORA-##### error message in VisualCron in the Output (error) field.

In particular in more complex processes it can be difficult to troubleshoot where a query may have gone wrong, when portions of the query may consist of VisualCron variables and it is not immediately clear what has been sent to the database. It might be useful to see which query has been parsed to the database, so troubleshooting is easier, for example by adding it to the Output (error).

To choose whether or not the query is show in the task or error output the "Extra Task Debugging" could be used, under the Main Settings of the SQL Task.

Agree with this although there is a way to do this via Notifications