Broadcasting jobs taking very long timel

[Uthay]

Hi Gurus,

We are using broadcasting funcitonality in our project , we use to have daily boradcasting jobs which will distribute the workbooks on daily basis.

Recently we observed that few jobs are taking very long time i.e

1.Say Job X have 10 receipents, as you know , for each receipent one additional job will create and will distribute as per the settings..in this sequence its taking very long time create that addional job,even its happening for single receipent jobs also...

If we would the check the daily logs, same job which use to complete 200 to 300 seconds, will take around 6000 to 8000 seconds....and will show the job log as waiting for job XXXXXX checking status in again 10secs..and job will show yellow status for long time.....

When ever we get this kind of issues, we use to kill the job and will ask the user to reschedule, but these days, users started asking for the reason , y same job is taking long time some times and same will comepltes in normal times in other days....

your quick help is more appriciated...

Regards,

UGiri

[Former Member]

hi,

a reason could be because in the same time of your jobs, there are many other treatments (job or not) which slow down your process, due to a lot of activities.

Another reason could be that you have not enough work process (job runs in background).

Note: in ECC system, during the day, we mainly have dialog processes to allow employees to work (in foreground)...., and during the night (for instance), we inverse the proportion of Dialog process / work process, to allow to have a high night job activity (so in background). See with your basis.

these two points are often the reason why sometimes a job is fast and why the same job is slow another time in the day.

regards

Mickael

[Uthay]

Hi Michal,

Thanks for your inputs, actually we have enough back ground jobs duirng the job running time, sometimes only its taking long time, and we didnt find any reason where the job is delaying and aslo not able to provide any reasons to the user.....Do you have inputs where the time will get struck....

Thanks,

Kesav.Nalla

SAP BW Team.

[Former Member]

Hi,

Except a lack of work process, a peak of activity... just like that, no, I don't see something, unless maybe the hardware itself(lack of memory or space file disk: not enough space => SAP needs more time to write the actions in tables).

But, if you really have enough work process (for background activity), then check if you have not a peak of activity, like many other jobs (for business or system job). And check if there is not a conflict between another job and yours, which try to update the same kind of data: I think mainly to jobs which reorganize the database, and/or change pointer (if you program use it), and/or program of archiving/deletion which modify tables.

regards

Mickael