Database Reference
In-Depth Information
/u01/app/11.2.0/grid/crs/template/appvip.type
2012-10-28 03:30:37: Create the Resource
2012-10-28 03:30:37: Executing /u01/app/11.2.0/grid/bin/crsctl add resource
omsvip -type app.appvip_net1.type -attr
"USR_ORA_VIP=192.168.1.0,START_DEPENDENCIES=hard(ora.net1.network)
pullup(ora.net1.network),STOP_DEPENDENCIES=hard(ora.net1.network),
ACL='owner:root:rwx,pgrp:root:r-x,other::r--,user:root:r-x',
HOSTING_MEMBERS=oms1.example.com,APPSVIP_FAILBACK="
2012-10-28 03:30:37: Executing cmd: /u01/app/11.2.0/grid/bin/crsctl add
resource omsvip -type app.appvip_net1.type -attr
"USR_ORA_VIP=192.168.1.0,START_DEPENDENCIES=hard(ora.net1.network)
pullup(ora.net1.network),STOP_DEPENDENCIES=hard(ora.net1.network),
ACL='owner:root:rwx,pgrp:root:r-x,other::r--,user:root:r-x',
HOSTING_MEMBERS=oms1.example.com,APPSVIP_FAILBACK="
This creates a VIP on network 1, which is defined as IP address 192.168.1.0. The VIP name is
omsvip
and it
is owned by the
ROOT
user.
2.
Next you need to allow the Oracle Grid Infrastructure software owner (for example,
GRID
)
to run the script to start the VIP. As
ROOT
, execute the following:
GRID_HOME/bin/crsctl setperm resource omsvip -u user:grid:r-x
3.
Start the VIP as the
GRID
user.
GRID_HOME/bin/crsctl start resource omsvip
For example:
[grid@oms1 ~]$ $GRID_HOME/bin/crsctl start resource omsvip
CRS-2672: Attempting to start 'omsvip' on 'oms1'
CRS-2676: Start of 'omsvip' on 'oms1' succeeded
4.
Check the status of the VIP.
GRID_HOME/bin/crsctl status resource omsvip
The status of the output should be similar to the following:
NAME=omsvip
TYPE=app.appvip_net1.type
TARGET=ONLINE
STATE=ONLINE on oms1
5.
The virtual hostname is defined in DNS, and should resolve to the application VIP address
created using the preceding steps. Check whether the virtual hostname and VIP are
resolvable by using
nslookup
or the
dig
command.
$ nslookup omsvip
This should resolve to a unique IP address of the virtual hostname on every node in the
cluster.
