on 11-24-2011 11:36 AM
Hi All,
We have a requirement for setting up oracle RAC for production system.
The scenario is that we have got four RAC nodes and it'll work as an active/active (first pair), active/active(second pair) clusters ,our requirement is to install ERP and EP system on first pair , PI and SOLMAN for second pair.
So in the first RAC pair two DB instances of ERP & EP + ASCS instance of ERP+Enqueue Replication Server of ERP. + SCS of EP+Enqueue Replication Server EP ).
So now our confusion is that which approach we should take for installing the SAP on the first two nodes.since direct oracle RAC installation is not possible we need to go for single instance installation and then migrate to ORacle RAC.
It would be helpful if anybody can give proper guidance for installing SAP by the given approach (with ASCS and ERS).we need help for installing SAP only,oracle migartion part DB team will takecare .
What is the purpose of Virtual Ip's here and how many VIP's we need in the above mentioned scenario for installing ASCS&ERS in r/3 and SCS&ERS in EP.In which phase we need to install SAPCTL and how does it work?
Anybody please help ASAP......
Edited by: SAP Basis2411 on Nov 24, 2011 1:21 PM
Hi,
Refer to SAP Note 527843 - Oracle RAC support in the SAP environment
Here you can find RAC support info for SAP environment.
Here you can get many documents on SAP installations on RAC. Based on your OS/DB platform you can choose relevant document.
Regarding Virtual IPs, you will need atleast 3 IPs per SAP solution setup.
So for ECC = 3
For EP = 3
etc.
2 Virtual IPs are needed for failover situations and 1 for hearbeat.
Hope this helps.
Regards,
Deepak Kori
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
Information on SAPCTL
======================
In addition to the critical SAP high availability components, namely the SAP Enqueue
and SAP Replication Service, SAPCTL Version 6 provides an interface for the
protection of arbitrary number of SAP application instances.
The SAP Central Instance (CI) or SAP application instances (DV) are possible
candidates to run under SAPCTL supervision.
The SAPCTL tool supports SAP Standalone Gateway (GW) and SAP WebDispatcher
(W) as independent SAP instances as well.
For all supported SAP instance types, SAPCTL in addition monitors the associated SAP
Start Service (sapstartsrv daemon process) with an always co-located CRS resource. The
SAP Start Service process is started automatically by SAPCTL if the SAP instance gets
started on a cluster node or relocated to another node in the cluster. There is no need to
bring up all SAP Start Processes on system boot by sapinit procedure as this task is
performed by SAPCTL after startup of Oracle Clusterware.
SAPCTL is available for the LINUX, Solaris and AIX operating system.
Oracle Clusterware 11g Release 2 is required for this version of SAPCTL.
All SAP kernels starting with kernel version 7.00 are supported by SAPCTL.
For ERS related best approch refer to following document.
Hope this helps.
Regards,
Deepak Kori
User | Count |
---|---|
90 | |
10 | |
10 | |
10 | |
7 | |
7 | |
6 | |
5 | |
4 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.