AOS restart with bath jobs executing - AX 2009

(0) Share

Report

Posted on by Waldemar Kuczynski

Hi All,

We have AX2009 RU8. For the past 7 years we had a job to change status of the batch jobs to 'withold' waited untill all batch jobs finish executions and only then shut down AX to do maintenance/upgrades.

Now I think it wasn't necessary, and it is okay to stop batch AOS when jobs are executing. They'll be interrupted, transactions aborted/rolled back. And then when AOS is restarted it'll run the job again.

Is my thinking correct? Is it okay to stop batch server with batch jobs in 'executing' status? What is your experience?

Best regards

Waldek

*This post is locked for comments

I have the same question (0)

All responses (4)

Answers (0)

Dick Wenning 8,705 Moderator on at

Like (0)

Report

yes it is correct, it is the same when your AOS crashes, the transaction on SQL are rolled back.

Was this reply helpful? Yes No
Soren Andersen 530 on at

Like (0)

Report

Your practice is actually very good.

If you just restart the AOS, some jobs might end in status "executing" - so you would have to do something about them instead.

Another option - if you know the start/end time of your AOS service windows - you can just shift the start times of the batch jobs - to sometime after the maintenance windows.

Was this reply helpful? Yes No
Waldemar Kuczynski 5 on at

Like (0)

Report

Thanks for replies.

Soren, our practice is taking more time to stop/start aos services plus we have to wait in case of a very long running job. Or if a job stops responding and stays in 'executing' status.

After windows updates that run at night AOS also need to be restarted. No one wants to stay up in the middle of the night on weekend, and our job to stop batches failed recently because one batch job was executing for ages.

That is the reason why i'm thinking of not using it at all and just let AOS to kill batch jobs.

I do not worry about jobs staying in 'executing' status, cause it'll only be a status of a batch job record, not the real execution of the job (which will stop with AOS). And to update the record I can always run an sql job to change the status of all jobs in status 'executing' to 'waiting' to make sure all is okay when AOS is started again.

I am more worried if anything can go wrong, data partly updated/corrupted or similar.

I was trying to find microsoft guidance on this, but couldn't.

I am also thinking there are companies with plenty of batch jobs, and when i started thinking of it I can't believe everyone postpones the jobs to do release. If it was that important i suppose there would be some sort of AX option: Stop all batch jobs/start all batch jobs.

Anyone else, do you stop/postpone batch jobs for your instances of AX or instances of your clients? Or do you just shut AX down not worrying of the batches?

Was this reply helpful? Yes No
BorisD 2,826 Moderator on at

Like (1)

Report

Hello Waldemar,

It also depends on the batch job. For example, if yo have an invoice batch jobs that prints or emails out invoices. You don't want 2 invoices sent out to customers. In this case, you want to withhold, or schedule the job to run after the maintenance time. otherwise, for all other batch jobs let AOS deal with it!

Was this reply helpful? Yes No