Batch -job monitoring

[former_member689296]

Hello All,

We have been facing performance issues, while batch jobs are running.

The jobs are taking long time to complete.

We need your help in monitoring it. Suggest what tcodes need to be used.

Thanks!

Sujit

[Former Member · Accepted solution]

Dear Sujit,

Workload analysis should start checking transaction SM50/SM66 in order to see what is going

on the DB (sequential read, full table scan...) and the table or program that is causing

the overload.

Useful transactions are ST06 (operating system analysis) and ST04 (DB analysis).

After detecting the main probable cause, you should run stats for the table detected or

evaluate why is taking so long, maybe a solution could be creating index. Sometimes HW or network are the bottle-necks.

The access path for every high sql sentence is given in ST04. If you detect standard programs you should

find SAP notes in order to improve performance.

Hope it helps.

Best regards from Peru.

[Former Member · Accepted solution]

Hi,

You can use SM37 to monitor your Batch Job.

Cheers,

RJ

[Former Member]

Hi all

Some background jobs are taking long time to complete in production BW system. Please suggest me what to do

[Former Member]

Are the jobs consuming many resources from your database? Do you see many sequential reads in transaction SM66?

Check with st04 if heavy SQL statements are being executed, do you see exclusive lock waits, etc.

Kind regards,

Mark

[former_member689296]

Thanks for reply!

Yes there are many sequential reads. It is observed in SM66. This increases CPU utilization and all processes run slow.

Here we were suggested to check through SM35, ST03N and ST06.

In SM35, it shows lot many jobs. Also we need to look on all child jobs and their analysis.

Kindly suggest how to monitor through SM35.

Also how to analyze database load during this activity.

Thanks!

Sujit

[Former Member]

Ah, you aren't running batch jobs, but batch input maps... Is some conversion taking place?

You could check for heavy sql statements on the database, but heavy load is pretty normal when running BIM's. I think it's best to ask if only a limited number of BIM's will be started at the same time.

Kind regards,

Mark

[former_member689296]

Thanks Mark!

But still we are facing the overload error. so many sql statements are executing.

How should we analyse and solve the workload issue?

Regards,

Sujit Takale

[Former Member]

Hello Sujit,

As mentioned by other guys, if you see more jobs running in SM66 and not able to finish check also ABAPer regarding those jobs, as they may not be coming out of the loop to finish. And one more thing please check the starting time of all jobs which are running long time and adjust them accordinly.

Because of this long running jobs, your online backup also may fail.

Rgds,

Durga.

[Former Member]

Hi,

First thing I would do is generating the DB stats for the table which has long sequential reads. Then use the SQL trace and analyse the sql statement if it is using a index range scan or a full table scan? Then check if there is any problem with the index or check for table reorg. So you have many differnet parameters to check, you can start with these......

Regards,

Vamshi.