2011. 5. 3. 10:22 오라클
node stop시 vip 가 fail-over되지 않을때.
Metalink (문서 ID 749160.1)
node1을 stop 했는데 VIP가 넘어가지 않을때, 10.2.0.5 로 patch or 11g 사용권장
========================================================================================
Running a 2 node rac with 10.2.0.3. When nodeapps are stopped from one node, the vip-interface
does not failover to existing nodes. Therefore all users can not connect to the database.
When issuing command :
node1을 stop 했는데 VIP가 넘어가지 않을때, 10.2.0.5 로 patch or 11g 사용권장
========================================================================================
Running a 2 node rac with 10.2.0.3. When nodeapps are stopped from one node, the vip-interface
does not failover to existing nodes. Therefore all users can not connect to the database.
When issuing command :
srvctl stop nodeapps -n node1then VIP-interface of node node1 does not get migrated to node node2.
As you entered the stop command manually this is interpreted by crs not as a failure but as a wish
from your side and so no failover takes place.
The behavior has changed in 11g and will in 10.2.0.5 due to enhancement request 4623630.
In 11g and 10.2.0.5 you will use the following syntax:
srvctl stop nodeapps -n node1 -r
The -r switch tells the system to relocate the VIP to an available node.
In case this functionality is important, the best is to upgrade to 11g or 10.2.0.5 as it becomes available.
