May 5, 2004 at 3:40 am
Hey,
We run Siebel on SQL Server 7.0 SP2 and NT4 SP6 and are experiencing problems with the transaction log schedule getting disabled on a daily basis.
Note, the actual job is enabled, it's the schedule that seems to get disabled daily. When I re-enable the schedule, the logs back up as normal throughout the day, but the next morning, I have to then re-enable the schedule.
Has anyone else seen this and also found a fix for it?
Unfortunately, due to us being a regional node, we can't upgrade the OS or SQL SP levels incase we mess up the replication beteen the HQ and ourselves!
Cheers
May 5, 2004 at 5:48 am
The job will disable itself if sheduled run one time.
Is this the only job get disabled daily? If not, schedule a job to enable it.
May 5, 2004 at 10:00 am
Hey,
The job is scheduled to run every 30 minutes between 7:30am and 8:00pm (Mon thru Fri). It runs without a problem during these times, but guaranteed, tomorrow I will need to re-enable the schedule.
I could write a script to re-enable the job for me, but thats just avoiding the issue at hand. Also, the other three jobs on the server do not have their schedule disabled.
Cheers!
May 6, 2004 at 7:33 am
Another way to handle it (in a long run, upgrade may kill the issue) is a window schedule job (at command) to call it.
May 6, 2004 at 11:32 am
We were having the same issue in SQL 2000. The resolution was to apply the latest service pack.
It is a KNOWN problem with both 2K AND 7.0.
MS Knowledge Base recommends applying latest service pack for 7.0 as well. Here is a link to the MS Knowledge Base article....
http://support.microsoft.com/default.aspx?scid=kb;en-us;295378&Product=sql2k
Hope this helps!!!
Steve
August 11, 2005 at 8:43 am
Don't know if you're still having this problem but I've just spent more time than I should have trying to figure out why I was getting a similar problem. I eventually discovered that somehow an expired end date was set which was not obvious until I went into the 'edit recurring job schedule' window. Once I'd set it as no end date it worked a treat.
Just as a final note I have also experienced similar problems with job scheduling which were fixed by the latest service pack.
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply