SM12 Table Lock Concept

Lock Transaction SM12: The SAP system is equipped with a special lock mechanism the purpose of the lock mechanism is to prevent two transactions from changing the same data on the database simultaneously. Locks are defined generically as "lock objects" in the Data Dictionary. Lock entries are usually set and deleted automatically when user programs access a data object and release it again. The SAP lock mechanism is closely related to the Update Mechanism . The documentation is divided into the following sections: SAP Lock Concept: describes how the SAP lock works. You have to understand the concepts described here in order to use the SAP locks when you are programming applications. You can use different types of locks. The lock mode describes what type of lock it is. S (shared Lock): Several users can access locked data at the same time in display mode. Requests from further shared locks are accepted, even if they are from different users. An exclusive lock set on an object that already has a shared lock will be rejected. E(Exclusive): An exclusive lock protects the locked object against all types of locks from other transactions. Only the same lock owner can reset the lock .
Important Profile Parameters: A list of the profile parameters relevant for the lock concept. enque/table_size: Size of the lock table managed by the enqueue server in the main memory. The lock table contains information on which locks are currently held by whom.

In this case, you should check whether the update server is functioning correctly, since the lock table can grow very fast if the update function stops. If no update problems exist, you can use this parameter to increase the size of the lock table. The Computing Center Management System (CCMS) monitors the status of the lock table constantly and outputs warnings if the space available is not adequate. Default value: 4096kb

rdisp/wp_no_enq: Number of enqueue work processes that are to run on this instance. rdisp/enqname: Name of the application server that provides the enqueue service.
Managing Lock Entries: It describes lock management , which you use to display, check, and delete lock entries. This may be necessary if the SAP dispatcher, the operating system, or the network connection fails, and the dispatcher cannot delete lock entries. In this case, invalid lock entries remain effective and block access to the locked data when the system is restarted. How to monitor a Lock entry:In SM12 check any lock entry older than 2 days, if any outdated entry check the corresponding User and check the user online or offline in AL08 and contact that User (you can get the User info from su01) and inform about the lock else if the user is offline release the table from lock by deleting the lock.

ABAP DUMPS:
An error in an ABAP program that is running in a background generally causes an immediate termination of the background job. If an ABAP program terminates, an ABAP dump is usually generated. This dump contains a description of the precise cause of the error. Different Types of Dumps: Assign_base_too_Short: Call_function_conflict_type Call_function_open_error Call_function_receive_error dbif_RSQL_invalid_RSQL dbif_RSQL_SQL_Error Dataset_can't_open Export_too_much_data Load_program_lost Message_type_x Move_to_lit_notallowed_nodata Raise_exception Sapsql_array_insert_duprec Sapsql_invalid_fieldname Spool_i/o_error Table_invalid_index Time_out

SM13 Update Records: 1- Check if the 'Update System' is active.

2- If not active, investigate what happened 3- Activate 'Update System' after fixing the problem 4- Review update records of past two days and delete if errored or obsolete

In a system when ever a user performs any update on any table for that period of time a lock on that particular field of that table is created so that no other user can update that table as user one is doing update on that table. And Suppose during the update user session get terminated due to some error then this lock entry remains on that field. From this Screen we can check those type of locks. 1. Run T-Code SM12 Select Lock Entry window will come 2. Change the User name to * from Sukhmani because we have to report for all users and lick on list button from top or press F8

Lock Entry List window will come. From this window we only have to report those lock entry which are older then one day. For Ex. 400 BOXBERGER 03/10/2006 S MCH1 4000000000000150529060U00131019.