Database Reference
In-Depth Information
6.
Also do a reverse lookup of the IP address.
$nslookup <virtual IP address>
Verify that the IP address returned from the
nslookup
output is running on the OMS host.
7.
ifconfig -a|grep <virtual IP address>
8.
After you have verified that the virtual hostname and VIP have been configured correctly,
you can then proceed with the OMS installation. The following should be performed
before starting the installer:
Create a new
ORACLE_HOME
for the OMS on the shared storage on all nodes in the
cluster:
a.
$ mkdir -p /u01/app/oms_share
Create an Oracle inventory directory under the
ORACLE_HOME
for the OMS on all
nodes:
b.
$ mkdir /u01/app/oms_share/oraInventory
Create the inventory pointer in the
oraInventory
directory:
c.
$ vi oraInst.loc
The
oraInst.loc
file should contain the path to the inventory and the group of the
software owner for the OMS. For example:
inventory_loc=/u01/app/oracle/oms_share/oraInventory
inst_group=oinstall
Next, you proceed with the installation by specifying the
ORACLE_HOSTNAME
environment
variable as your virtual hostname and pointing to the shared inventory location.
9.
runInstaller -invPtrloc /u01/app/oms_share/oraInst.loc \
ORACLE_HOSTNAME=omsvip.example.com -debug
10.
Install the OMS on the first host by following the installation steps as described in the
Oracle Enterprise Manager Cloud Control 12c Basic Installation Guide
. You need to
complete the installation only once. Because the location is shared, the binaries will be
accessible from another host that shares the filesystem.
After the OMS has been successfully installed and is up and running, if the host were to go down, then the VIP
would be automatically relocated to another node. The management service can then be manually started on any
remaining node in the cluster on which the VIP is running.
1.
To manually relocate the VIP to another host in the cluster, issue the following command:
[grid@oms1 ~]$ crsctl relocate res omsvip
CRS-2673: Attempting to stop 'omsvip' on 'oms1'
CRS-2677: Stop of 'omsvip' on 'oms1' succeeded
CRS-2672: Attempting to start 'omsvip' on 'oms2'
CRS-2676: Start of 'omsvip' on 'oms2' succeeded
