Error locking table TBTCO

[Former Member]

Hi,

We are having issue in locking "Error locking table TBTCO" at our SM12 statics Maximum Number of Lock Owners 3603

Even on increasing the enque/table_size it not effecting the lock owner. Our environment having enq replication server.

The profile parameter for enque/serverinst = $(SCSID) (00)

enque replication server instance number is 10

What could be the correction need to be done?

Regards,

RMav

[Former Member]

Hi,

TBTCO is a table used for background processing. Possibly, there is an old long running job that is creating locks on the system.

Check the job and consider killing it, if possible.

Regards,

Venkata S Pagolu

[former_member4224]

You have to check the reason for the error in the lock.

Get the Work Process number that logged the error in SM21. Check the trace file of this work proces. At the same timestamp of the error in SM21 you do find the root cause in the work process trace.

Usually this is caused by a overflow in the enqueue table, but not always. For this reason you have to check the work process trace the reasl root cause.

To check if the enqueue is suffering a overflow you should go to SM12 -> Extras -> Statistics

If in the statistics you do find that the "Maximum Fill Level" reached the maximum number of locks in these itens, for example:

Maximum Number of Lock Owners 39481

Maximum Fill level 458

Current Fill Level -25

Maximum Number of Lock Arguments 39481 <<<

Maximum Fill level 39480 <<<

Current Fill Level 15

Maximum Number of Lock Entries 39481 <<<

Maximum Fill level 39480 <<<

this means that the enqueue was really suffering under an overflow situation.

Just for your information, the TBCTO is the table for the status of the jobs. So, every job need

to write the status in this table and also lock this table firstly.

Clébio

[Former Member]

Raj,

SAP updates the tables TBTCO whenever your background jobs status change and there could be an old long running job that is creating locks on the system. Check the job and consider killing it, if possible.

What value you increased for Enqeue lock table, Please increase locktable size to 80000 by using rz10 and restart apllication server after restarting check lock table size and maximum lock table entries in sm12>extras->statistics.

Refer to the link

http://help.sap.com/SAPHELP_NW04S/helpdata/en/d3/43d2416d9c1c7be10000000a1550b0/content.htm

Regards,

Arjun

[Former Member]

Hi,

even keeping value for enque/table_size to 102400 no change Maximum Number of Lock Arguments still it's 3603.

do I need to change the enque/serverinst value. since this value set as 00 i.e. SCSID and enque replicationserver instace id is 10.

Please suggest.

Regards,

R Mav

[Former Member]

Under Enque server instance, You need to set the value as Instance number of enqeue which is enque/serverinst=10.

Refer to the link

http://help.sap.com/saphelp_nw04s/helpdata/en/4c/1184365e3d4f4fb521a420bcad4e38/content.htm

http://help.sap.com/saphelp_nw04s/helpdata/en/de/cf853f11ed0617e10000000a114084/content.htm