Skip Navigation Links | |
Exit Print View | |
Oracle Solaris Cluster Data Service for SAP liveCache Guide Oracle Solaris Cluster 4.1 |
1. Installing and Configuring HA for SAP liveCache
Installing and Configuring HA for SAP liveCache
Planning the HA for SAP liveCache Installation and Configuration
Standard Data Service Configurations
Configuration Planning Questions
Verifying the liveCache Installation and Configuration
How to Verify the liveCache Installation and Configuration
Installing the HA for SAP liveCache Package
How to Install the HA for SAP liveCache Package
Registering and Configuring the HA for SAP liveCache
Setting HA for SAP liveCache Extension Properties
How to Register and Configure HA for SAP liveCache
Verifying the HA for SAP liveCache Installation and Configuration
How to Verify the HA for SAP liveCache Installation and Configuration
Tuning HA for SAP liveCache Fault Monitors
Factors That Affect the Interval Between Fault Monitor Probes
Operations by the HA for SAP liveCache Fault Monitors During a Probe
Operations by the SAP liveCache Fault Monitor During a Probe
Operations by the SAP xserver Fault Monitor During a Probe
Faults Detected by the HA for SAP liveCache Fault Monitors
Faults Detected by the SAP liveCache Fault Monitor
Faults Detected by the SAP xserver Fault Monitor
Recovery Actions in Response to Detected Faults
Monitoring the Termination of liveCache by a User
This section contains the procedures that you need to install and configure liveCache.
Use this procedure to install and configure liveCache.
See Oracle Solaris Cluster Data Service for SAP Guide for the procedures on how to install and configure SAP APO System on Oracle Solaris Cluster software.
Note - Install liveCache by using the physical hostname if you have not already created the required logical host.
For more information, see your SAP documentation.
The format of the liveCache administrator user's user ID is lc-nameadm.
If you are creating the liveCache administrator user manually, add the following entry to the /etc/group file:
sdba::group-id:lc-nameadm
The group's unique numerical ID (GID) within the system
Lowercase name of liveCache database instance
For more information about the /etc/group file, see the group(4) man page.
Note - This user whose home directory contains the .XUSER.62 file is an internal database user who has permissions to start, stop, and query the database.
$ dbmcli -d LC-NAME -n logical-hostname-ususername,passwd
Uppercase name of liveCache database instance
Logical hostname that is used with the liveCache resource
Caution - Neither SAP APO transaction LC10 nor HA for SAP liveCache functions properly if you do not create this file correctly. |
Ensure that the ownership of these files is the same on all nodes as it is on the node or zone on which you installed liveCache.
Example:
# tar cfB /tmp/usr-spool.tar /usr/spool/sql Log in to the destination zone. # scp root@soruce:/tmp/usr-spool.tar /tmp # cd / # tar xfb /tmp/usr-spool.tar
Specifies the node or zone where you installed SAP liveCache
Ensure that the ownership of these files is the same on all nodes as it is on the node or zone on which you installed liveCache.
# tar cfB /tmp/opt-sdb.tar /etc/opt/sdb Log in to the target zone. # scp root@source:/tmp/opt-sdb.tar /tmp # cd / # tar xfb /tmp/opt-sdb.tar
Specifies the node or zone where you installed SAP liveCache.
# ln -s /sapdb/data/wrk /sapdb/LCA/db/wrk
The required files include /etc/group, /etc/passwd, /etc/project, and /etc/user_attr.
During a standard SAP installation, liveCache is installed with a physical hostname. You must modify liveCache to use a logical hostname so that liveCache works in a Oracle Solaris Cluster environment. Use this procedure to enable liveCache to run in a cluster.
Before You Begin
Ensure that the /etc/netmasks file has IP-address subnet and netmask entries for all logical hostnames. If necessary, edit the /etc/netmasks file to add any missing entries.
# clresourcegroup create [-n node-zone-list] livecache-resource-group
# clreslogicalhostname create -g livecache-resource-group \ -h lc-logical-hostname lc-logical-hostname
Note - If you require a fully qualified hostname, you must specify the fully qualified name with the -h option and you cannot use the fully qualified form in the resource name.
# clresourcegroup online -M livecache-resource-group
# clresource enable lc-logical-hostname
# su - lc-nameadm $ x_server start
Lowercase name of liveCache database instance
liveCache host: lc-logical-hostname