Lock table Overflow due to batch jobs

[Former Member]

Hi,

After refresh, there are 100s of ARFC locks instantly created and lock table overflow is taking place. Eveter deleting, locks are recreated instantly, Not sure, which job to be stopped.

SM12 Locks::

000 SAPSYS 19:35:43 E TBTCO ARFC:A467A23015CC4B055BA6065D 13314800 0 1

000 SAPSYS 19:35:43 E TBTCO ARFC:A467A23015CC4B055BA6065D 13315400 0 1

000 SAPSYS 19:35:43 E TBTCO ARFC:A467A23015CC4B055BA6065D 13320300 0 1

000 SAPSYS 19:35:43 E TBTCO ARFC:A467A23015CC4B055BA7065E 13315000 0 1

000 SAPSYS 19:35:43 E TBTCO ARFC:A467A23015CC4B055BA7065E 13315600 0 1

SM21 Error:

19:55:19 DIA 001 000 SAPSYS GE G Lock table overflow

19:55:19 DIA 001 000 SAPSYS GE A Internal lock administration error

19:55:19 DIA 001 000 SAPSYS GZ Z > EqSetCluster(); rtc=16 enxxmenq1905

Currently jobs are put under suspended status using BTCTRNS1. Still locktabe is getting filled up and no other transactions are working, due to this. Would appreciate any input.

currently enque/table_size = 30000

Thanks,

[Former Member]

Check if there is any job active via SM37 and stop if there is one. BTW, did you complete all post-refresh activities before using SAP system?

[Former Member]

Hi Raj,

The maximum number of locks in the lock table is subject to an upper limit that is set by profile parameters. The enque / table_size parameter determines the size of the lock table in KBs. You can use transaction SM12 -> Extras -> Statistics to determine both the maximum number and current number of entries.

A lock table overflow may occur if:

the lock table configuration is too small the lock table configuration is too small

an application sets lots of locks an application sets lots of locks

Regards

Sekhar

[Former Member]

Thanks.. This seems to be happening for this system only. The source system has similar conf works fine. My concern is what triggers, so many locks.. as no background job is running now. wondering, if it possible to validate, if ENQUE work process is functioning at all ? I could see ENQ wp in SM50 in waiting state.

Below is the Enque trace from ST05.:

Enqueue Statement

Lock Operation ENQUEUE

Execution Mode WAIT

Lock Object ESTBTCO

Owner 20091221204543487201000191sapar1

Owner UPT 20091221204543487212000191sapar1

Scope parameter 2

Collision Owner

Collision Object

Collision User Name

Remote Time 0

Request Time 0

ABAP program name SAPLSENA

Granulate

GranularityNo. 1

Lock mode Table Name Granularity Argument

Excl(Cumulati TBTCO ARFC:A467A23015CF4B05599B

0518 17555301

[peter_dzurov]

SAP updates table TBTCO whenever a job change its status. Are you experiencing some problems with background processing?

[Former Member]

Below process continously running. causing locks created.. restarted on its own.

0 DIA 935 Running Yes 508 SAPMSSY2 000 SAPSYS Direct Read BTCDELAY

Thanks

[Former Member]

Hi Raj,

Please check at the database level what's the size of this table?

Basically table BTCDELAYContains 'Directory of delayed system log messages for batch scheduler '

And you can think of scheduleing the corresponding job in Background rather using Dialog user.

Regards

Sekhar