For a two-node cascading HACMP cluster running highly available NetView, TMR
server and RIM host on one node and a highly available Oracle dbms on the other
node, here are the filesystems I used on shared external disks that were
twin-tailed to each node:
node 1= netview host, TMR server, RIM host
nvservervg
lvnetivew
/usr/OV
lvoptivity
/opt
lvtivoli
/tivoli
lvdynatext
/usr/ebt
lvdatabases
/usr/OV/databases
lvoraclient
/oracle/client (this is for oracle's sqlnet client when the
oracle server node is different from the netview server node.)
node2 = oracle dbms server
nvdbasevg
lvorahome
/oracle/product/7.3.4
lvoradmin
/oracle/admin
lvoradata1
/oracle/oradata1
lvoradatau01
/u01/oradata
lvoradatau02
/u02/oradata
lvoradatau03
/u03/oradata
Recall that for the oracle server and client to work correctly in a 2-node
cascading cluster, that the sqlnet client must be running on the NetView server
node but after failover to the oracle server node that sqlnet is not used so
that the database talks directly to the application. The
oracle "two-task" variable must be set correctly for this to occur.
NetView resolves the hostname to the ipadapter label so that after failover,
reset the hostname in the netview startup script. This hostname should be the
same as the ipadapter label for the HACMP service ipaddress for this
highly-available application. Do NOT use reset_ci. In addition, for Tivoli to
work correctly, use the same hostname but set it in the wlocaltemp file on both
nodes. Oracle doesn't care where it is running vis-a-vis hostnames, unames or
ipadapter labels so long as the oracle environmental variables are set
correctly for the tnslistener.
Regards,
ken
ken.garst@kp.org
(P.S.: If you are running NetView clients via nfsmounts for maps to the HACMP
cluster node for NetView, certain special things have to be done for the
failover to occur correctly such as defining a pre-event to NODE DOWN where
NetView. The pre-event issues a nvstopall forceall on the NetView client node
that correctly stops all client sessions so the nfs files can be unmounted. In
addition, there is a modification to the nfs unmount script in HACMP that must
be made for this to work, which is documented in the HACMP installation manual.)
|