I have been having an issue with 24 x 7 just quitting for no apparent reason. I look in the job log to see if resources were low or other issues it may be having....but no.

What has occurred 2 times now in the last month. I have a Database Export job which is suppose to run at 4:00 a.m. every morning. I get an email when the job completes.

No email has been received, so when I look on the server, the 24x7 icon is at the bottom of the screen, but when I move my mouse over the top of it, the icon disappears.

Any suggestions?

Did the job start?
If yes, set this job to start detached so it cannot bring the entire scheduler down.
If no, please check if there were some other jobs and whether they completed succesfully.

: I have been having an issue with 24 x 7 just quitting for no apparent reason.
: I look in the job log to see if resources were low or other issues it may
: be having....but no.

: What has occurred 2 times now in the last month. I have a Database Export job
: which is suppose to run at 4:00 a.m. every morning. I get an email when
: the job completes.

: No email has been received, so when I look on the server, the 24x7 icon is at
: the bottom of the screen, but when I move my mouse over the top of it, the
: icon disappears.

: Any suggestions?

The job finished successfully on 11/4/2001 04:00 a.m., but never started again. There are no other jobs than this export on this server.

I've experienced this before on other boxes when resources were low. This server has 86% resources, and no other errors existed.

: Did the job start?
: If yes, set this job to start detached so it cannot bring the entire
: scheduler down.
: If no, please check if there were some other jobs and whether they completed
: succesfully.

Can you provide more details on the job? How often does it run? is this a synchronous or asynchronous job? is this script? if yes, what kind? does it connect to a database? what is the database engine/version? how the connection is setup (odbc or native driver, if yes which one)?

: The job finished successfully on 11/4/2001 04:00 a.m., but never started
: again. There are no other jobs than this export on this server.

: I've experienced this before on other boxes when resources were low. This
: server has 86% resources, and no other errors existed.

1) Job runs every a.m. -- 4:00 a.m.
2) It is Asynchronous, however, no other jobs run on this server
3) It is a JAL Script
4) It connects to an Oracle 8.06 database and performs an export
5) Connects with ODBC Driver (Oracle ODBC Driver)

Hope this helps.
Candy

: Can you provide more details on the job? How often does it run? is this a
: synchronous or asynchronous job? is this script? if yes, what kind? does
: it connect to a database? what is the database engine/version? how the
: connection is setup (odbc or native driver, if yes which one)?

Oracle 8.0.x drivers are known to be very buggy and they often cause various problems including memory leaks. I highly recommend to setup that job to run detached in order to isolate it from the scheduler and improve stability. Since this is the only job running on the server, consider setting it as synchronous to reduce the system load. I am sure both these things will help to solve the issue.

: 1) Job runs every a.m. -- 4:00 a.m.
: 2) It is Asynchronous, however, no other jobs run on this server
: 3) It is a JAL Script
: 4) It connects to an Oracle 8.06 database and performs an export
: 5) Connects with ODBC Driver (Oracle ODBC Driver)

: Hope this helps.
: Candy

Made the changes....let you know. Thanks for your help

: Oracle 8.0.x drivers are known to be very buggy and they often cause various
: problems including memory leaks. I highly recommend to setup that job to
: run detached in order to isolate it from the scheduler and improve
: stability. Since this is the only job running on the server, consider
: setting it as synchronous to reduce the system load. I am sure both these
: things will help to solve the issue.

The saga continues.

I made all the changes you suggested. The 24 x 7 scheduler version 3.1.3 just stoped again. There is nothing within statistics to indicate that memory was low. It was at about 94% when the job ran the night before. It just discontinued running.

Any other suggestions?