Microsoft Dynamics AX (Archived)

Batch job took more time

(0) Share

Report

Posted on by sri17

346

Hi All ,

AX 2012 R3

Need your assistance or insights to find the root cause of the below issue .

One of the batch job recurrence is one time in a day and usually ends in 2 mins daily ,but yesterday it took an hour ,but the data created or posted is approx same count as it posted in the previous days and there is no major record count difference also.

Points :

=====

* Batch job recurrence is runs once in a day

* Batch batch job usually ends in 2 mins as per batch job history for last 6 months.

* Batch job runs in the batch mode and dedicated server.

* Yesterday also batch job starts as per recurrence ,but took an hour and ended successfully.

* Record count data processed by batch job is approx same yesterday and previous days.

* Since batch job ended successfully ,there wouldn't be any event log or error log .

Client asks why batch job took an hour yesterday . Looking for some help here .

Thanks in advance for looking into it and response.

*This post is locked for comments

I have the same question (0)

All responses (7)

Answers (0)

sri17 346 on at

Like (0)

Report

Hi All ,

AX 2012 R3

Need your assistance or insights to find the root cause of the below issue .

One of the batch job recurrence is one time in a day and usually ends in 2 mins daily ,but yesterday it took an hour ,but the data created or posted is approx same count as it posted in the previous days and there is no major record count difference also.

Points :

=====

* Batch job recurrence is runs once in a day

* Batch batch job usually ends in 2 mins as per batch job history for last 6 months.

* Batch job runs in the batch mode and dedicated server.

* Yesterday also batch job starts as per recurrence ,but took an hour and ended successfully.

* Record count data processed by batch job is approx same yesterday and previous days.

* Since batch job ended successfully ,there wouldn't be any event log or error log .

Client asks why batch job took an hour yesterday . Looking for some help here .

Thanks in advance for looking into it and response.

Was this reply helpful? Yes No
Suggested answer

Satish Panwar 14,671 Moderator on at

Like (1)

Report

Hi Sri17,

One of the reasons could be network/SQL resources availability. Unless the job will continue to take longer on regular basis, it would be very difficult to identify what's caused one time delay.

Suggest that you monitor it next time and analyze it next time. If you have back prior to last run, try restore in non-prod and see if it again takes regular time or 1 hr or so.

Another check can be..see whatever records are processed. If you have date time on those records somewhere so you can see if it took longers to process each record or there is delay to start and record still got processed quickly. This can only give you pointers.

Thanks,

Satish Panwar

Please take time to click yes against the answer if it help guide you in right direction.

Was this reply helpful? Yes No
Suggested answer

A.Prasanna 8,223 on at

Like (0)

Report

Hi Sri17,

if it is took Initially 2 min , and now its consuming 1 hour , it is significant change .

first of all , check what has been changed during the job recurrence , if it is still consuming same mount ,

just check /Monitor SQL Resource Availability (RAM and Processor Utilization ) and Disk Performance , better if you can use Performance Counters.

Hope you are not set your Windows Server Updates automatically.

Thanks & Regards,

Amith Prasanna

Was this reply helpful? Yes No
Suggested answer

Ludwig Reinhard Microsoft Employee on at

Like (0)

Report

Hello sri17,

Was there something special yesterday e.g. somebody applied new code or made a backup or did some other maintenance work on your machine that would explain the longer time for running the batch?

Please check again tonight and let us know if the batch still needs an hour to complete.

Many thanks and best regards,

Ludwig

Was this reply helpful? Yes No
qianwang 7,168 on at

Like (0)

Report

Hi sri17,

Try a tool like a trace resolver that tells you exactly what's going on and which ones are the heaviest, so you can identify bottlenecks and which steps take longer than before.

blogs.msdn.microsoft.com/.../

Regards，

QianQW

Was this reply helpful? Yes No
Suggested answer

A.Prasanna 8,223 on at

Like (0)

Report

Hi QuianQW, Sri17,

It's not recommend to run Trace Parser on Production Instances , because it will add Performance Overhead on AOS.

Thanks & Regards,

Amith Prasanna

Was this reply helpful? Yes No
Suggested answer

nmaenpaa 101,162 Moderator on at

Like (0)

Report

Actually running trace capturing in prod system is perfectly ok, and it will add only a minimal performance overhead. But you can't use tracing to diagnose why a batch job runs for one hour, since the tracing captures about 1 GB data every minute! Capturing AOS trace is only realistic to use if the process that is traced doesn't last more than a few minutes.

The actual Trace Parser tool should be used in a test/dev system to analyze the trace that was captured in prod.

Since Trace parser might not be a suitable candidate for troubleshooting this case, you could try Tools - Options - SQL to capture information about long running queries (if you use "Write to file" option, it will write the results to a file that you find in the Log folder of the corresponding AOS instance). But remember to disable this setup once you have recorded the information to a file.

Anyway, like others already suggested, I would not use too much time to wonder why it took so long once. But if it happens again, then you should investigate.

Was this reply helpful? Yes No