MC 603: Lock table overflow

[Former Member]

We are getting issue like "MC 603: Lock table overflow" for some update failed tcode VL10n and VL20n, and short dump's.

we have already set the enque\table_size to 102400 KB.

There are short dumps for user's using tcode VL10N and dump is Lock table overflow...

a Quick help is needed.

Thanks

Gopesh

[jens_hoetger]

Hello,

first step should be to figure out the reason for this. The mentioned transactions are maybe only suffering from the lock table overflow.

Take a look at note 746138 for getting the transaction and the user which caused the overflow, and then try to fix this.

HTH and kind regards

Jens Hoetger

[Former Member]

We are getting issue like "MC 603: Lock table overflow" for some update failed".. The tcodes VT10n and VT20n

we have already set the enque\table_size to 102400 KB.

There are errors for "Lock table overflow" in sm21 and in file ENQHISOVR at /usr/sap/PR0/DV*/work found following entries:

EnqStoreTopHist: Lock Table Overflow at 2009/02/27 20:59:55 caused by

Cnt= 89480 Cli=400 Uname=EKOVALE Tcode=VT01N

Owner1=20090227202840993302001204pr0-04..........................

Owner2=20090227202840993302001204pr0-04..........................

Cnt= 814 Cli=400 Uname=B_PRD_BATCH Tcode=VT02N

Owner1=20090227205639255519001304pr0-04..........................

Owner2=20090227205639255519001304pr0-04..........................

Cnt= 148 Cli=400 Uname=LTOBIAS Tcode=CO11N

Owner1=20090227202839141759000705pr0-05..........................

Owner2=20090227202839141759000705pr0-05...........................

It seems other than updates also lock table overflow issue occured for specific user when they were using tcodes VT01N and VT02N.

We have ECC 500 witrh SP17.

a Quick help is needed.

Gopesh

[jens_hoetger]

Hello,

you may take a look on SAP notes 604473, 660133, 364248.

Also you may have a very ugly side effect from the overflow of the lock table: I recommend to check your periodically scheduled jobs which started in the period of the problem with your locktable. I guess the next job couldn't be scheduled because of enqueue problems...

If this occurred you have to figure out the jobs via comarision of 2 lists:

1st: jobs periodically scheduled which ran in the past

SE16 -> table TBTCO with field PERIODIC = 'X' and STATUS != 'P'

2nd: jobs peridically scheduled in the future

SE16 -> table TBTCO with field PERIODIC = 'X' and Status = 'S'

Jobs found in list 1, but not in list 2 have to be scheduled again. -> SM37, "Job" -> "Repeat Scheduling".

HTH and kind regards

Jens Hoetger

[Former Member]

What are the dumps that you are getting and what is the current release of your system

Also trying using note 1092188,might help you

Rohit