Re: Best Practices for Oracle CRS Setup for a BIG Transaction Volume Benchmark ?
- From: "LS Cheng" <exriscer@xxxxxxxxx>
- To: VIVEK_SHARMA@xxxxxxxxxxx
- Date: Mon, 15 Oct 2007 21:17:53 +0200
1. Yes
2. No
3. IPMP or Sun Traffic Manager
Try Metalink
Thaks
--
LSC
On 10/15/07, VIVEK_SHARMA <VIVEK_SHARMA@xxxxxxxxxxx> wrote:
>
> Folks
>
>
>
> For an upcoming BIG Transaction Volume 3 Node RAC Benchmark, what are the
> *best practices* for ORACLE CRS Setup ?
>
>
>
> 1. Can Multiple Private Interconnects be setup between each RAC
> Pair?
> 2. Can Multiple "Private Node Names" be defined for each "Public
> Node Name" during CRS installation?
> 3. Do Multiple Network Interfaces of Interface Type "Private" need
> to be defined during CRS installation?
>
>
>
> *Any Docs, Links will help.*
>
>
>
> NOTE – Am familiar with CRS installation of 2 Node RAC with Single Private
> Interconnect.
>
>
>
> Cheers & Thanks
>
>
>
> Vivek
>
>
>
> SETUP:-
>
> Oracle 10gR2
>
> Solaris 10
>
> Cluster filesystem – QFS
>
> Each DB Server Node model = SF 25K
>
> Num of CPUs in Each Node = 40
>
> Storage - Sun Storagetek 9990 Base System storage box
>
>
> **************** 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:
