Hi Steve,
thanks for your suggestion, my on-site engineers will try your trick!
> In any case, it would be helpful to see the output of V$SYSTEM_EVENT, to
> get more info on what your hold ups really are.
The output looks like this:
EVENT
TOTAL_WAITS TOTAL_TIMEOUTS TIME_WAITED AVERAGE_WAIT
- -------------- ----------- ------------
Null
event
1 1 0 0
latch
free
5 5 0 0
pmon timer
274 274 0 0
process
startup
8 0 0 0
rdbms ipc
reply
7 0 0 0
rdbms ipc message
2549 809 0 0
imm
op
10 0 0 0
io done
2796 0 0 0
slave wait
3227 422 0 0
control file sequential read
181 0 0 0
control file parallel write
332 0 0 0
EVENT
TOTAL_WAITS TOTAL_TIMEOUTS TIME_WAITED AVERAGE_WAIT
- -------------- ----------- ------------
refresh controlfile
command 1
0 0 0
write complete
waits
14 0 0 0
buffer busy
waits
8 0 0 0
log file sequential
read 12
0 0 0
log file single
write
17 0 0 0
log file parallel write
2795 0 0 0
log file switch
completion
5 0 0 0
log file sync
475 0 0 0
db file sequential read
39755 0 0 0
db file scattered
read 21
0 0 0
db file parallel write
3342 2 0 0
EVENT
TOTAL_WAITS TOTAL_TIMEOUTS TIME_WAITED AVERAGE_WAIT
- -------------- ----------- ------------
direct path read
192 0 0 0
direct path write
144 0 0 0
instance state
change
1 0 0 0
smon
timer
5 2 0 0
library cache
pin
2 0 0 0
file
identify
45 0 0 0
file open
184 0 0 0
SQL*Net message to client
186085 0 0 0
SQL*Net message from client
186084 0 0 0
SQL*Net more data from client
5621 0 0 0
Thanks again,
Brian
Received on Wed Feb 02 2000 - 16:05:45 CST
