I am seeing that our scheduler on our test machine
is now crashing after finishing a script. I do not
see any errors in the event logs or the trace logs.
We have limited our Oracle access to one connection
on a startup script. The script disconnects
immediately after reading a value from the database.
After that script finishes, the scheduler randomly
crashes after running and and completing a job.
Can you offer any solution, other than re-installing
the scheduler?

It sounds like you are experiencing a problem with a database connection.

1. Set the job to run detached so it cannot crash the scheduler.
2. Do not use ODBC connection with an Oracle ODBC driver. Use native driver connection is possible or use ODBC driver from another vendor.
3. If you choose native driver connection make sure you select the correct driver that matches your Oracle client version (not your Oracle server version).

: I am seeing that our scheduler on our test machine
: is now crashing after finishing a script. I do not
: see any errors in the event logs or the trace logs.
: We have limited our Oracle access to one connection
: on a startup script. The script disconnects
: immediately after reading a value from the database.
: After that script finishes, the scheduler randomly
: crashes after running and and completing a job.
: Can you offer any solution, other than re-installing
: the scheduler?

I cannot set the job to detached because I need to
define and set a global variable from a database
lookup that almost every job we use references.
When I set the job as detached, no other job could
see the global variable. If you have a way to have
the other jobs see the global variable that is
defined and set in the detached job, that would be
great! Thank you.

: It sounds like you are experiencing a problem with a database connection.

: 1. Set the job to run detached so it cannot crash the scheduler.
: 2. Do not use ODBC connection with an Oracle ODBC driver. Use native driver
: connection is possible or use ODBC driver from another vendor.
: 3. If you choose native driver connection make sure you select the correct
: driver that matches your Oracle client version (not your Oracle server
: version).

Instead of using global variables you can use system registry or INI file or even a text file as a global storage to pass values around.

For example

// set value
INIFileSetKey ( "win.ini", "My Job", "My Value", my_local_var )

// get value
INIFileGetKey ( "win.ini", "My Job", "My Value", my_local_var )

: I cannot set the job to detached because I need to
: define and set a global variable from a database
: lookup that almost every job we use references.
: When I set the job as detached, no other job could
: see the global variable. If you have a way to have
: the other jobs see the global variable that is
: defined and set in the detached job, that would be
: great! Thank you.