on 10-05-2011 4:57 PM
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
Hi,
You can troubleshoot lock table overflow issue with SAP note 746138.
Thanks
Sunny
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello,
Not on apps servers but on CI/enque server
http://help.sap.com/saphelp_nw04/helpdata/en/37/a2e3ab344411d3acb00000e83539c3/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/fd/c675698b8d462b8895583c27bdc9bd/content.htm
Thanks
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
User | Count |
---|---|
83 | |
24 | |
12 | |
9 | |
7 | |
6 | |
5 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.