Hi,

the VIP is a very important feature and you *must not* forget about the VIP.

The only reason why we have a VIP is to avoid TCP/IP-timeouts. And this is crucial in a high availability environment. It's not acceptable for a client to wait minutes for the timeout.

If the VIP is not moving over during a node shutdown (it actually should) then contact Oracle Support and open a SR.

The main thing, which was missing for me in the context of VIPs was the feature of gracefully switching a VIP over to another node in case of e.g. planned maintenance. Therefore Bug 4623630 was opened to enhance srvctl. A new option "-r" (relocate) is added to "srvctl stop nodeapps" command that automatically relocates all active VIPs on the node to another node or stop all active VIPs when this is the last node.

If you want to stop crs and move a VIP to another node you may follow the following steps as an "unsupported" workaround.

1. srvctl stop instance -i < instance> -d < database>
for all databases that have instance configured on the < node>
2. srvctl stop asm -n < node>
3. srvctl stop nodeapps -n < node>
4. crs_start ora.< node>.vip -f
5. crs_relocate ora.< node>.vip -f
6. /etc/init.d/init.crs stop

Using "crs_"-commands is only supported for resources which do NOT start with "ora", ie it is supported only for your own applications, which you want to make high available (you always should use srvctl for resources, which start with "ora"). You therefore better ask for a backport of enhancement request 4623630.

Ciao

Clemens



--
To unsubscribe, email: suse-oracle-unsubscribe@(protected)
For additional commands, email: suse-oracle-help@(protected)
Please see http://www.suse.com/oracle/ before posting