User uses Toad Options | Oracle | General | Default Schema fields in order to enter a different schema than the connected schema. However, when running scripts, they are executed in the connected schema and not the schema entered in options screen.
Also, running a statement will run in the default schema, however, Toad reverts back to the connected schema after statement execution. Below is the background queries:
“ALTER SESSION SET current_schema = ”
“ALTER SESSION SET current_schema = ”
How to run scripts in default schema or prevent Toad from reverting back to connection schema after running a statement?
This was resolved in Toad for Oracle 11.0. The latest version of Toad for Oracle can be downloaded here.
