read by other session
This event occurs when a session requests a buffer that is currently being read into the buffer cache by another session.
Detailed Description​
This is a marker to show when blocks are being accessed concurrently. When a block is requested by two sessions one will have to wait for the first request to complete. Prior to release 10.1, waits for this event were grouped with the other reasons for waiting for buffers under the 'buffer busy waits' event.
How to reduce this wait​
If this is a significant wait in your system, the application performance as a whole may suffer. The parameters of the wait will point to the object in question. This could be a busy index block or concurrent table scans happening. Investigations should focus on eliminating the cause of contention in these 'hot blocks'.
Additional Links​
- Oracle Reference Manual - read by other session
- LogicalRead article on read by other session waits
- Oracle Base script to identify Hot Blocks
Search online​
If this article doesn't have the information you need you can try searching online. Remember, you can contribute suggestions to this page.