Re: Performance tuning of a system
- From: rjamya <rjamya@xxxxxxxxx>
- To: s.cislaghi@xxxxxxxxx, ORACLE-L <oracle-l@xxxxxxxxxxxxx>
- Date: Tue, 4 Sep 2012 09:45:16 -0400
Or, (assumption alert), most likely the said vendor apps wont be using
module and/or action and/or client_info (i.e. dbms_application_info),
so you could populate those fields in the logon trigger. Then let
ASH/AWR do their work, perhaps adjust AWR snapshot frequency to
something less than an hour (which is default). Then run AWR reports
for specific strings in module/action/client_info based on what you
have set in the logon trigger.
Granted the tracing method is most detailed/complete but this method
will be quick, involve less resources and once you get a good picture,
then you can drill into it using 10046. Of course I am also assuming
you are licensed for A[SH/WR/DDM] suitably. If vendor app uses all
three columns using dbms_application_info, then Chris has given you a
solution already. You should note that ASH/AWR will give you the heavy
hitters first .. the 10046 will give you everything minus the kitchen
sink.
Raj
--
//www.freelists.org/webpage/oracle-l
Other related posts:
