Use the following steps to start the Infrastructure in an OracleAS Cold Failover Cluster:
1. Set the ORACLE_HOME environment variable to the Infrastructure’s Oracle home.
2. Set the ORACLE_SID environment variable to the metdata repository’s system identifier.
3. Set the PATH environment variable to include the Infrastructure’s $ORACLE_
HOME/bin directory.
4. Enable volume management software and mount the file system (if necessary).
5. Enable the virtual IP address.
6. Start the metadata repository listener. $ORACLE_HOME/bin/lsnrctl start
7. Start the metadata repository.
Note: For details on installing for high availability, refer to the Oracle Application Server 10g Installation Guide.
Important: Specify the path of the working Oracle home as the first entry in the PATH environment variable if there are several Oracle homes installed on the machine. Also, ensure that the full paths of the executables you use are specified.
Oracle Application Server Cold Failover Clusters
8. Start OPMN and all OPMN-managed processes for each OracleAS instance locally. If OPMN daemon is not running, start both OPMN daemon and OPMN-managed processes:
$ORACLE_HOME/opmn/bin/opmnctl startall
If OPMN daemon is running, start all OPMN-managed processes collectively: $ORACLE_HOME/opmn/bin/opmnctl startproc
Alternatively, to individually start up OPMN-managed processes:
a. Start Oracle HTTP Server:
$ORACLE_HOME/opmn/bin/opmnctl startproc ias-component=HTTP_Server
b. Start Oracle Internet Directory:
$ORACLE_HOME/opmn/bin/opmnctl startproc ias-component=OID
c. Start the Delegated Administration Services instance:
$ORACLE_HOME/opmn/bin/opmnctl startproc ias-component=OC4J instancename=OC4J_SECURITY
d. Check the status of the OPMN-managed processes using the following command:
$ORACLE_HOME/opmn/bin/opmnctl status
9. Start the Application Server Console. Use one of the following commands: $ORACLE_HOME/bin/emctl start iasconsole
Or:
$ORACLE_HOME/bin/emctl startifdown iasconsole
Stopping
Use the following steps to stop the OracleAS Infrastructure in an OracleAS Cold Failover Cluster:
1. Set the ORACLE_HOME environment variable to the Infrastructure’s Oracle home.
2. Set the ORACLE_SID environment variable to the metdata repository’s system identifier.
3. Stop OPMN and all OPMN-managed processes for each OracleAS instance locally. To shutdown the OPMN daemon and all OPMN-managed processes:
$ORACLE_HOME/opmn/bin/opmnctl stopall
To shutdown all OPMN-managed processes but leave the OPMN daemon running:
$ORACLE_HOME/opmn/bin/opmnctl stopproc
Alternatively, to individually shutdown all OPMN-managed processes:
a. Stop the Delegated Administration Services instance:
$ORACLE_HOME/opmn/bin/opmnctl stopproc ias-component=OC4J instancename=OC4J_SECURITY
Oracle Application Server Active Failover Cluster (UNIX)
b. Stop Oracle Internet Directory:
$ORACLE_HOME/opmn/bin/opmnctl stopproc ias-component=OID
c. Stop Oracle HTTP Server.
$ORACLE_HOME/opmn/bin/opmnctl stopproc ias-component=HTTP_Server
4. Stop the metadata repository
5. Stop the metadata repository listener. $ORACLE_HOME/bin/lsnrctl stop
6. Stop the Application Server Console. $ORACLE_HOME/bin/emctl stop iasconsole
7. Disable volume management software and unmount the file system (if necessary).
8. Disable the virtual IP address.
Oracle Application Server Active Failover Cluster (UNIX)
The instructions in this section detail the steps for starting and stopping the Infrastructure in the OracleAS Active Failover Cluster high availability solution.
Starting Up
For an OracleAS Active Failover Cluster-enabled Infrastructure, each node in the cluster is functionally equivalent to the other nodes. All nodes access a common repository. The database instance and the individual OracleAS processes need to be started on each node of the cluster. At any given time, the load balancer should be configured to direct traffic to only the active nodes. The order of starting up Infrastructure instances on all nodes is:
1. On each node, start the global services daemon: $ORACLE_HOME/bin/gsd
2. Start the database instances and listeners on all nodes with the following command (can be run from any node in the cluster):
$ORACLE_HOME/bin/srvctl start -p <database_name>
The global services daemon on each node ensures that the local database processes on each node are started.
3. Start OPMN and all OPMN-managed processes.
If OPMN daemon is not running, start both OPMN daemon and OPMN-managed processes (following command need only be run once):
Note: Check OracleMetalink (http://metalink.oracle.com) for the most current certification status of this feature or consult your Oracle sales representative before deploying this feature in a production environment.
Oracle Application Server Active Failover Cluster (UNIX)
$ORACLE_HOME/opmn/bin/opmnctl
@instance:<instancename_on_node1>:<instancename_on_node2> startall
If OPMN daemon is running, you can start all OPMN-managed processes on all nodes (following command need only be run once):
$ORACLE_HOME/opmn/bin/opmnctl
@instance:<instancename_on_node1>:<instancename_on_node2> startproc For example, assuming there are two nodes in the cluster:
$ORACLE_HOME/opmn/bin/opmnctl
@instance:infra_node1:infra_node2 startproc
Alternatively, to individually start up OPMN-managed processes on all nodes (following commands need only be run once):
a. Start Oracle HTTP Server: $ORACLE_HOME/opmn/bin/opmnctl
@instance:<instancename_on_node1>:<instancename_on_node2> startproc ias-component=HTTP_Server
b. Start Oracle Internet Directory. $ORACLE_HOME/opmn/bin/opmnctl
@instance:<instancename_on_node1>:<instancename_on_node2> startproc ias-component=OID
c. Start the Delegated Administration Services instance: $ORACLE_HOME/opmn/bin/opmnctl
@instance:<instancename_on_node1>:<instancename_on_node2> startproc ias-component=OC4J instancename=OC4J_SECURITY
4. Configure the load balancer and enable traffic to the current node.
5. Check the status of OPMN-managed processes on all nodes using the following command:
$ORACLE_HOME/opmn/bin/opmnctl
@instance:<instancename_on_node1>:<instancename_on_node2> status
6. Start the Application Server Console. Run one of the following commands on each node in the cluster:
$ORACLE_HOME/bin/emctl start iasconsole Or:
$ORACLE_HOME/bin/emctl startifdown iasconsole
Note: For more efficient startup of the OracleAS Active Failover Cluster nodes, you can configure each node’s operating system to start up the OPMN daemon whenever the node starts up. The procedures for performing this task are specific to each operating system. For example, in UNIX, the rc scripts can be configured by the system administrator for this purpose.
Oracle Application Server Active Failover Cluster (UNIX)