test

Sun Cluster 2.2 Data Services Update: SAP With Oracle, SAP With Informix

SAP With Informix

Use the information in the following sections to install and configure SAP with Informix. For information about installing and configuring SAP with Oracle, see "SAP With Oracle".

Installation and Configuration Overview (SAP With Informix)

Table 1-10 summarizes the tasks you must complete to install and configure SAP and Sun Cluster HA for SAP.

Table 1-10 Installation Overview for Sun Cluster HA for SAP (SAP With Informix)

Task 

See ... 

Prepare the cluster environment for SAP and Informix: 

 

- Install Solaris 

- Install and configure the volume manager 

- Create disksets or disk groups 

- Create volumes and file systems 

- Install Sun Cluster and the data services 

- Set up public network monitoring (PNM) 

- Set up logical hosts and mount points 

- Configure the shared CCD (SSVM, 2-node only) 

- Set up HA-NFS, if necessary 

- Adjust kernel parameters 

- Create links for Informix 

- Create and modify the administrative file systems 

- Configure Sun Cluster HA for NFS 

- Configure swap space and paging space 

- Create user and group accounts 

"How to Prepare the Cluster Environment for SAP and the Database (SAP With Informix)"

Install SAP and Informix: 

- Install SAP, Informix 

- Install other components as necessary, such as application servers 

- Install the SAP GUI 

- Shut down SAP and Informix 

"How to Install SAP and the Database (SAP With Informix)"

Enable SAP and Informix to run in the cluster environment: 

 

- Modify the Informix configuration files 

- Set up the SAP central instance environment 

- Modify the SAP database user environment 

- Update /etc/services and create /usr/sap/tmp - Test the SAP installation

"How to Enable SAP and the Database to Run in the Cluster Environment (SAP With Informix)"

Configure Sun Cluster HA for Informix: 

- Shut down SAP and Informix 

- Register and activate HA-Informix 

- Bring Informix under the control of HA-Informix 

- Start HA-Informix 

- Test switchover of the database 

"How to Configure Sun Cluster HA for Informix"

Configure Sun Cluster HA for SAP: 

- Register Sun Cluster HA for SAP 

- Configure Sun Cluster HA for SAP with hadsconfig(1M)

- Turn on Sun Cluster HA for SAP 

- Test switchover of SAP 

- Customize start and stop scripts for application servers 

- Set data service dependencies for SAP 

"How to Configure Sun Cluster HA for SAP (SAP With Informix)" and "How to Set a Data Service Dependency for SAP (SAP With Informix)"

Installation Worksheet for Sun Cluster HA for SAP (SAP With Informix)

Complete the following worksheet before beginning the installation procedures.

Table 1-11 Sun Cluster HA for SAP Installation Worksheet (SAP With Informix)

Name of the cluster 

 

Number of logical hosts 

 

Name and IP address of all physical hosts that are potential masters of the CI logical host 

 

Name and IP address of CI logical host 

 

SAP system ID (<SAPSID>)

 

SAP system number 

 

Name and IP address of all physical hosts that are potential masters of the DB logical host 

 

Name and IP address of DB logical host 

(In asymmetric configurations, this is identical to the CI logical host.) 

 

Name of NFS logical host (see Note below) 

 

SAP license for each potential master of the CI logical host 

 

Note -

If all application servers are external to cluster, the name of the NFS logical host is the same as the central instance logical host. If the application servers are inside the cluster, name of the NFS logical host is the logical host that provides NFS service from the external NFS cluster. See "Sun Cluster HA for NFS Considerations".

Installation and Configuration Procedures (SAP With Informix)

Perform the procedures in the order indicated in Table 1-10.

How to Prepare the Cluster Environment for SAP and the Database (SAP With Informix)

Before installing SAP and Informix, perform the following tasks.

  1. On all nodes, install the Solaris operating environment and Solaris patches.

    See Chapter 3, "Installing and Configuring Sun Cluster Software" in the Sun Cluster 2.2 Software Installation Guide.

  2. On all nodes, install Volume Manager software and any required Volume Manager patches.

    See Chapter 3, "Installing and Configuring Sun Cluster Software" in the Sun Cluster 2.2 Software Installation Guide.

  3. On the node on which you will install SAP and Informix, create Solstice DiskSuite disksets or SSVM disk groups.

    Separate disk groups for the SAP central instance and database instance are recommended, for ease of administration.

  4. On the node on which you will install SAP and Informix, 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 the following table as a worksheet to capture the name of the volume that corresponds to each file system used for the SAP central instance and database instance. Refer to the SAP installation guide for the file system sizes recommended for your particular configuration. The central instance file systems are database-independent; the database instance file systems are database-dependent. Use raw partitions for the database instances.

    Table 1-12 Worksheet: File Systems and Volume Names for the SAP Instances (SAP With Informix)

    File System Name 

    Volume Name 

    /usr/sap/trans

     

    /sapmnt/<SAPSID>

     

    /usr/sap/<SAPSID>

     

    /informix/<SAPSID>

     

  5. On all nodes, install Sun Cluster, Sun Cluster HA for SAP, Sun Cluster HA for Informix, and any required patches.

    Use the procedures described in Chapter 3, "Installing and Configuring Sun Cluster Software" in the Sun Cluster 2.2 Software Installation Guide, but do not set up logical hosts with scinstall(1M) during this installation (you will set up logical hosts with scconf(1M) in Step 10).

  6. On all nodes, configure PNM.

    For detailed procedures, see Chapter 3, "Installing and Configuring Sun Cluster Software" in the Sun Cluster 2.2 Software Installation Guide, and Chapter 6, "Administering Network Interfaces" in the Sun Cluster 2.2 System Administration Guide.

  7. Start the cluster.

    Run the following command on one node.


    # scadmin startcluster physicalhost clustername

    Run the following command on all other nodes, sequentially.


    # scadmin startnode

  8. (SSVM only) Verify that all disk groups are deported.

  9. (Solstice DiskSuite only) Release ownership of all disksets.

  10. On the node on which you installed SAP, create logical hosts with scconf(1M).

    The number of logical hosts depends on your particular configuration. You should set up two disk groups: one for SAP and one for Informix. You can place both disk groups on the same logical host, or configure one disk group per logical host (in a configuration with two logical hosts). See Chapter 3, "Installing and Configuring Sun Cluster Software" in the Sun Cluster 2.2 Software Installation Guide for more information.

    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).

  11. (SSVM, two-node configurations only) Configure the shared CCD.

    See Appendix C, "Configuring Sun StorEdge Volume Manager and Cluster Volume Manager" in the Sun Cluster 2.2 Software Installation Guide.

  12. Create mount points for the central instance and database instance volumes, and update the vfstab.logicalhost files on all potential masters of each logical host.

    The vfstab.logicalhost files are located in /etc/opt/SUNWcluster/conf/hanfs.

    The following table 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 different disk groups or disksets (even when you use a single logical host) may provide more configuration flexibility in the future

    Table 1-13 Disk Groups/Disksets and Mount Points for the SAP Central Instance and Database Instance (SAP With Informix)

    Disk Group or Diskset for the ... 

    Mount Point 

    Central instance 

    /usr/sap/<SAPSID>

    Central instance 

    /usr/sap/trans

    Central instance 

    /sapmnt/<SAPSID>

    Database instance 

    /informix/<SAPSID>

  13. On all nodes, create directories for Informix.


    # mkdir /informix
# mkdir -p /var/opt/informix
# cd /var/opt/
# chown informix:informix informix

  14. On the node on which you installed SAP and Informix, create Informix data directories and set up soft links.

    See your SAP installation documentation for more information. For example:


    # mkdir /informix/<SAPSID>/sapdata
# mkdir /informix/<SAPSID>/sapdata/physdev<n>
...
# ln -s /dev/vx/rdsk/dbdg/vol01 /informix/<SAPSID>/sapdata/physdev1/data1
# ln -s /dev/vx/rdsk/dbdg/vol02 /informix/<SAPSID>/sapdata/physdev1/data2
# ln -s /dev/vx/rdsk/dbdg/vol03 /informix/<SAPSID>/sapdata/physdev1/data3
# ln -s /dev/vx/rdsk/dbdg/vol04 /informix/<SAPSID>/sapdata/physdev1/data4
# ln -s /dev/vx/rdsk/dbdg/vol05 /informix/<SAPSID>/sapdata/physdev2/data5
# ln -s /dev/vx/rdsk/dbdg/vol06 /informix/<SAPSID>/sapdata/physdev2/data6
# ln -s /dev/vx/rdsk/dbdg/vol07 /informix/<SAPSID>/sapdata/physdev2/data7
# ln -s /dev/vx/rdsk/dbdg/vol08 /informix/<SAPSID>/sapdata/physdev2/data8
# ln -s /dev/vx/rdsk/dbdg/vol09 /informix/<SAPSID>/sapdata/physdev3/data9
# ln -s /dev/vx/rdsk/dbdg/vol10 /informix/<SAPSID>/sapdata/physdev3/data10
# ln -s /dev/vx/rdsk/dbdg/vol11 /informix/<SAPSID>/sapdata/physdev3/data11
# ln -s /dev/vx/rdsk/dbdg/vol12 /informix/<SAPSID>/sapdata/physdev3/data12

  15. On all nodes, create links from /var/opt/informix to the appropriate directory on the shared disk.

    For example: 


    # ln -s /informix/<SAPSID>/sapdata /var/opt/informix/sapdata# ln -s /informix/<SAPSID>/sapreorg /var/opt/informix/sapreorg

  16. On all nodes, create logical host administrative file systems, using scconf(1M).

    For detailed procedures, see Appendix B, "Configuring Solstice DiskSuite" and Appendix C, "Configuring Sun StorEdge Volume Manager and Cluster Volume Manager" in the Sun Cluster 2.2 Software Installation Guide.

  17. If SAP application servers will be configured outside the cluster, 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 "Configuration Options for Application Servers and Test/Development Systems" for more information.

    Share the following file systems to SAP application servers outside the cluster. These are general guidelines. See your SAP documentation for more information.

    Table 1-14 File Systems to Share to External Application Servers (SAP With Informix)

    File Systems to Share to External Application Servers 

    /usr/sap/trans

    /sapmnt/<SAPSID>/exe

    /sapmnt/<SAPSID>/profile

    /sapmnt/<SAPSID>/global

  18. 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.

  19. Adjust kernel parameters in the /etc/system files on all potential masters of the logical hosts.

    Follow 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.

  20. Create permanent swap areas on all potential masters of the logical hosts.

    See the "Installation Requirements Checklist" in your SAP documentation for swap size guidelines.

  21. On all nodes, check the paging space size.

    Use the SAP-supplied memlimits utility to assist you in checking the address space. See the "R/3 Installation on UNIX" guidelines in the SAP documentation for more information on this utility. As a general rule, swap should be at least three times the memory on a given node. See your SAP installation documentation for details.

  22. Stop the cluster and reboot all nodes.

  23. On all nodes, verify system resources.

    See your SAP installation documentation for details. 


    # ulimit -a...
time(seconds)	 unlimited
file(blocks) unlimited
data(kbytes) 2097148 
stack(kbytes) 8192
coredump(blocks) unlimited
nofiles(descriptors) 64
memory(kbytes) unlimited

  24. Create SAP and Informix groups, users, passwords, and home directories on all potential masters of the logical hosts.

    Create user home directories.


    # mkdir /export/home/<sapsid>adm
# mkdir /export/home/sapr3
# mkdir /export/home/informix

    Add the following users and groups. 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.


    # groupadd -g 10000 sapsys
# groupadd -g 10002 informix
# groupadd -g 10004 super_archive
# groupadd -g 10006 super_
# groupadd -g 10008 bargroup (for SAP4.5B only)
# useradd -g sapsys -G super_archive,super_,root,informix,bargroup -s \

/usr/bin/csh -d /export/home/<sapsid>adm -u 2001 <sapsid>adm
# useradd -g sapsys -G super_archive,super_,root,informix -s /usr/bin/csh -d \

/export/home/sapr3 -u 2002 sapr3
# useradd -g informix -G super_archive,super_,root,sapsys -s /usr/bin/csh -d \

/export/home/informix -u 2004 informix

    Create passwords for the users. 


    # passwd sapr3
# passwd informix
# passwd <sapsid>adm

This completes preparation of the cluster environment for SAP and Informix. Now proceed to "How to Install SAP and the Database (SAP With Informix)".

How to Install SAP and the Database (SAP With Informix)

  1. Verify that you have completed all tasks described in "How to Prepare the Cluster Environment for SAP and the Database (SAP With Informix)".

  2. Verify that all nodes are running in the cluster.

  3. Switch over all logical hosts to the node from which you will install SAP and the database. 


    # scadmin switch clustername phys-hahost1 CIlogicalhost DBlogicalhost ...

  4. Create the SAP installation directory and install SAP, the database, other components such as application servers, and the SAP front-end GUI.

    Use your SAP documentation to perform the installation and refer to the "R/3 Installation on UNIX" guidelines in the SAP documentation for details.

This completes the installation of SAP and Informix. Next, proceed to "How to Enable SAP and the Database to Run in the Cluster Environment (SAP With Informix)".

How to Enable SAP and the Database to Run in the Cluster Environment (SAP With Informix)

  1. Shut down the SAP central instance and database.


    # su - <sapsid>adm
$ stopsap

  2. As root, copy the Informix files from the shared disk to all nodes.

    1. On the node on which you installed SAP and Informix, create or edit the /.rhosts file to permit access from all nodes.

    2. Change directories to the Informix directory on the shared disk. 


      # cd /informix/<SAPSID>

    3. Use tar(1M) to package the Informix directories and copy them to the local Informix directory on the node on which you installed SAP and Informix (in this example, phys-hahost1).

      The directories and files present in the directory depend on the version of SAP. Include all files and directories except the data directories (sapdata and sapreorg). For example: 


      # tar cf -  aaodir bin console.phys-hahost1.<SAPSID>.log dbssodir \
forms gls incl help installconn installserver ism IVODBC.LIC lib locale \
messages release snmp | ( cd /var/opt/informix ; tar xf -)

  3. On all nodes, modify the Informix configuration files.

    Log in as user informix to perform the following tasks.

    Note -

    Make backup copies of all files before performing the following steps.

    1. Rename the sqlhosts.tli file to sqlhosts, for Informix use. 


      # mv /var/opt/informix/etc/sqlhosts.tli /var/opt/informix/etc/sqlhosts

    2. In the sqlhosts file, replace all occurrences of the physical host name with the database instance logical host name.

      For example: 


      CIlogicalhost<sapsid>shm onipcshm DBlogicalhost sapinf<SAPSID>
CIlogicalhost<sapsid>tcp ontlitcp DBlogicalhost sapinf<SAPSID>

    3. Modify the /export/home/informix/.rhosts file to allow user informix to access the database from all nodes.

      Create entries similar to the following, with one entry for each host. 


      phys-hahost1	 informix
phys-hahost2	 informix
CIlogicalhost	 informix
DBlogicalhost	 informix

    4. Rename the Informix onconfig file to replace the physical host name with the database instance logical host name.

      Rename /var/opt/informix/etc/onconfig.physicalhost.<sapsid> to /var/opt/informix/etc/onconfig.CIlogicalhost.<sapsid>.

    5. Modify the onconfig file for Informix.

      Modify the file /var/opt/informix/onconfig.CIlogicalhost.<sapsid> to direct all Informix paths to /var/opt/informix rather than to the shared diskset, for the following parameters:

      ROOTPATH MIRRORPATH MSGPATH CONSOLE ALARMPROGRAM DRLOSTFOUND SYSALARMPROGRAM

      The resulting entry should look similar to the following: 


      # original entry
# ROOTPATH	 	 /informix/<SAPSID>/sapdata/physdev1/data1

# new entry
ROOTPATH	 	 /var/opt/informix/sapdata/physdev1/data1

      Additionally, replace the physical host name with the logical host name in the database server fields. For example: 


      DBSERVERNAME    CIlogicalhost<sapsid>tcp
DBSERVERALIASES CIlogicalhost<sapsid>shm

    6. Create the /var/opt/informix/inftab file.

      The file format is $ONCONFIG:$INFORMIXDIR. For example: 


      onconfig.CIlogicalhost.<sapsid>:/var/opt/informix

  4. Copy the Informix directories to the local Informix directory on all nodes other than the node on which SAP and Informix is installed (in this example, phys-hahost1). 


    # rsh phys-hahost1 tar cfB - /var/opt/informix | tar xfB -

  5. On all nodes, set up the administrative environment for the SAP database user (user informix).

    1. On all nodes, rename the .dbenv_physicalhost.csh file to .dbenv.csh.


      $ mv .dbenv_physicalhost.csh .dbenv.csh

    2. On all nodes, edit the .dbenv.csh files as follows.

      Modify the file so that $INFORMIXDIR points to /var/opt/informix and change the ONCONFIG value to onconfig.CIlogicalhost.<sapsid>.

      Also, modify the file to specify use of TCP for $INFORMIXSERVER and ping(1M) to check the status of the database logical host. This is necessary to enable dynamic reset of the $INFORMIXSERVER parameter in case of switchover or failover.

      Note -

      In asymmetric configurations, the use of TCP and loopback might reduce performance. If so, you can set $INFORMIXSERVER to use shared memory instead.

      The resulting file should look similar to the following sample, in which the modified fields are in bold type: 


      ...
setenv INFORMIXDIR /var/opt/informix
setenv ONCONFIG onconfig.CIlogicalhost.<sapsid>
...
	case Sun*:
        setenv INFORMIXSHMBASE 0x01000000
        setenv LC_CTYPE iso_8859_1
        setenv INFORMIXSQLHOSTS $INFORMIXDIR/etc/sqlhosts
# use TCP for connection prototype always because connection
# cannot be reset dynamically between shared memory and TCP in 
# the Sun Cluster environment.
        setenv INFORMIXSERVER `grep 'CIlogicalhost<sapsid>.*ontlitcp' $INFORMIXSQLHOSTS | awk '{print $1}'`

        /usr/sbin/ping DBlogicalhost >& /dev/null
        if ( $status != 0 ) then
                           echo dbserver DBlogicalhost is not alive.
        endif

    3. On all nodes, rename the .sapenv_physicalhost.csh file to .sapenv.csh, and edit it to replace occurrences of the physical host name with the logical host name.

      First rename the file. 


      $ mv .sapenv_physicalhost.csh .sapenv.csh

      Then edit the startsap and stopsap aliases in the .sapenv.csh file to specify the central instance logical host in the set hostname= field.


      ...
set hostname='CIlogicalhost'
...

  6. Modify the SAP configuration files.

    Perform the tasks in these substeps on all nodes except the application server. Log in as user <sapsid>adm to perform the following tasks.

    1. Rename and revise the SAP instance startsap and stopsap shell scripts in the <sapsid>adm home directory.

      On the server on which the SAP central instance is installed, the <sapsid>adm home directory contains shell scripts that include physical host names. Rename these shell scripts by replacing the physical host names with logical host names. In this example, CIlogicalhost represents the logical host name of the central instance:


      $ mv startsap_physicalhost_00 startsap_CIlogicalhost_00
$ mv stopsap_physicalhost_00 stopsap_CIlogicalhost_00

      The startsap_CIlogicalhost_00 and stopsap_CIlogicalhost_00 shell scripts specify physical host names in their START_PROFILE parameters. Replace the physical host name with the central instance logical host name in the START_PROFILE parameters in both files.


      ...
START_PROFILE="START_DVEBMGS00_CIlogicalhost"
...

    2. Revise the SAP central instance profile files.

      Replace all occurrences of physical host names with logical host names, in the three profile files created by SAP during installation. You must be user <sapsid>adm, and you must be in the profile directory.

      Rename the START_DVEBMGS00_physicalhost and <SAPSID>_DVEBMGS00_physicalhost profile files.


      $ cd /sapmnt/<SAPSID>/profile
$ mv START_DVEBMGS00_physicalhost START_DVEBMGS00_CIlogicalhost
$ mv <SAPSID>_DVEBMGS00_physicalhost <SID>_DVEBMGS00_CIlogicalhost

      In the START_DVEBMGS00_CIlogicalhost profile file, replace occurrences of the physical host name with the central instance logical host name for all pf= arguments.


      Execute_00 =local $(DIR_EXECUTABLE)/sapmscsa -n \
pf=$(DIR_PROFILE)/<SAPSID>_DVEBMGS00_CIlogicalhost
Start_Program_01   =local $(_MS) pf=$(DIR_PROFILE)/<SAPSID>_DVEBMGS00_CIlogicalhost
Start_Program_02   =local $(_DW) pf=$(DIR_PROFILE)/<SAPSID>_DVEBMGS00_CIlogicalhost
Start_Program_03   =local $(_CO) -F pf=$(DIR_PROFILE)/
<SAPSID>_DVEBMGS00_CIlogicalhost
Start_Program_04   =local $(_SE) -F pf=$(DIR_PROFILE)/
<SAPSID>_DVEBMGS00_CIlogicalhost
...

      Edit the <SAPSID>_DVEBMGS00_CIlogicalhost file to add a new entry for the SAPLOCALHOST parameter.

      Add this entry only for the central instance profile. Set the SAPLOCALHOST parameter to be the central instance logical host name. This parameter allows external application servers to locate the central instance by using the logical host name.


      ...
SAPLOCALHOST		 	 	 	 	 	 		=CIlogicalhost
...

    3. Edit the DEFAULT.PFL file to replace occurrences of the physical host name with the logical host name.

      For each of the rdisp parameters, replace the physical host name with the central instance logical host name. For the SAPDBHOST parameter, enter the logical host name of the database. If the central instance and database are installed on the same logical host, enter the central instance logical host name. If the database is installed on a different logical host, use the database logical host name instead. In this example, CIlogicalhost represents the logical host name of the central instance, and DBlogicalhost represents the logical host name of the database: 


      $ vi /sapmnt/<SAPSID>/profile/DEFAULT.PFL
...
SAPDBHOST	 	 	 	 	 	 	 		=DBlogicalhost
rdisp/mshost	 	 	 	 	 	 	 	 	=CIlogicalhost
rdisp/sna_gateway	 	 	 	 		 =CIlogicalhost
rdisp/vbname	 	 	 	 	 	 	 	 	=CIlogicalhost_<SAPSID>_00
rdisp/enqname	 	 	 	 	 	 	 	 	=CIlogicalhost_<SAPSID>_00
rdisp/btcname	 	 	 	 	 	 	 	 	=CIlogicalhost_<SAPSID>_00
...

    4. Rename the .dbenv_physicalhost.csh file to .dbenv.csh.


      $ mv .dbenv_physicalhost.csh .dbenv.csh

    5. Rename the .sapenv_physicalhost.csh file to .sapenv.csh.


      $ mv .sapenv_physicalhost.csh .sapenv.csh

    6. Edit the startsap and stopsap aliases in the .sapenv.csh file to specify the central instance logical host in the `set hostname=' field.


      ...
set hostname='CIlogicalhost'
...

    7. Modify the .dbenv.csh file to specify use of TCP for $INFORMIXSERVER and to use ping(1M) to check the status of the database logical host.

      This is necessary to enable dynamic reset of the $INFORMIXSERVER parameter in case of switchover or failover.

      Note -

      In asymmetric configurations, the use of TCP and loopback might reduce performance. If so, you can set $INFORMIXSERVER to use shared memory instead.

      Modify the file to point $INFORMIXDIR to the shared disk, and to modify $INFORMIXSERVER to use TCP and ping(1M). The resulting file should look similar to the following sample, in which the modified fields are in bold type: 


      ...
setenv INFORMIXDIR /var/opt/informix
setenv ONCONFIG onconfig.CIlogicalhost.<sapsid>
...
	case Sun*:
        setenv INFORMIXSHMBASE 0x01000000
        setenv LC_CTYPE iso_8859_1
        setenv INFORMIXSQLHOSTS $INFORMIXDIR/etc/sqlhosts
# use TCP for connection prototype always because connection
# cannot be reset dynamically between shared memory and TCP in 

# the Sun Cluster environment.
        setenv INFORMIXSERVER `grep 'CIlogicalhost<sapsid>.*ontlitcp' $INFORMIXSQLHOSTS | awk '{print $1}'`

        /usr/sbin/ping DBlogicalhost >& /dev/null
        if ( $status != 0 ) then
                           echo dbserver DBlogicalhost is not alive.
        endif

    8. Modify the /export/home/<sapsid>adm/.rhosts file to allow user <sapsid>adm to access the database from all nodes.

      Create entries similar to the following, with one entry for each physical and logical host in the cluster.


      phys-hahost1	 	 	 <sapsid>adm
phys-hahost2	 	 	 <sapsid>adm
CIlogicalhost	 	 	 	 	 	<sapsid>adm
DBlogicalhost		 	 	 	 	<sapsid>adm

  7. Create the /usr/sap/tmp directory on all nodes.

    The saposcol program will rely on this directory.

  8. Copy the SAP-specific /etc/services entries from the node on which SAP and Informix are installed to the /etc/services files on all other nodes.

    Copy these entries from the /etc/services files: 


    sapms<SID>	 		 	 	 	 3601/tcp
sapdp00         3200/tcp
sapdp00s        4700/tcp
sapgw00         3300/tcp
sapgw00s        4800/tcp

  9. Test the SAP installation.

    Test the SAP installation by manually shutting down SAP, manually switching the logical host between the potential master nodes, and then manually starting SAP on the backup node. This will verify that all kernel parameters, service port entries, file systems and mount points, and user/group permissions are properly set on all potential masters of the logical hosts.

    1. As user <sapsid>adm, start the central instance and database.


      # startsap

    2. Run the GUI and verify that SAP comes up correctly.


      # su - <sapsid>adm
$ setenv DISPLAY workstation:0
$ sapwin phys-hahost1 instancenumber

    3. Verify that SAP can connect to the database.


      # su - <sapsid>adm
$ R3trans -d

    4. Run the saplicense utility to get a CUSTOMER KEY for the current node.

      You need a SAP license for all potential masters of the central instance logical host.

    5. Stop SAP and the database.


      # su - <sapsid>adm
$ stopsap

    6. On all nodes (except the application servers), set up links for the Informix library files.

      You must be root to perform these commands. 


      # unlink iosm07a.so
# unlink ipldd07a.so
# unlink ismdd07b.so
# ln -s /var/opt/informix/lib/iosm07a.so /usr/lib/iosm07a
# ln -s /var/opt/informix/lib/ipldd07a.so /usr/lib/ipldd07a.so
# ln -s /var/opt/informix/lib/ismdd07b.so /usr/lib/ismdd07b.so

  10. For each remaining node that is a potential master of the central instance logical host, switch the central instance logical host to that node and repeat the test sequence described in Step 9. 


    # scadmin switch clustername phys-hahost2 CIlogicalhost

Next, proceed to "How to Configure Sun Cluster HA for Informix".

How to Configure Sun Cluster HA for Informix

  1. On all nodes, bring up the Informix database and make sure it's running.


    # oninit
...
# dbaccess

  2. From only one node, as root, register Sun Cluster HA for Informix.


    # hareg -s -r informix [-h DBlogicalhost]

  3. From only one node, activate Sun Cluster HA for Informix. 


    # hareg -y informix

  4. From only one node, bring Informix under the control of Sun Cluster HA for Informix.

    See the hainformix(1M) man page for details. 


    # hainformix insert onconfig.CIlogicalhost.<sapsid> DBlogicalhost \

60 10 120 300 sysmaster CIlogicalhost<sapsid>tcp

  5. From only one node, bring Sun Cluster HA for Informix into service. 


    # hainformix start onconfig.CIlogicalhost.<sapsid>

  6. Verify that the database is working properly under the control of Sun Cluster HA for Informix.

    Perform a switchover of the database and make sure the oninit processes are stopped on the old master and restarted on the new master. The database should be accessible from all potential masters.

Next, proceed to "How to Configure Sun Cluster HA for SAP (SAP With Informix)".

How to Configure Sun Cluster HA for SAP (SAP With Informix)

  1. Register the Sun Cluster HA for SAP data service by running the hareg(1M) command.

    If you configure one logical host for the central instance and one for the database instance, you must register and unregister data services in the following order to preserve the order in which Informix and SAP are started and stopped:

    hareg -n informix (do this if you had informix registered before sap)

    hareg -u informix (do this if you had informix registered before sap)

    hareg -s -r sap -h CIlogicalhost

    hareg -s -r informix -h DBlogicalhost

    Activate the data service and bring it under the control of Sun Cluster using the procedures "How to Enable SAP and the Database to Run in the Cluster Environment (SAP With Informix)" and "How to Configure Sun Cluster HA for Informix".

    Run the command on only one node. For example:


    # hareg -s -r sap -h CIlogicalhost

  2. Verify that all nodes are running in the cluster.

  3. Create a new Sun Cluster HA for SAP instance using the hadsconfig(1M) command.

    The hadsconfig(1M) command is used to create, edit, and delete instances of the Sun Cluster HA for SAP data service. The configuration parameters are described in "Configuration Parameters for Sun Cluster HA for SAP (SAP With Informix)".

    Run this command on only one node, while all nodes are running in the cluster:


    # hadsconfig

  4. Stop the central instance before starting SAP under the control of Sun Cluster HA for SAP.


    # su - <sapsid>adm
$ stopsap r3

    Caution - Caution -

    The SAP central instance must be stopped before Sun Cluster HA for SAP is turned on.

  5. Turn on the Sun Cluster HA for SAP instance.


    # hareg -y sap

  6. Test switchover of Sun Cluster HA for SAP.

    For example:


    # scadmin switch clustername phys-hahost2 CIlogicalhost

  7. (Optional) If you have application servers or a test/development system, customize and test the hasap_start_all_instances and hasap_stop_all_instances scripts.

    See "Configuration Options for Application Servers and Test/Development Systems" for details. Test switchover of Sun Cluster HA for SAP, and verify start and stop of application servers. Verify that the test/development system stops when the central instance logical host is switched to the test/development system physical host.


    # scadmin switch clustername phys-hahost1 CIlogicalhost

Next, proceed to "Setting Data Service Dependencies for SAP (SAP With Oracle)", if you want to specify the start and stop order of data services within a logical host.

Configuration Parameters for Sun Cluster HA for SAP (SAP With Informix)

This section describes the information you supply to hadsconfig(1M) to create configuration files for the Sun Cluster HA for SAP data service. The hadsconfig(1M) command uses templates to create these configuration files. The templates contain some default, some hard coded, and some unspecified parameters. You must provide values for all parameters that are unspecified.

The fault probe parameters, in particular, can affect the performance of Sun Cluster HA for SAP. Tuning the probe interval value too low (increasing the frequency of fault probes) might encumber system performance, and also might result in false takeovers or attempted restarts when the system is simply slow.

Configure Sun Cluster HA for SAP by supplying the hadsconfig(1M) command with parameters listed in the following table.

Table 1-15 Sun Cluster HA for SAP Configuration Parameters (SAP With Informix)

Name of the Instance 

Nametag used internally as an identifier for the instance. The log messages generated by Sun Cluster refer to this nametag. The hadsconfig(1M) command prefixes the package name to the value you supply here. You can use the <SAPSID> for this nametag. For example, if you specify HA1, hadsconfig(1M) produces SUNWscsap_HA1.

Logical Host 

Name of the logical host that provides service for this instance of Sun Cluster HA for SAP. This name should be the logical host name for the central instance. 

Time Between Probes 

The interval, in seconds, of the fault probing cycle. The default value is 60 seconds. 

SAP SID 

This is the SAP system name or <SAPSID>.

Central Instance ID 

This is the SAP system number or central instance ID. The default value is 00.

SAP Admin Login Name 

The name used by Sun Cluster HA for SAP to log in to the SAP central instance administrative account. This name must exist on all central instance and application server hosts. This is the <sapsid>adm. For example, ha1adm.

Database Admin Login Name 

This is the SAP database administrator's account. For SAP with Informix, this is informix.

Database Logical Host Name 

Name of the logical host for the database used by SAP. This might be the same as the logical host name used for the central instance, depending on your configuration. 

Log Database Warnings 

Possible values are y or n. If set to y and the Sun Cluster HA for SAP probe detects that it cannot connect to the database during a probe cycle, a warning message appears saying the database is unavailable. For example, this occurs if the database logical host is in maintenance mode or if the database is being relocated to another node in the cluster. If the parameter is set to n, then no messages appear if the probe cannot connect to the database.

Central Instance Start Retry Count 

This must be an integer greater than or equal to 1. The default value is 10. This is the number of times Sun Cluster HA for SAP should attempt to start the central instance before giving up. This value is also the number of times the Sun Cluster HA for SAP fault monitor will probe in grace mode before entering normal probe mode. While in grace mode, the probe will not perform a restart or initiate a failover of the central instance if the probe detects that the central instance is not yet up. Instead, the fault monitor will report the status of all probes and will continue in grace mode until all probes pass, or until the retry count has been exhausted. 

Central Instance Start Retry Interval 

This is the number of seconds Sun Cluster HA for SAP should wait between each attempt to start the central instance. This value is also the number of seconds that the Sun Cluster HA for SAP fault monitor will sleep (between probe attempts) while in grace mode. The default value is 30.  

Time Allowed to Stop All Instances Before Central Instance Starts 

This must be an integer greater than or equal to 0. The default value is 60. This parameter dictates for how much time (in seconds) the hasap_stop_all_instances script should be run before starting the central instance. If set to 0, then hasap_stop_all_instances is run in the background while the central instance is being started. If set to a positive integer, then hasap_stop_all_instances is run for that amount of time in the foreground before the central instance is started.

Allow the Central Instance to Start if Foregrounded Stop All Instances Returns  

Error 

This flag should be set to either y or n. The default value is n. This value determines whether the central instance should be started in the case where the hasap_stop_all_instances script returns a non-zero exit code or does not complete in the time specified by the "Time Allowed to Stop All Instances Before Central Instance Starts" parameter. If set to n and the value for "Time Allowed to Stop All Instances Before Central Instance Starts" is greater than 0, and if the hasap_stop_all_instances script does not complete in the time configured above or the hasap_stop_all_instances script returns a non-zero exit status, the central instance will not be started and the fault monitors will take action based on the other configuration parameters. If set to y, then the central instance will be started regardless of whether hasap_stop_all_instances returns an error code or finishes within the timeout specified above.

Number of Central Instance Restarts on Local Node 

This must be an integer greater than or equal to 0. The default value is 1. This dictates how many times the SAP central instance will be restarted on the local node before giving up, after a failure has been detected. When this number of restarts has been exhausted, Sun Cluster HA for SAP either issues a failover request, if permitted by the "Allow Central Instance Failover" parameter, or does nothing to correct the failure detected by the fault monitor. 

Number of Probe Successes to Reset the Restart Count 

This parameter should be an integer that is greater than or equal to 0. The default value is 60. If set to a positive integer, then after that many consecutive successful probes, the count of restarts done so far on the local node will be reset to 0. For example, if the value for "Number of Central Instance Restarts on Local Node" parameter is 1 and the value for "Number of Probe Successes to Reset the Restart Count" is 60, then after the first failure occurs, the probe will try to restart the central instance on the local node. If this restart succeeds, then after 60 successful probes, the restart count will be reset to 0, allowing the probe to do another restart if it detects another failure. If the parameter "Number of Probe Successes to Reset the Restart Count" is set to 0, then the restart count is never reset. This means that the number of restarts set in the parameter "Number of Central Instance Restarts on Local Node" is the absolute number of restarts that will be done on the local node before failing over. 

Allow Central Instance Failover 

Possible values are y or n. The default value is y. If set to y and Sun Cluster HA for SAP detects an error in the SAP instance it is monitoring and the "Number of Central Instance Restarts on Local Node" has been exhausted, then Sun Cluster HA for SAP issues a request to relocate the instance's logical host to another cluster node. If this flag is set to n, then even if an error is detected and all of the local restarts have been exhausted, Sun Cluster HA for SAP will not cause a relocation of this instance's logical host. When this occurs, the central instance is left in the failed state, and the probe exits.

Setting Data Service Dependencies for SAP (SAP With Informix)

Setting a dependency with hasap_dbms is only necessary to specify the order that data services are started and stopped within a single logical host. There is no mechanism for setting dependencies for data services configured on two different logical hosts.

If Sun Cluster HA for Informix or Sun Cluster HA for NFS are configured on the same logical host as Sun Cluster HA for SAP, then you should set a dependency for Sun Cluster HA for SAP on those data services. You can use the hasap_dbms command to create or remove such a dependency. These dependencies affect the order that the services are started and stopped. Sun Cluster HA for Informix and Sun Cluster HA for NFS should always be started before Sun Cluster HA for SAP is started. Similarly, Sun Cluster HA for SAP should always be stopped before the other data services are stopped.

Caution - Caution -

If Sun Cluster HA for Informix or Sun Cluster HA for NFS is not configured on the same logical host as Sun Cluster HA for SAP, then do not use the hasap_dbms command.

How to Set a Data Service Dependency for SAP (SAP With Informix)

To set a data service dependency, issue one of the hasap_dbms commands described below.

Note -

The hasap_dbms command can be used only when Sun Cluster HA for SAP is registered but is in the off state. Run the command on only one node, while that node is a member of the cluster. See the hasap_dbms(1M) man page for more information.

Caution - Caution -

If the hasap_dbms(1M) command returns an error stating that it cannot add rows to or update the CCD, it might be because another cluster utility is also trying to update the CCD. If this occurs, re-run hasap_dbms(1M) until it runs successfully. After the hasap_dbms(1M) command runs successfully, verify that all necessary rows are included in the resulting CCD by running the command hareg -q sap. If the hareg(1M) command returns an error, then first restore the original method timeouts by running the command hasap_dbms -f. Second, restore the default dependencies by running the command hasap_dbms -r. After both commands complete successfully, retry the original hasap_dbms(1M) command to configure new dependencies and method timeouts. See the hasap_dbms(1M) man page for more information.

  1. Set the data service dependency using one of the following commands.

    If you are using only Sun Cluster HA for NFS and Sun Cluster HA for SAP on the same logical host, use the following command: 


    # /opt/SUNWcluster/ha/sap/hasap_dbms -d nfs

    If you are using only Sun Cluster HA for Informix and Sun Cluster HA for SAP on the same logical host, use the following command:


    # /opt/SUNWcluster/ha/sap/hasap_dbms -d informix

    If you are using Sun Cluster HA for Informix, Sun Cluster HA for NFS, and Sun Cluster HA for SAP on the same logical host, use the following command:


    # /opt/SUNWcluster/ha/sap/hasap_dbms -d informix,nfs

  2. Check the dependencies set for Sun Cluster HA for SAP using the following command:


    # hareg -q sap -D

How to Remove a Data Service Dependency for SAP (SAP With Informix)

The dependencies set for Sun Cluster HA for SAP can be removed by running the hasap_dbms -r command. Issuing this command causes all of the dependencies set for Sun Cluster HA for SAP to be removed.

Note -

The hasap_dbms command can be used only when Sun Cluster HA for SAP is registered but is in the off state. Run the command on only one node, while that node is a member of the cluster. See the hasap_dbms(1M) man page for more information.

Caution - Caution -

If the hasap_dbms(1M) command returns an error stating that it cannot add rows to or update the CCD, it might be because another cluster utility is also trying to update the CCD. If this occurs, re-run hasap_dbms(1M) until it runs successfully. After the hasap_dbms(1M) command runs successfully, verify that all necessary rows are included in the resulting CCD by running the command hareg -q sap. If the hareg(1M) command returns an error, then first restore the original method timeouts by running the command hasap_dbms -f. Second, restore the default dependencies by running the command hasap_dbms -r. After both commands complete successfully, retry the original hasap_dbms(1M) command to configure new dependencies and method timeouts. See the hasap_dbms(1M) man page for more information.

  1. Remove all of the dependencies set for Sun Cluster HA for SAP, using the following command:


    # /opt/SUNWcluster/ha/sap/hasap_dbms -r

  2. Check the dependencies set for Sun Cluster HA for SAP, using the following command:


    # hareg -q sap -D