The HDB_DBCC_OLOCK event is used in SAP to provide an overview of the acquired locks on Hana Database objects.
Potential Use Cases
This event could be used in the following scenarios:
Determine overview of locked objects(tables) i.e. lock types, object type, object name, etc.
Monitor to determine if critical objects(tables) are locked and send alerts
Determine how frequently the critical objects are locked
Can be used to find which Transactions lock critical objects and schedule the execution of such transactions accordingly
Splunk Event
The event will look like this in Splunk:
SAP Navigation
Log in to the SAP system (having a HANA database) and execute the transaction DB01. Navigate to Diagnostics->Locks->Object Locks and currently locked objects will be displayed.
Field Mapping
Field
Description
Unit of Measure
EVENT_TYPE
SECPOL_LOG
String
EVENT_SUBTYPE
Not Applicable for this Event Type (always blank)
String
CURRENT_TIMESTAMP
The date time stamp when the information was collected
YYYYMMDDHHMMSS
HOST
Host Name
String
PORT
Internal Port
String
LOCK_OWNER_TRANSACTION_ID
Transaction object ID owning the lock
String
LOCK_OWNER_UPDATE_TRANSACTION_
Write transaction ID owning the lock
String
ACQUIRED_TIME
Lock acquisition time
YYYYMMDDHHMMSS
OBJECT_OID
Object OID
String
SCHEMA_NAME
Schema Name
String
OBJECT_NAME
Object Name
String
OBJECT_TYPE
Object Type
String
LOCK_MODE
Lock mode: EXCLUSIVE, INTENTIONAL EXCLUSIVE
String
UTCDIFF
The UTC OFFSSET in HHMMSS that the data was collected in
HHMMSS
UTCSIGN
The UTC positive or negative OFFSET indicator. Positive (+) means add UTCDIFF to find the time zone of the data, negative (-) means subtract the UTCDIFF to find the time zone adjusted date time the data was collected in.
+ | -
JavaScript errors detected
Please note, these errors can depend on your browser setup.
If this problem persists, please contact our support.