Toad v12.10
When I run something simple like Select '&x' from dual; in the Execute Script action in automation designer, I do get the popup to set the value of the variable when it is run.
But assigning any environment variable to that substitution variable just causes that env variable name to appear in the output instead of its value ??
old: Select '&x' from dual
new: Select 'ACTIVESESSIONUSER' from dual
'ACTIVESESSIONUSER'
-------------------
ACTIVESESSIONUSER
1 row selected.
How can we get this to work?
Some other unrelated bugs/issues I ran into while struggling with this for several days:
1. Doing the same thing in Export Dataset action with export query option, produces a modal dialog with this error and permanently hangs Toad, requiring taskkill.
ORA-00933: SQL command not properly ended
I would like a pointer to any documentation on this action and on what kind of sql that can go in that box. Can we use pl/sql ? Can it only be a single query ?
2. Toad spool files are set to output UTF-8 with BOM by default, which is incompatible with sqlplus (if you want to execute spooled, generated sql code).
This default is different from the ANSI default encoding for saving all other Toad files, i.e,
Options --> General --> Default Encoding
What is the reason for this inconsistency in encoding defaults?
How do we change the spool file encoding locally within an Automation Designer app to ANSI, without requiring a Toad-wide default change for all users?
3. What is the meaning of the [<no hint present>] visible in front of many of the automation actions ? Are things like this explained in an Automation Designer User Manual that you can point me to ?
4. In the FTP or Rexec actions, how do I parametrize the Hostname, Username and password like all the other fields? For example with $uid or %ACTIVESESSIONUSER% or %USERNAME% etc.
5. Export DDL action (export dataset) does not produce a sqlplus compatible Insert/Merge script when table data contains '/' forward slashes or semicolons on lines by themselves, or if it has any blank lines. To workaround this we need to set sqlterminator off and setblanklines on.
How can we change the default semicolon statement separators that are in the generated insert scripts from this action?