HOT blocks
hi
here is a case i really appreciate your comment regarding that:
Please consider we have a simple query (a select statement with bind variables ) which is high used and many many sessions go for it
but at some of the times (not pick time always) these sessions became under ‘latch: cache buffers chains’ or ‘read by other session’ and considerable 'db file sequential read'
hot block will be on database
i know it is oracles behavior that it will first read the data from disk into the database buffer cache.
If two or more sessions request the same information then the first session reads data to the buffer cache while other sessions wait.
Please consider we have a simple query (a select statement with bind variables ) which is high used and many many sessions go for it
but at some of the times (not pick time always) these sessions became under ‘latch: cache buffers chains’ or ‘read by other session’ and considerable 'db file sequential read'
hot block will be on database
i know it is oracles behavior that it will first read the data from disk into the database buffer cache.
If two or more sessions request the same information then the first session reads data to the buffer cache while other sessions wait.
0