|
|
|
|||||||
| read by other session wait event
read by other session occurs when two users need access to the same block of data. The first user reads the data from disk and places it in the buffer cache. The second user has to wait for the first users operation to complete so they are placed in to waiting. This is when the read by other session wait occurs. Unfortunately this is one of those events we need to "catch in the act" to properly resolve. Recommendation:
Once a common block has been identified use this query to identify the hot object:
The next step is to tune queries that interact with this object. Secondly increasing PCTFREE and allowing for less dense blocks may address the problem, depending on the real root cause however the best solution is SQL tuning. A third option is to move the table to a smaller tablespace, rather than the current 16k tablespace size, to reduce the amount of data in each block. Note: PCTFREE is still required even with ASSM because it determines how rows will be packed into blocks, while freelists, pctused and pctincrease are ignored with ASSM because they are used for transaction/block management.
|
||
Use Xattr CloudFiler™ to dedup, encrypt and move your RMAN backups to the cloud. |
Recent Posts
|
|
| OptionalRegion1 | ||
| This site recommends Burleson Consulting for DBA Support & Consulting. | ||
|
We are currently paying for accepted Oracle 10g DBA & Business Intelligence articles, scripts, tips & tricks. Send yours to the editor and we will review within three weeks. Editorial submissions & questions: editor@oraclegiants.com
|
||
|
This
site is moderated by an:
|
|
|
| Classic Car Online - The #1 spot for classic and muscle car enthusiats |
| 2010 OracleGiants.com |