| Top wait event - control file sequential read [message #432185] |
Sun, 22 November 2009 17:30  |
oracleperm
Messages: 2
Registered: November 2009
Location: California
|
Junior Member |
|
|
Hi friends,
From AWR reports, the top wait event is "control file sequential read". The control files are located on ASM diskgroup with raid 10 (mirror and stripe). How can I know the ASM disk(s) associated with the control files, and what disks are the hot disks that causing this wait event?
Any advice is greatly appreciated.
Thanks,
Jenny -
|
|
|
|
|
|
|
|
| Re: Top wait event - control file sequential read [message #436700 is a reply to message #432185] |
Fri, 25 December 2009 21:30  |
 |
BlackSwan
Messages: 26766
Registered: January 2009
Location: SoCal
|
Senior Member |
|
|
Top wait event
In EVERY Top Wait Event list, one wait event will ALWAYS be on top as #1; by definition of the list.
Simply because any item, even #1, appears on this list does not mean this is a problem & needs to be fixed.
If the Top Wait Event accounts for only 5 seconds out of a 1 hour sample,
then reducing it to ZERO won't measurably improve overall application performance.
The actual Time Waited is required to determine if it is a problem or not.
[Updated on: Fri, 25 December 2009 21:31] Report message to a moderator |
|
|
|
] 
Blog
Search
Help
Members
Register
Login
Home
