I have just been made aware of a DB server down time that will have my DB (for reads and writes) down for a couple hours. This is during overnight processing in which we do a lot of reads and a lot of writes (MODIFY to the Data Warehouse).

So, in considering my options, I figured I could just disable the ReportCaster service and when the DB environment came back up, turn it back on.

So, here's my question. What happens when ReportCaster comes back up? Will it try to 'catch up' and rerun the jobs that it would have otherwise missed?

- ABT

This message has been edited. Last edited by: ABT,

Per my rep, Lee. ReportCaster is smart enough to read BOTSCHED and figure out what it didn't run and rerun it.

I love my rep -- Lee rocks!!!

- ABT

ABT,
If a scheduled job did not run because ReportCaster's Dist. Server was down, then Scanback should be set so that when Dist. Server comes back up, it will scan back on its schedule and run those jobs that were not
previously run.

If a scheduled job did run but did not complete because the Distr. Server was stopped, or for some other reason, then the Recovery setting
should be set to ON, so that the incomplete runs can be restarted and completed.

The Recovery and Scanback settings are located in the General tab of the ReportCaster Configuration tool.

Ira

Thanks for the information ira! Today you taught me seomething new!

quote:

Originally posted by Vinay Kumar:
Thanks for the information ira! Today you taught me seomething new!

+1 I thought I had an answer but I too always appreciate more than one arrow in my quiver.

- ABT