The ORA_DB02_BFFR event is used in SAP to check buffer busy waits in the Oracle database.
A buffer busy wait indicates that there are some buffers in the buffer cache that multiple processes are attempting to access concurrently. This event happens because one of the following is true:
An Oracle block is being read into the buffer cache by another session and the session is waiting for that read to complete.
The buffer is already in the buffer cache but in an incompatible mode (that is, some other session is changing the buffer).
Potential Use Cases
This event could be used in the following scenarios:
Create alerts based on the percent utilization.
Trend buffer utilization over time.
Identify slowdowns in the buffer cache.
The event will look like this in Splunk:
Log into the managed system and execute the dbacockpit transaction code. Then expand the Performance menu option on the left side of the screen, then expand the Wait Event Analysis menu option. Double-click on the Buffer Busy Wait option displayed. The information displayed on the screen will match the data that is extracted and sent to Splunk.
Unit of Measure
Average Time Waited (ms)
Oracle monitoring: COUNT
The date time stamp when the information was collected
Percent of Buffer Busy Waits
Percent of Buffer Busy Waits per Instance
Percent of Time of Buffer Waits
Percent of Time of Buffer Waits per Instance
Oracle monitoring: field Time
The UTC OFFSSET in HHMMSS that the data was collected in
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.
+ | -