I defined an action for database health check.
It runs fine when I activate it in TOAD.
I created a scheduled task for it, running as an administrator, and
tried to run it.
I see TOAD running for a few seconds and then the status of the task
show that it is nor running.
There is nothing in the log in TOAD.
The most common cause of this type of problem is one doesn’t have ‘save passwords’ turned on. Scheduled Actions run by launching a separate Toad process, and it needs the password saved to disk in order to connect.
Passwords are saved to disk.
Allow multiple copies of toad to be loaded is checked (in case I left toad
open).
In the task manager I see toad starting to run and disappearing after a few
seconds.
I open the app designer and open the logs and there is no mention of the run.
You really need to save userid and passwords for the actions in a separate
place.
Turning on the save password is really bad when toad is used on a server that
several people can access.
Everyone can double click the connection and get in.
Adar Yechiel
Rechovot, Israel
Mark Lerch wrote:
The most common cause of this type of problem is one doesn’t have ‘save
passwords’ turned on. Scheduled Actions run by launching a separate Toad
process, and it needs the password saved to disk in order to connect.
You’re looking here for the log, right? Then you can double-click one of
them for details…. I’m trying to reproduce your problem, but it
seems to be working here.
It is also working here on another machine.
The action does not appear in the list in the execution log.
Adar Yechiel
Rechovot, Israel
John Dorlon wrote:
You're looking here for the log, right? Then you can double-click
one of them for details.... I'm trying to reproduce your problem, but
it seems to be working here.
Passwords are saved to disk.
Allow multiple copies of toad to be loaded is checked (in case I left
toad open).
In the task manager I see toad starting to run and disappearing after
a few seconds.
I open the app designer and open the logs and there is no mention of
the run.
You really need to save userid and passwords for the actions in a
separate place.
Turning on the save password is really bad when toad is used on a
server that several people can access.
Everyone can double click the connection and get in.
Adar Yechiel
Rechovot, Israel
Mark Lerch wrote:
The most common cause of this type of problem is one doesn't have
'save passwords' turned on. Scheduled Actions run by launching a
separate Toad process, and it needs the password saved to disk in
order to connect.
It is also working here on another machine.
The action does not appear in the list in the execution log.
Adar Yechiel
Rechovot, Israel
John Dorlon wrote:
You’re looking here for the log, right? Then you can double-click one
of them for details…. I’m trying to reproduce your problem, but
it seems to be working here. att1.dat (143 KB)
Maybe they’re launching Toad from (and on) the server??
ie running the application in memory on the server with different people
accessing the server’s desktop.
Disclaimer:
I’m probably wrong and waiting to be told so … att1.dat (1.79 KB)
Maybe they’re launching Toad from (and on) the server??
ie running the application in memory on the server with different people
accessing the server’s desktop.
Disclaimer:
I’m probably wrong and waiting to be told so … att1.dat (43 Bytes)
When you create an Action/App it gets stored here:
C:\Documents and Settings\Application Data\Quest Software\Toad for
Oracle\User Files\ToadActions.dat
When you execute an Action (e.g., “Toad.exe –a SomeAction”),
Toad looks in ToadActions.dat for the Action.
If Toad is being executed on a server, if User A creates “MyAction,”
obviously, User B can’t execute it unless ToadActions.dat is copied across
to their Application Data folder, overwriting their own file. If User B tries to
execute an Action not in their data file, they will get an “Action not
found” message. That’s why I asked about the Toad version, to make
sure we were displaying that in all the earliest versions.
When you create an Action/App it gets stored here:
C:\Documents and Settings\Application Data\Quest Software\Toad for
Oracle\User Files\ToadActions.dat
When you execute an Action (e.g., “Toad.exe –a SomeAction”),
Toad looks in ToadActions.dat for the Action.
If Toad is being executed on a server, if User A creates “MyAction,”
obviously, User B can’t execute it unless ToadActions.dat is copied across
to their Application Data folder, overwriting their own file. If User B tries to
execute an Action not in their data file, they will get an “Action not
found” message. That’s why I asked about the Toad version, to make
sure we were displaying that in all the earliest versions.