Lock table overflows - what does it notify

[Former Member]

Hi Friends,

When I am dealing with the population of internal table, the ends gets ended with the waring message " Lock table overflows ".

I guess, Internal table gets records more than its storage limit....If so do u have any way to increase the memory using abap statement occurs xxxx..

otherwise....Where it goes wrong..

I appreciate ur effort in sorting out the issue..

U have a good day

Thanks,

Matthew

[RichHeilman]

Lock table overflows means that their are too many locks in the system at that point in time. Check SM12 to see these locks. Is your program causing all these locks or is it something else.

Regards,

Rich Heilman

[Former Member]

Heilman,

Thanks for the information...I have been working with that

This is what the SAP help information in run time :

Lock table overflow

Message no. MC603

Lock table overflow

Message no. MC603

Diagnosis

This table overflowed when trying to enter SAP locks in the lock table.

System Response

The locks could not be set.

Procedure

Contact your system administrator. If this error occurs frequently, change the size of the profile parameter 'enque/table_size'. This parameter defines the size of the lock table in KByte.

ends

During runtime only, this prg gets lock which could be seen in SM12. Does it deal with locking concepts in DB table or internal table.

How the locks could not be set , Why do we need to set the lock...Could u share with me.

How to change the size of the profile parameter 'enque/table_size'. This parameter defines the size of the lock table in KByte.

You could send the portal link of SAP locks concepts.

I appreciate ur help in due time..

Thanks

Matthew

[Former Member]

The maximum number of locks in the lock table is subject to an upper limit. If it has reached the limit, you will get this message. Inform your Basis folks to delete the entries and make space. They will be able to help you.

If you need more info.

A lock table overflow can occur if:

· The lock table is configured too small

· An application sets a large number of locks

· The update process is hanging and this is passing a lot of locks onto the update task.

To analyze choose (SM12) Extras Statistics to display the statistics. These are the statistics that have been compiled since the last time the lock server was restarted.

The size of the lock table can be increased. As the number of records updates increases and crosses the limit of the lock table size it happens.

Hope this helps

Vinodh Balakrishnan

[Former Member]

Bala,

Thanks for the information...I have been working with that

This is what the SAP help information in run time :

Lock table overflow

Message no. MC603

Lock table overflow

Message no. MC603

Diagnosis

This table overflowed when trying to enter SAP locks in the lock table.

System Response

The locks could not be set.

Procedure

Contact your system administrator. If this error occurs frequently, change the size of the profile parameter 'enque/table_size'. This parameter defines the size of the lock table in KByte.

ends

During runtime only, this prg gets lock which could be seen in SM12. Does it deal with locking concepts in DB table or internal table.

How the locks could not be set , Why do we need to set the lock...Could u share with me.

How to change the size of the profile parameter 'enque/table_size'. This parameter defines the size of the lock table in KByte.

You could send the portal link of SAP locks concepts.

I appreciate ur help in due time..

Thanks

Matthew

[Former Member]

Matthew,

Click the SAP Help link for SAP Lock Concept

Normally the lock entries are created and deleted automatically by R/3 System.For example if Dispatcher for an instance or entire instances suddenly fails, obsolete lock entries may sometimes remain in the system. Lock entries can also remain in the system if users switch off their computers without first logging off the r/3 system. This is the most frequent cause of obsolete lock entries.

You must check the lock entries daily and, if necessary, delete them manually.

· You should analyze lock entries that are kept for a particularly long time. To display more information about an entry, such as the transaction code that created the lock entry, double click the entry.

· If the lock entries were caused by an update, check the update transactions.

· Check whether the user for a lock entry is still logged on.

· Do not delete locks unless you are absolutely certain about what you are doing.

Hope this helps

Vinodh Balakrishnan