Oracle B32100-01 User Manual
Pre-Installation Steps for OracleAS Cold Failover Cluster
8-4
Oracle Application Server Installation Guide
from a different node should provide a login to the node you configured in
this procedure:
this procedure:
telnet hostname.domain
telnet ip_address
For example, enter:
telnet vhost.mydomain.com
telnet 138.1.12.191
On Failover
If the active node fails, then the secondary node takes over. If you do not have a
clusterware agent to map the virtual IP from the failed node to the secondary node,
then you have to do it manually. You have to remove the virtual IP mapping from the
failed node, and map it to the secondary node.
clusterware agent to map the virtual IP from the failed node to the secondary node,
then you have to do it manually. You have to remove the virtual IP mapping from the
failed node, and map it to the secondary node.
1.
On the failed node, remove the virtual IP address by running the following
command as the root user:
command as the root user:
/usr/sbin/ifconfig
configured_interface down
For example, enter the following command if lan0:2 is configured with the
virtual IP address:
virtual IP address:
/usr/sbin/ifconfig
lan0:2 down
2.
On the secondary node, add the virtual IP address.
On the secondary node, follow steps 2 to 6 of the previous procedure to add and
confirm the virtual IP address on the secondary node.
confirm the virtual IP address on the secondary node.
8.2.2 Set Up a File System That Can Be Mounted from Both Nodes
Although the hardware cluster has shared storage, you need to create a file system on
this shared storage such that both nodes of the OracleAS Cold Failover Cluster can
mount this file system. You will use this file system for the following directories:
this shared storage such that both nodes of the OracleAS Cold Failover Cluster can
mount this file system. You will use this file system for the following directories:
■
Oracle home directory for the Oracle Application Server instance
■
The oraInventory directory
For disk space requirements, see
If you are running a volume manager on the cluster to manage the shared storage,
refer to the volume manager documentation for steps to create a volume. Once a
volume is created, you can create the file system on that volume.
refer to the volume manager documentation for steps to create a volume. Once a
volume is created, you can create the file system on that volume.
If you do not have a volume manager, you can create a file system on the shared disk
directly. Ensure that the hardware vendor supports this, that the file system can be
mounted from either node of the OracleAS Cold Failover Cluster, and that the file
system is repairable from either node if a node fails.
directly. Ensure that the hardware vendor supports this, that the file system can be
mounted from either node of the OracleAS Cold Failover Cluster, and that the file
system is repairable from either node if a node fails.
To check that the file system can be mounted from either node, do the following steps:
1.
Set up and mount the file system from node 1.
Note:
Use the commands in step 3 of the previous procedure to
confirm that the virtual IP address has been removed.