cancel
Showing results for 
Search instead for 
Did you mean: 

Error locking table TBTCO

Former Member
0 Kudos

Hi,

During the FBRA tcode user finding error that system lock error; for this I've checked the enqueue log and found that

EnqStoreTopHist: Lock Table Overflow at caused by

Cnt= 3588 Cli=500 Uname=AA15506 Tcode=FBRA

EnqStoreTopHist: Lock Table Overflow at caused by

Cnt= 3569 Cli=500 Uname=DP10611398 Tcode=FBRA

Owner1=20111005193833036000010201JETSAPR3P.......................

Owner2=20111005193833036000010201JETSAPR3P.......................

Cnt= 24 Cli=500 Uname=MAACATTMFK Tcode=ZCSHR

Owner1=20111005132938416000010301JETSAPR3P.......................

Owner2=20111005132938416000010301JETSAPR3P.......................

EnqStoreTopHist: Lock Table Overflow at caused by

Cnt= 3590 Cli=500 Uname=AA15506 Tcode=FBRA

Owner1=20111005194402938000010102SAPAPPL60.......................

Owner2=20111005194402938000010102SAPAPPL60.......................

EnqStoreTopHist: Lock Table Overflow at caused by

Cnt= 3593 Cli=500 Uname=RL10602976 Tcode=FBRA

Owner1=20111005200919284000010101JETSAPR3P.......................

Owner2=20111005200919284000010101JETSAPR3P.......................

enque/table_size is 32768 in our system .

Please suggest what could be the solution

Regards,

RMav

Accepted Solutions (0)

Answers (1)

Answers (1)

sunny_pahuja2
Active Contributor
0 Kudos

Hi,

You can troubleshoot lock table overflow issue with SAP note 746138.

Thanks

Sunny

Former Member
0 Kudos

Hello Raj,

Please increase locktable size to 50000by using rz10 and restart apllication server after restarting check lock table size and maximum lock table entries in sm12>extras->statistics.

this will solve your problem

Thanks,

Venkat

Former Member
0 Kudos

Hello Venkat,

In my environment I am having enqueue replication server and 3 app server.

In which profile should I change this value ERS Or DVEBMGS?

Regards,

R Mav

Former Member
0 Kudos

Hi,

We have increased the enque/table_size parameter from 32768 to 50000.

But still issue persist.

Please suggest.

Regards,

RMav

Former Member
0 Kudos

Hi,

Please check the no. of currently existing lock entries in SM12.

You need to analyze the lock entries to understand the reason for huge no. of lock entries - check the tablename, lock mode and duration of lock.

Incase the locks are more than a day old, you should consider questioning the lock owner about details and possibilities of deleting old locks.

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.

Hope this helps.

Regards,

Varun