RE: Statspack setup for 2nd RAC instance ?...basic Qs

  • From: "VIVEK_SHARMA" <VIVEK_SHARMA@xxxxxxxxxxx>
  • To: <tim@xxxxxxxxx>, <oracle-l@xxxxxxxxxxxxx>
  • Date: Wed, 7 Feb 2007 01:47:00 +0530

Thanks Tim as always for the support & explanation in such simple
language.



It worked. I simply executed "exec statspac.snap" from the 2nd instance
& the 2nd started appearing thereafter in the sprepins.sql Output



Would you still recommend the following parameters (as picked up from
your site) for RAC with 10gR2 & advised by Barbara?



exec statspack.modify_statspack_parameter( -

        i_snap_level => 7, -

        i_executions_th => 1000, -

        i_parse_calls_th => 1000, -

        i_disk_reads_th => 10000, -

        i_buffer_gets_th => 100000, -

        i_sharable_mem_th => 1048576, -

        i_version_count_th => 20, -

      i_seg_itl_waits_th => 1)



NOTE - We aim to collect Statspack for Benchmark Runs on a Hybrid
Banking Application product



Cheers



-----Original Message-----
From: oracle-l-bounce@xxxxxxxxxxxxx
[mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of Tim Gorman
Sent: Wednesday, February 07, 2007 12:48 AM



Vivek,



Yes, you did communicate the issue sufficiently.  What you have not done
is

understand Barb's response sufficiently.



You only need to take at least two snapshots on an instance in order

for "spreport.sql" to have something against which to report.  The
STATSPACK

repository is always installed initially capable of handling data from

multiple OPS/RAC instances - there is no "installation" process for

additional OPS/RAC instances.  Barb provided you with instructions on
how to

schedule DBMS_JOB jobs on the second instance -- once those snapshots

happen, then "spreport.sql" will have something to report against.



Hope this helps...



-Tim





**************** CAUTION - Disclaimer *****************
This e-mail contains PRIVILEGED AND CONFIDENTIAL INFORMATION intended solely 
for the use of the addressee(s). If you are not the intended recipient, please 
notify the sender by e-mail and delete the original message. Further, you are 
not to copy, disclose, or distribute this e-mail or its contents to any other 
person and any such actions are unlawful. This e-mail may contain viruses. 
Infosys has taken every reasonable precaution to minimize this risk, but is not 
liable for any damage you may sustain as a result of any virus in this e-mail. 
You should carry out your own virus checks before opening the e-mail or 
attachment. Infosys reserves the right to monitor and review the content of all 
messages sent to or from this e-mail address. Messages sent to or from this 
e-mail address may be stored on the Infosys e-mail system.
***INFOSYS******** End of Disclaimer ********INFOSYS***

Other related posts: