The RAc database has been switch to DEDICATED mode, why do we still recieve two statspack report and which one should we concentrate on????
Thanks,
Printable View
The RAc database has been switch to DEDICATED mode, why do we still recieve two statspack report and which one should we concentrate on????
Thanks,
what do you think the connection mode has anything to do with statspack?Quote:
Originally posted by learning_bee
The RAc database has been switch to DEDICATED mode, why do we still recieve two statspack report and which one should we concentrate on????
Thanks,
you are getting a report per instance
thanks Davey,
what do you think of the below info form statspack???
why the Execute to Parse is so low and the wait time in global cache cr request huge????Code:
Instance Efficiency Percentages (Target 100%)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Buffer Nowait %: 99.72 Redo NoWait %: 100.00
Buffer Hit %: 99.01 In-memory Sort %: 100.00
Library Hit %: 93.10 Soft Parse %: 74.57
Execute to Parse %: 62.10 Latch Hit %: 99.09
Parse CPU to Parse Elapsd %: 75.09 % Non-Parse CPU: 83.02
Shared Pool Statistics Begin End
------ ------
Memory Usage %: 92.12 91.59
% SQL with executions>1: 49.31 44.67
% Memory for SQL w/exec>1: 23.97 21.91
Top 5 Timed Events
~~~~~~~~~~~~~~~~~~ % Total
Event Waits Time (s) Ela Time
-------------------------------------------- ------------ ----------- --------
CPU time 3,996 32.13
global cache cr request 4,878,612 2,252 18.11
db file scattered read 765,763 1,811 14.56
enqueue 7,223 1,469 11.81
db file sequential read 632,876 972 7.82
thanks,
i am hazarding a guess that you aren't using a binds a whole lot (look at your soft parse ratio %), that is causing you problems I would guess
that's absolutely right and unfortunately we can't change the code. I did enforce session_cached_cursors to hope improving performance but no luck. One more thing, I really suspect is DISK I/O.
rac will only make you parsing problem worse
Do you have any recommndation at this point????
thanks again
how long was the report run for?
yeah, fix the parsing problemQuote:
Originally posted by learning_bee
Do you have any recommndation at this point????
thanks again
Smontgo,
the report ran over 10 hours.