Installing OPS

These are the high-level steps to install OPS in a Sun Cluster configuration. If you are installing Oracle7 Parallel Server, refer to the Oracle7 for Sun SPARC Solaris 2.x Installation and Configuration Guide, Release 7.x. If you are installing Oracle8 Parallel Server, refer to the Oracle8 Parallel Server Concepts and Administration, Release 8.0 Guide. If you are installing Oracle8i Parallel Server, refer to your Oracle8i installation documentation.

1. Configure the UNIX kernel Interprocess Communication (IPC) parameters to accommodate the Shared Global Area (SGA) structure of Oracle8i. Reboot all nodes.

2. Set up the Oracle user environment on all nodes, using your Oracle documentation.

3. Use the scinstall(1M) command to install Sun Cluster 2.2. Specify OPS when prompted to select a data service, and use VxVM with the cluster feature enabled as the volume manager.

4. Reboot all nodes.

5. Install the ORCLudlm package on all nodes. This package is located at on the Oracle product CD-ROM, in the ops_patch directory.

6. On all nodes, install VERITAS Volume Manager (VxVM) with the cluster feature enabled.

7. Reboot all nodes.

8. Create the VERITAS root disk group (rootdg). See your VERITAS documentation for detailed instructions about creating the rootdg.

9. Start the cluster on one node only.

10. Create Oracle disk groups and raw volumes for the OPS database. See your VERITAS and Oracle8i installation documentation for details.

11. Stop the cluster.

12. Restart the cluster on all nodes.

13. Install Oracle with the OPS option on all nodes. See your Oracle/OPS documentation for detailed instructions about installing OPS.

14. For OPS versions 8.0.5 and earlier, configure the Oracle GMS daemon. See "Starting the Oracle GMS Daemon" for details. This step is not necessary for OPS 8.1.6 or later versions.

Configuring Oracle SQL*Net and Net8

The methods used to configure Oracle SQL*Net or Net8 for OPS are identical to the methods used for Oracle, with one exception: with OPS instances, Net8 can be configured for load balancing and failover. The configuration methods differ for different versions of Oracle and OPS; consult your Oracle documentation for detailed procedures to configure the connections between the Oracle client and Oracle server.

Starting the Oracle GMS Daemon

In Sun Cluster 2.2, Oracle's Group Membership Services (GMS) daemon is not started by scogms(1M) as part of the Sun Cluster framework installation. This means that for Oracle Parallel Server databases, the GMS daemon must be started manually using the binary ogmsctl that is provided by the Oracle Parallel Server Option installation on a cluster node. The ogmsctl daemon must be up and running even when the instance on the node is started in exclusive mode. Therefore, this daemon should be running when the database is created.

The GMS binaries ogms and ogmsctl are located in the /bin directory under $ORACLE_HOME. The default home directory for the GMS daemon is /tmp/.ogms. This directory contains trace files and the gms0000.dat file.

The GMS daemon must be started from the oracle user login. The following commands start the GMS daemon.

# su - oracle
$ ogmsctl start

For the daemon to start successfully, the node upon which it is run must be a cluster member.

The following command stops the GMS daemon.

$ ogmsctl stop

The ogmsctl command has the following options.