cancel
Showing results for 
Search instead for 
Did you mean: 

Enqueue Locks -batch job processing

Former Member
0 Kudos

Hi Experts,

We have upgraded our SAP ECC environment from 6.0 ehp4 to ECC 6.0 ehp7. Before upgrade XXX job was running with 4000 seconds, but post upgrade the same job is running long with 20000 to 25000 seconds.
During the job run, we are getting 900+ exclusive lock entries.


Does this issue related to the SAP Note given below, we are on 740 Kernel release and we are having integrated enqueue WP(not a separate one)
2013043 - Performance Problems with Enqueue Work Process

or should we try some other solution before splitting Enqueue WP from the integrated environment?

Thanks,

Preetha Balan

Accepted Solutions (0)

Answers (2)

Answers (2)

Former Member
0 Kudos

Hope your kernel version is 740. If it is please upgrade your kernel to latest (if not latest).

There are few performance related issues in the initial level of kernel as we faced during upgrade in our landscape.

isaias_freitas
Advisor
Advisor
0 Kudos

Hello,

The kernel 740 is not supported anymore, actually.

If you plan to update the kernel patch level, you should consider upgrading the kernel to 741 or 742.

Regards,

Isaías

Former Member
0 Kudos

Hi All,

Thanks for your response!!

Our Kernel release is 740. We cannot compare the performance of the job with pervious version as all our systems are upgraded.

Due to these E locks and the long duration taken by this XXX job affects other job's performance and those gets cancelled accessing the same tables as this one.

Is there any other way to increase performance of Enqueue work process to accommodate more/shared locks in order to avoid dead lock situations.

Thanks,

Preetha Balan

former_member185954
Active Contributor
0 Kudos

Hello Preetha,

Have you raised an OSS message ?

Regards,

siddhesh

manumohandas82
Active Contributor
0 Kudos

Hi Preetha ,

Believe more analysis needs to be done   . Having 900 locks at a time is not a very big issue .

Are the other jobs failing because of Enque table lock overflow ? ( Please post the job log  of the failed jobs )

If not why do you want to investigate in this manner  or what is the reason you believe enqueue is the problem .

Have you taken an ST12 trace for the Job and tried to find out where the issue is actually ?

Thanks ,

Manu

Former Member
0 Kudos

Hello Preetha,

It could be one of many things.

You're on EHP7, what SP level ?

What's your DB ?

Have you analysed where the job is spending it's time ?

If your DB is Oracle, have you scheduled a collect,allsel since the update to EHP7 ?

See what I mean that it could be one of many things ?

Amerjit

Former Member
0 Kudos

Hi Amerjit,

We are with Netweaver 740 sp 04 and ECC 6 ehp 7 sp02, DB is DB2 9.7.

Thanks,

Preetha Balan

Former Member
0 Kudos

Hi Preeta,

With tx: ST03, check the runtime info of the program. Compare it to the runs before the EHP.

Starting from there, you will see where the difference in runtime is coming from.

It could well be coming from the ENQ as you have considered but ST03 will show you the runtime breakdown which will give you a better idea.

KR,

Amerjit