background job delay

[Former Member]

Hi All,

in ECC production system we have more then 2000 jobs running.so for that reason we have created background logon group as public, we assigned 4 application server to that group and in ci we don't have bg wp.

Here Issue is jobs are in delay, one job never went active more then 10 days (it is in delay state more than 10 days )which are not assigned executing server.usually if we don't assign target server it should take default server but why it is not taking could you please some one explain.

thanks

mani

Edited by: manohar kumar on Apr 29, 2010 4:15 PM

[former_member227600 · Accepted solution]

Hi,

Have you configure batch server group using SM61.

[Former Member · Accepted solution]

Hi Karan,

Yes, we have configured logon groups using sm61 .

[Former Member]

Hi,

First of all check File system size /sapmnt/<SID>/global.

If free size is not enough to run, special batch job can not start. Allocate enough free space to file system, and reasign.

It will start.

Thanks

[Former Member]

that was the issue with logon groups.

[Former Member]

HI Mani,

one job never went active more then 10 days (it is in delay state more than 10 days

For this you might want to check the job class(A, B or C) as well, it will be delayed more if you have another jobs with high priority.

But 10 Days!! its too long still. What is the normal delay!!

Try to run consistency check as well in SM37>Select job>job-->check status

Regards

Edited by: Gagan Deep Kaushal on Apr 30, 2010 12:47 AM