Long running background job

[Former Member]

Hi,

We are facing problem with an MM job, this job some time finishes in few minutes or some times it will be running for a long time so that we should kill the job manually.

Can you please tell me what are the reasons can be for this, and also tell me what are the reasons that a job to be fnished in scheduled is running for a long time and how to find the root cause for this.

Yours reply is very much appreciated

Regards

Balaji Vedagiri

[former_member185954]

Hello Balaji,

We do not have access to your systems, so we cannot tell you the reason. However we can tell you where to look.

But before that is done, we would need information:

What is your SAP version?

What is your OS?

What is your Database on which SAP runs?

What time do you schedule the job?

How many times do you schedule the job?

More questions to follow, once you provide answer to these questions.

Regards,

siddhesh

[Former Member]

Hi Balaji,

Please let know if the issue is resolved for you with SM65 options...if not provide some more details about the MM job...is it a standard SAP or customized program,check what are the other jobs that are running at the time if long executions of the said job.

Srikanth

[former_member215759]

Hi,

Please confirm you have enough hardware space.

Please do a consistency check of the BTC Processing System as follows:

1. Run Transaction SM65

2. Select Goto ... Additional tests

3. select these options: Perform TemSe check

Consistency check DB tables

List

Check profile parameters

Check host names

Determine no. of jobs in queue

All job servers

and then click execute.

4. Once you get the results check to see if you have any inconsistencies

in any of your tables.

5. If there are any inconsistencies reported then run the "Background

Procesing Analyses" (SM65 .. Goto ... Additional Tests) again.

This time check the "Consistency check DB tables" and the

"Remove Inconsistencies" options.

6. Run this a couple of times until all inconsistencies are removed from

the tables.

Make sure you run this SM65 check when the system is quiet and no other

batch jobs are running as this would put a lock on the TBTCO table till

it finishes. This table may be needed by any other batch job that is

running or scheduled to run at the time SM65 checks are running.

Please confirm you are running the following reports daily as per note #48400:

RSPO0041 (or RSPO1041), RSBTCDEL: To delete old TemSe objects

RSPO1043 and RSTS0020 for the consistency check.

Regards,

Snow