Hello experts,
something weird happened yesterday to a customer's system, and I'd like to ask you if you've seen anything like this and how to avoid it.
The system is a SAP ERP 6.0 EHP6 SPS3 on Windows Server 2008 R2 and ASE 15.7.0.042.
I've scheduled in DBACOCKPIT a weekly job for the full database dump: the schedule is weekly, Monday to Friday at 23:00. This schedule has run for a few weeks now and has worked regularly until yesterday.
Yesterday morning apparently the host server has been uncleanly shutdown, and then after a while restarted. ASE services are set to start automatically so the db started after the system boot. SAP ERP instead isn't set up to start automatically, so it didn't.
Yesterday evening, a Sunday so out of schedule, ASE started running all of those backups in sequence: it started at 23:00 and did one full dump, then after it finished the first it did another, and then another - at this point the destination disk was full.
In DBACOCKPIT I can see the logs of the job but it tells me there's no schedulation for them. So I've checked the jobs is ASE itself using Sybase Central, and found that my DBACOCKPIT schedule translates in ASE in five distinct jobs, one for each day of the week. I also found out that for each job has been specified a starting calendar day, a starting time, a weekly schedule but not the day of the week the job should run.
So to explain, the job that should run on Mondays is scheduled to run weekly at 23:00, with a starting date of May 27th (a Monday) and no end date; it's not specified that the job should run on Mondays, though. So I think this is why it run on a Sunday.
I don't like that because the local backup partition can't take five whole database backups, so should this happen again, it would fill the partition again.
I'd like to know if this is a normal behaviour, if it's happened to you before, and what to do to avoid that. I also wonder if I changed the schedules directly in ASE (if it's at all possible) specifying for each of them the day of the week they should run, if it would solve the problem and if it would brake something in DBACOCKPIT.
Let me know if something is not very clear, I can provide screenshots. Thanks for your opinions, kind regards.
--
M