Database Reference
In-Depth Information
2.
Check whether the IP address associated with the VIP is running on the relocated host.
ifconfig -a|grep <vip>
The repository database should be reachable from other hosts in the cluster, and the
listener should be up and running.
Set the
ORACLE_HOSTNAME
environment variable to the virtual hostname. Continuing with
our example, we use the following command:
3.
export ORACLE_HOSTNAME=omsvip.example.com
4.
Start the OMS on the new node.
$OMS_HOME/bin/emctl start oms
Alternatively, Oracle Clusterware can be configured to fully manage the OMS by creating start, check, stop, clean,
and abort routines that tell it how to operate on the OMS. Details on this configuration are outside the scope of this
chapter. See the
Oracle Clusterware Administration and Deployment Guide 11gR2
for details.
With a cold-failover solution in place for the OMS, you are protected from the failure of a single host. However,
time to perform failover could range from a few minutes to hours, depending on whether it is done manually or
automated via Oracle Clusterware or other methods. The repository also needs to be protected, as it is now a single
point of failure. As mentioned earlier, a local Data Guard setup consisting of a single physical standby is highly
recommended. The standby database should be configured on a separate host from the management servers and
primary database. However, it may be possible to create both the primary and the physical standby on another
OMS host to keep costs down. In the event of a planned or unplanned outage of the primary repository, the physical
standby can be switched or failed over to the standby on a remaining host. Please note that the host will now become
a single point of failure.
As a prerequisite to creating a standby database using Enterprise Manager, the destination host should have an
Oracle Management Agent installed and should be monitored by Enterprise Manager. Also, if ASM is used as database
storage, it should be monitored along with the listener.
To create a standby database using Enterprise Manager, use these steps:
1.
Navigate to the repository database home page and choose Availability รค Add Standby
from the menu.
2.
Back up the primary database (see Figure
13-6
). Data Guard uses RMAN to create the
standby database based on either a new or existing backup. An online backup requires that
the database be in
ARCHIVELOG
mode.
