Data Description

The HDB_DBCC_RLOCK event is used in SAP to provide an overview of the status of HANA Database Record locks.

Potential Use Cases

This event could be used in the following scenarios:

  • Determine an overview of the status of record locks i.e. lock type, record id, table name, etc.

  • Monitor to determine if critical tables records are locked and send alerts

  • Determine how frequently records from the critical tables are locked

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->Record Locks and currently locked records 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

RECORD_ID

Record ID

String

SCHEMA_NAME

Schema Name

String

TABLE_NAME

Table Name

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.

+ | -