| Direct Path Wait event [message #614512] |
Thu, 22 May 2014 13:28  |
guru_karnam
Messages: 142
Registered: May 2005
|
Senior Member |
|
|
How to tune Direct Path Wait Event?
WAIT_EVENT TIME_WAITED
Idle 608679137
User I/O 18453705
Commit 3203799
System I/O 3119861
Application 111518
Concurrency 108803
Network 57015
Other 29079
Configuration 11815
USER I/0
direct path write temp 7046394
db file sequential read 4851947
direct path read 2442452
read by other session 1873309
direct path read temp 844338
db file scattered read 816091
direct path sync 616623
db file parallel read 211920
flashback log file sync 47662
Disk file operations I/O 40962
local write wait 31636
[EDITED by LF: fixed topic title typo; was "drect"]
[Updated on: Sun, 25 May 2014 09:12] by Moderator Report message to a moderator |
|
|
|
|
|
|
|
|
|
|
|
|
|
| Re: Drect Path Wait event [message #614622 is a reply to message #614512] |
Fri, 23 May 2014 20:27  |
 |
Kevin Meade
Messages: 2103
Registered: December 1999
Location: Connecticut USA
|
Senior Member |
|
|
Roachcoach is at least half right. If we think of a WAIT as waiting on something to get done (what else would it be), then there are really only two ways to deal with it. Here are these two ways in priority order.
1. change what you do so you need less of whatever you are waiting on
2. make whatever you are waiting on faster
My first question though is, DO YOU HAVE A PROBLEM? or are you just looking at some stat and thinking "hey that is the biggest one so if I make it smaller things will be better."?
Do you have a user complaining that something is taking too long or a process not meeting an SLA? If not then there is no need to "tune this wait event" because "direct path write temp 7046394"
means pretty much nothing given a lack of context.
Kevin
|
|
|
|
] 
Blog
Search
Help
Members
Register
Login
Home
