10.4 Preparing the SAP Environment
Before beginning the SAP or Sun Cluster HA for SAP installation procedures, perform the following prerequisite tasks.
-
Load the Solaris operating environment and any required Solaris patches.
-
Install Volume Manager software and any required Volume Manager patches.
-
Create Solstice DiskSuite disksets or SSVM disk groups (separate disk groups for the central instance and database instance are recommended).
-
Create volumes according to Sun Cluster guidelines:
-
Mirror volumes across controllers
-
With SSVM, use Dirty Region Logging for faster mirror resynchronization
-
Use a logging file system for faster logical host failover
Use Table 10-4 as a worksheet to capture the name of the volume that corresponds to each file system used for the SAP central instance. Refer to the SAP installation guide for the file system sizes recommended for your particular configuration. These are database-independent file systems.
-
|
File System Name / Mount Point |
Volume Name |
|---|---|
|
/usr/sap/trans |
|
|
/sapmnt/<SAPSID> |
|
|
/usr/sap/<SAPSID> |
|
Use Table 10-5 as a worksheet to capture the name of the volume that corresponds to each file system used for the database instance. Refer to the SAP installation guide for the file system sizes recommended for your particular configuration. These are database-dependent file systems.
Table 10-5 Worksheet: File Systems and Volume Names for the SAP Database Instance|
File System Name / Mount Point |
Volume Name |
|---|---|
|
/oracle/<SAPSID> |
|
|
/oracle/stage/stage_<version> |
|
|
/oracle/<SAPSID>/origlogA |
|
|
/oracle/<SAPSID>/origlogB |
|
|
/oracle/<SAPSID>/mirrlogA |
|
|
/oracle/<SAPSID>/mirrlogB |
|
|
/oracle/<SAPSID>/saparch |
|
|
/oracle/<SAPSID>/sapreorg |
|
|
/oracle/<SAPSID>/sapdata1 |
|
|
/oracle/<SAPSID>/sapdata2 |
|
|
/oracle/<SAPSID>/sapdata3 |
|
|
/oracle/<SAPSID>/sapdata4 |
|
|
/oracle/<SAPSID>/sapdata5 |
|
|
/oracle/<SAPSID>/sapdata6 |
|
-
Install Sun Cluster, Sun Cluster HA for SAP, Sun Cluster HA for Oracle, and any required patches. Use the procedures described in Chapter 3, Installing and Configuring Sun Cluster Software, but do not set up logical hosts with scinstall(1M) during this installation. Instead, set up logical hosts with scconf(1M) after the cluster is up. Set up two disksets per logical host.
-
Configure PNM on all nodes.
-
Start the cluster.
-
(SSVM only) Verify that all disk groups are deported.
-
(Solstice DiskSuite) Release ownership of all disksets.
-
Create logical hosts with scconf(1M); the number of logical host depends on your particular configuration. See the section on adding and removing logical hosts in the Sun Cluster 2.2 System Administration Guide. You will need:
-
logical host name(s)
-
physical host names of potential masters of logical host(s)
-
names of the primary public network controllers for the potential masters of the logical host(s)
-
disk group name(s)
When you create logical hosts, disable the automatic failback mechanism by using the -m option to scconf(1M).
-
-
(SSVM, two-node configurations only) Configure the shared CCD.
-
After creating the logical host(s), create the logical host administrative file system. For detailed procedures, see Appendix B, Configuring Solstice DiskSuite, or Appendix C, Configuring Sun StorEdge Volume Manager and Cluster Volume Manager.
-
As part of the logical host configuration, create mount points for the central instance and database instance volumes, and enter them into the respective vfstab.logicalhost files on all potential masters of each logical host. These files are located in /etc/opt/SUNWcluster/conf/hanfs.
Table 10-6 lists the suggested file system mount points for the disk groups (SSVM) or disksets (Solstice DiskSuite) associated with the central instance and database instance. Note that separating the central instance and database instance file systems into separate disk groups or disksets (even if using a single logical host) may provide more configuration flexibility in the future.
|
Disk Group (SSVM) |
Diskset (Solstice DiskSuite) |
Volume Name |
Mount Point |
|---|---|---|---|
|
ci_dg |
CIloghost |
sap |
/usr/sap/<SAPSID> |
|
ci_dg |
CIloghost |
saptrans |
/usr/sap/trans |
|
ci_dg |
CIloghost |
sapmnt |
/sapmnt/<SAPSID> |
|
db_dg |
DBloghost |
oracle |
/oracle/<SAPSID> |
|
db_dg |
DBloghost |
stage |
/oracle/stage/stage_<version> |
|
db_dg |
DBloghost |
origlogA |
/oracle/<SAPSID>/origlogA |
|
db_dg |
DBloghost |
origlogB |
/oracle/<SAPSID>/origlogB |
|
db_dg |
DBloghost |
mirrlogA |
/oracle/<SAPSID>/mirrlogA |
|
db_dg |
DBloghost |
mirrlogB |
/oracle/<SAPSID>/mirrlogB |
|
db_dg |
DBloghost |
saparch |
/oracle/<SAPSID>/saparch |
|
db_dg |
DBloghost |
sapreorg |
/oracle/<SAPSID>/sapreorg |
|
db_dg |
DBloghost |
sapdata1 |
/oracle/<SAPSID>/sapdata1 |
|
db_dg |
DBloghost |
sapdata2 |
/oracle/<SAPSID>/sapdata2 |
|
db_dg |
DBloghost |
sapdata3 |
/oracle/<SAPSID>/sapdata3 |
|
db_dg |
DBloghost |
sapdata4 |
/oracle/<SAPSID>/sapdata4 |
|
db_dg |
DBloghost |
sapdata5 |
/oracle/<SAPSID>/sapdata5 |
|
db_dg |
DBloghost |
sapdata6 |
/oracle/<SAPSID>/sapdata6 |
-
If SAP application servers will be configured outside the cluster, then configure Sun Cluster HA for NFS and enter the appropriate shared file systems into the dfstab.logicalhost files on all potential masters of each logical host. These files are located in /etc/opt/SUNWcluster/conf/hanfs. See "10.2.4 Configuration Options for Application Servers and Test/Development Systems", and Chapter 11, Setting Up and Administering Sun Cluster HA for NFS, for more information.
Share the following file systems to SAP application servers outside the cluster. These are general guidelines. See the SAP documentation for more information.
|
File Systems to Share to External Application Servers |
|---|
|
/usr/sap/trans |
|
/sapmnt/<SAPSID>/exe |
|
/sapmnt/<SAPSID>/profile |
|
/sapmnt/<SAPSID>/global |
-
Test the functionality and mount points of the logical host(s) by switching them between all potential masters. This verifies that all mount points have been created correctly.
-
Adjust kernel parameters on all potential masters, as per the "R/3 Installation on UNIX: OS Dependencies" guidelines in the SAP documentation. In configurations where the central instance and database instance may coexist with each other or with other instances, be sure to size the kernel parameters accordingly.
-
Create appropriately sized permanent swap areas on all potential master nodes. See the Installation Requirements Checklist in your SAP documentation for swap guidelines. Use the SAP-supplied memlimits utility to assist you in sizing the swap space. See the "R/3 Installation on UNIX" guidelines in the SAP documentation for more information on this utility.
-
Stop the cluster and reboot all nodes after adjusting kernel parameters and swap space.
-
Create SAP and database user and group accounts on all potential masters of the logical hosts. Refer to the "R/3 Installation on UNIX: OS Dependencies" guidelines in the SAP documentation for details. User and group IDs must be identical on all nodes. Create the home directories for these users on the shared diskset. Table 10-8 shows suggested home directory paths for the user accounts.
|
User |
Home directory |
|---|---|
|
<sapsid>adm |
/usr/sap/<SAPSID>/home |
|
ora<sapsid> |
/oracle/<SAPSID> |
Note -
For SAP 4.0b, read OSS note 0100125 for special steps required when creating user home directories outside of the /home location.
After all of these prerequisites have been fulfilled, proceed to "10.5 Installing and Configuring SAP and the Database".
- © 2010, Oracle Corporation and/or its affiliates