Cluster Manager Setup
The cluster manager software is how the Oracle instances communicate their activities. Obviously this is an important piece to the puzzle as well. Here I review the configs, and then show how to get it up and running on each node. I *DID NOT* patch the cluster manager with the 184.108.40.206 db patch, but your mileage may vary.
Edit file $ORACLE_HOME/oracm/admin/cmcfg.ora
ClusterName=Oracle Cluster Manager, version 9i
Note, if you patch oracm to 220.127.116.11, remove the two Watchdog lines, and uncomment and use the CmDiskFile.
Edit file $ORACLE_HOME/oracm/admin/ocmargs.ora
watchdogd -d /dev/null -l 0
Note, if you patch oracm to 18.104.22.168, comment out the watchdog line.
Now *AS ROOT* start up the cluster manager:
You should see 8 processes with “ps -auxw | grep oracm”. Note that if you are running RH8, there’s a new ps which needs a special option “m” to notice threads. Apparently oracm is threaded (Thanks Wim). This had me pulling my hair out for weeks, and I’m bald! Anyway if that is the case, use “ps auxwm | grep oracm”. One more little recommendation. oracm is communicating via a port which you define. If you’re using iptables/ipchains, or some other firewall solution, I would recommend disabling it, at least temporarily, until you know you’ve configured everything right. Then reenable it, being sure you are good at configuring just the ports you need.
15. Perform step 14 on node 2.