Hierarchy
⤷ BC-TWB-TST-P-PA (Application Component) Performance Analysis (Transaction ST05)
⤷ SQLT (Package) Trace for SQL, Enqueue, RFC, Memory
Basic Data
Data Element | E_OPER |
Short Description | Lock Operation |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | CHAR10 | |
Data Type | CHAR | Character String |
Length | 10 | |
Decimal Places | 0 | |
Output Length | 10 | |
Value Table |
Further Characteristics
Search Help: Name | ||
Search Help: Parameters | ||
Parameter ID | ||
Default Component name | ||
Change document | ||
No Input History | ||
Basic direction is set to LTR | ||
No BIDI Filtering |
Field Label
Length | Field Label | |
Short | 10 | Operation |
Medium | 15 | Lock Operation |
Long | 20 | Lock Operation |
Heading | 14 | Lock Operation |
Documentation
Definition
Description of the performed lock operation.
The lock operations have the following meaning:
ENQUEUE Set lock for lock object or increase lock counter for this lock object
DEQUEUE Remove lock for lock object or decrease object counter if there are multiple locks
DEQUEUE_ALL Remove all locks on all lock objects for one owner that is identified by the enqueue owner ID or the enqueue transaction ID
REMOVE Delete any locks, that is, also other owners' locks - for example with SM12
GETUSER Determine own enqueue owner ID (for example, to pass to an RFC function module, if the locks in the RFC function module are to be made under the owner ID of the caller
ENQUEUE_PERM Save the locks inherited by an update request from the backup file
QUERY Read lock entries from the lock table. (Is used for high availability solutions ) By default, lock entries are read using RFC.
GET_STAMP Acquire unique, guaranteed increasing numbers. (Is used, for example, for qRFC.)
STATISTICS Read statistics for the enqueue server.
OPERATIONS FOR SPECIAL USES SUCH AS ERROR DIAGNOSIS; ADMINISTRATION, and so on.
LOG_ON Activate logging. The operations of the enqueue server are recorded in the ENQLOG<nr> files for diagnosis purposes. This recording usually allows the diagnosis of lock operations of application programs.
LOG_OFF Deactivate logging.
BCK_ON Activate backup file. During an update call, the inherited locks are saved to backup file , so that they can, like the update call, survive a restart. The backup file is activated by default. For special performance-related special cases, it can, however, be deactivated by agreement with the customer. In this case, you must ensure that there no open update requests exist at shutdown or after the startup using administrative tools, you can ensure that all existing update requests are processed before new transactions are started.
BCK_OFF Deactivate backup file, compare with operation BCK_ON
GET_ENQID Read the lock table ID, for example to determine whether the lock table contents were lost between client and server during a temporary disconnection and reconnect.
CLEANUP_USER like DEQUEUE_ALL, but ownerID can contain wildcard characters. Is used to delete the locks of all owners in an application during startup and shutdown,
ENQUEUE_ON Activation of the emergency operation mode; lock operations deliver ok, but do nothing. Is used to be able to execute diagnosis and administration transactions even in the case of partial breakdown of the SAP R/3 Systems.
ENQUEUE_OFF Deactivates emergency operation mode - compare with operation ENQUEUE_ON.
ENQUEUE_STATE Queries whether emergency operation mode is activated
SET_ENQID Used for diagnosis purposes.
GET_HRES_TIME Used for diagnosis purposes.
STATE_TRANSFER Used for diagnosis purposes in high availability solutions.
LOG_ON_REPL Activates the recording of replicated lock entries for dialog purposes for the high availability solutions based on the standalone server.
LOG_OFF_REPL Deactivate recording - compare with operation LOG_ON_REPL.
CLRSTAT Reset time measurement statistics in the client interface.
GETSTAT Read time measurement statistics in the client interface.
DUMP For diagnosis purposes.
VERIFY For diagnosis purposes.
History
Last changed by/on | SAP | 20010130 |
SAP Release Created in | 50A |