Call now: 252-767-6166  
Oracle Training Oracle Support Development Oracle Apps

 
 Home
 E-mail Us
 Oracle Articles
New Oracle Articles


 Oracle Training
 Oracle Tips

 Oracle Forum
 Class Catalog


 Remote DBA
 Oracle Tuning
 Emergency 911
 RAC Support
 Apps Support
 Analysis
 Design
 Implementation
 Oracle Support


 SQL Tuning
 Security

 Oracle UNIX
 Oracle Linux
 Monitoring
 Remote s
upport
 Remote plans
 Remote
services
 Application Server

 Applications
 Oracle Forms
 Oracle Portal
 App Upgrades
 SQL Server
 Oracle Concepts
 Software Support

 Remote S
upport  
 Development  

 Implementation


 Consulting Staff
 Consulting Prices
 Help Wanted!

 


 Oracle Posters
 Oracle Books

 Oracle Scripts
 Ion
 Excel-DB  

Don Burleson Blog 


 

 

 


 

 

 

 

 

Transferring Oracle_home to Other Nodes

Oracle RAC Cluster Tips by Burleson Consulting

This is an excerpt from the bestselling book Oracle Grid & Real Application Clusters.  To get immediate access to the code depot of working RAC scripts, buy it directly from the publisher and save more than 30%.


To add nodes to the Oracle RAC database later, the existing oracle_home will have to be transferred. To do this, the OUI should be run in ADD NODE mode to configure the new nodes. If there are multiple Oracle homes and the DBA wants to add them to the other nodes, the following steps should be performed for each Oracle home to which the new nodes should be transferred:

1. On the existing main node, from the $oracle_home/oui/bin directory on UNIX-based systems, %oracle_home%\OUI\bin on Windows run either the addNode.sh or addnode.bat script. This starts OUI in the add node mode, which displays the OUI Welcome screen.

2. Using the mouse click the Next button on the Welcome screen and the OUI displays the Specify Cluster Nodes for Node Addition screen.

3. From the Specify Cluster Nodes for Node Addition screen, use the top table showing the existing nodes associated with the Oracle home from which the OUI was launched to determine existing nodes. At the bottom of the page, there is a node selection table showing the nodes that are available for addition. Using the mouse, select the nodes to be added and then click on the Next button.

4. The OUI now verifies proper connectivity and performs availability checks on both the existing nodes and on the nodes to be added. The following list are examples of what items are verified:

* The nodes are active

* The nodes are network enabled

* The installing user has the proper permissions to create the Oracle home on the new nodes

* The installing user has write permission to the OUI inventory in the oraInventory directory on UNIX or the Inventory directory on Windows on the existing nodes and on the new nodes

5. When the new nodes do not have an inventory set up, depending on the system, one of the following will occur:

* For UNIX-based systems, the OUI displays a dialog asking that the oraInstRoot.sh script be run on the new nodes.

* For Windows-based systems, the Registry is automatically updated with the inventory location by the OUI

If any of the other checks fail, the node that has the error should be deselected or the error fixed in order to proceed. Nodes that are already a part of the cluster cannot be deselected.  The problems on the existing nodes must be corrected before proceeding with node addition. Once all of the checks are successful, the OUI displays the Node Addition Summary screen.

The following information about the products that are installed in the Oracle home that are going to extend to the new nodes is listed on the Node Addition Summary screen:

* The Oracle home that is the source for the add node process

* The existing node and new node information

* The new nodes that have been selected

* For new nodes, the required and available space

* The listing of all the products that are already installed in the existing Oracle home

6. Click the Finish button, and the OUI will display the Cluster Node Addition Progress screen.

The status of the cluster node addition process is shown on the Cluster Node Addition Progress screen. The table on this page shows two columns profiling the addition phases:

* The node addition phase progress

* The phase's status according to the following platform-specific content:

On Linux or UNIX-based systems, the Cluster Node Addition Progress page shows four distinct OUI phases:

* Instantiation of the Root Scripts: This phase instantiates the root.sh script in the new Oracle home by copying it from the local node

* Copying of the Oracle Home to the New Nodes: This phase copies the rest of the entire Oracle home from the source node to the new nodes, unless the Oracle home is on a cluster file system

* Running of the root.sh: Displays the dialog about running the root.sh script from the root user on the new nodes

* Saving of the Cluster Inventory: Update of the node list associated with the Oracle home and its inventory

While on Windows-based systems, the Cluster Node Addition Progress will show the following three OUI phases:

* Copying of the Oracle Home To New Nodes: Copies the entire Oracle home to the new nodes unless the Oracle home is already on a cluster file system

* Perform the Oracle Home Setup: Update of the Registry entries for the new nodes, creation of the needed services, and creation of the needed folder entries

* Saving Cluster Inventory: The update of the node list associated with the Oracle home and its inventory

For all of the platforms, the Cluster Node Addition Progress screen?s Status column displays one of three status messages:

* SUCCEEDED when the phase completes

* IN PROGRESS when the phase is active

* SUSPENDED when the phase is awaiting execution

7. When the OUI displays the End of Node Addition screen, click on the Exit button to end the OUI session.

8. For UNIX/Linux-based systems only, the root.sh script will be run next.

9. Next, the vipca utility must be run from the bin subdirectory of the Oracle home using the -nodelist option identifying the complete set of nodes that are now part of the RAC database beginning with Node1 and ending with <NodeN> using the following syntax:

vipca -nodelist Node1,Node2,Node3,...<NodeN>

When the private interconnect interface names on the new nodes are not the same as the interconnect names on the existing nodes, the private interconnect must be configured for the new nodes. This is done by executing the Oracle Interface Configuration (OIFCFG) utility with the SETIF option. The OIFCFG executable is run from the bin directory of the hosts Oracle home. The command is executed using the following syntax where <subnet> is used the subnet for the private interconnect for the RAC databases to which nodes are added:

oifcfg setif <interface-name>/<subnet>:<cluster_interconnect|public>

For example:

oifcfg setif eth0/162.178.26.0:cluster_interconnect

Once the procedures in the previous section are complete, the new nodes are defined at the cluster database layer. The new database instances can now be added to the new nodes as described next.

 


This is an excerpt from the bestselling book Oracle Grid & Real Application Clusters, Rampant TechPress, by Mike Ault and Madhu Tumma.

You can buy it direct from the publisher for 30%-off and get instant access to the code depot of Oracle tuning scripts.

http://www.rampant-books.com/book_2004_1_10g_grid.htm


 

 
��  
 
 
Oracle Training at Sea
 
 
 
 
oracle dba poster
 

 
Follow us on Twitter 
 
Oracle performance tuning software 
 
Oracle Linux poster
 
 
 

 

Burleson is the American Team

Note: This Oracle documentation was created as a support and Oracle training reference for use by our DBA performance tuning consulting professionals.  Feel free to ask questions on our Oracle forum.

Verify experience! Anyone considering using the services of an Oracle support expert should independently investigate their credentials and experience, and not rely on advertisements and self-proclaimed expertise. All legitimate Oracle experts publish their Oracle qualifications.

Errata?  Oracle technology is changing and we strive to update our BC Oracle support information.  If you find an error or have a suggestion for improving our content, we would appreciate your feedback.  Just  e-mail:  

and include the URL for the page.


                    









Burleson Consulting

The Oracle of Database Support

Oracle Performance Tuning

Remote DBA Services


 

Copyright © 1996 -  2017

All rights reserved by Burleson

Oracle ® is the registered trademark of Oracle Corporation.

Remote Emergency Support provided by Conversational