Vip Does Not Failover When Nodeapps Stopped (Doc ID 749160.1)

rongshiyuan發表於2014-12-18
AIAPP

Vip Does Not Failover When Nodeapps Stopped (Doc ID 749160.1)


In this Document
  Goal
  Solution
  References

Applies to:

Oracle Server - Enterprise Edition - Version: 10.2.0.1
Oracle Server - Standard Edition - Version: 10.2.0.1
Information in this document applies to any platform.
Oracle CRS 10g prior the upcoming 10.2.0.5

Goal

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. How to accomplish that the VIP will failover to node2?

Solution

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 node1

then 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.


References

 

Document Details

 
Rate this document Email link to this documentOpen document in new windowPrintable Page
Type:
Status:
Last Major Update:
Last Update:
HOWTO
PUBLISHED
Nov 24, 2009
Nov 24, 2009
     
 

Related Products

 
Oracle Database - Enterprise Edition
Oracle Database - Standard Edition
     
 

Document References

 
No References available for this document.
     
 

Recently Viewed

 
     




來自 “ ITPUB部落格 ” ，連結：http://blog.itpub.net/17252115/viewspace-1372063/，如需轉載，請註明出處，否則將追究法律責任。

相關文章