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 


 

 

 


 

 

 

 

 

Adding Nodes at the Vendor Clusterware Layer in UNIX/Linux

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


In UNIX/Linux-based systems using non-Oracle supplied clusterware, new nodes are added at the clusterware layer by using the vendor supplied clusterware documentation. When systems use shared storage for the CRS home, it is important to make sure that the existing clusterware is accessible by the new nodes. Test that prove that the new nodes can be brought online as part of the existing cluster should be conducted. The next section will cover adding the nodes at the clusterware layer.

All platforms require the following steps. The OUI requires access to the private interconnect which has already been verified:

1. Using one of the existing nodes, go to the <CRS home>/OUI/bin directory on UNIX/Linux-based systems or to the <CRS home>\oui\bin directory on Windows-based systems. The addnode script, which is addNode.sh on UNIX/Linux and addNode.bat on Windows, is used to start the OUI.

2. The OUI is started in the add node mode and the OUI Welcome screen appears. Click on the Next button, and the Specify Cluster Nodes for Node Addition screen will appear.

3. On the Specify Cluster Nodes for Node Addition screen, the upper table shows the existing nodes associated with the CRS home from which the OUI was launched, and the lower table is used to enter the public and private node names of the new nodes.

4. When vendor supplied clusterware is used, the public node names automatically appear in the lower table. Click Next and the OUI verifies connectivity on the existing nodes and on the new nodes. The verifications performed by the OUI include:

* That the nodes are up

* That the nodes are accessible by way of the network

* That the user has WRITE permission to create the CRS home on the new nodes

* That the user has write permission to the OUI inventory in the oraInventory directory on UNIX/Linux or Inventory directory on Windows

5. When the OUI detects that the new nodes do not have an inventory location:

* On UNIX/Linux platforms, the OUI displays a dialog asking the user to run the oraInstRoot.sh script on the new nodes

* On Windows platforms, the OUI automatically updates the inventory location in the proper Registry key with no special script required.

When any verifications fail, the OUI will re-display the Specify Cluster Nodes for Node Addition screen with the Status column in both upper and lower tables indicating the errors that occurred. The errors should be corrected or if correction is not possible, deselect the nodes that have errors and proceed. However, if the errors are on existing nodes, they cannot be deselected; the errors must be corrected if nodes are already part of the CRS cluster before node addition can proceed. When all the checks succeed, the OUI Node Addition Summary screen will be displayed.

It is a good practice to install CRS on every node in the cluster that has vendor clusterware installed. The Node Addition Summary screen displays information about the products that are installed in the CRS home that is being extending to the new nodes.  The information shown is:

* The source directory for the add node process, which should be the CRS home.

* The private node names or interconnects that were entered for the new nodes.

* The new nodes that where entered.

* The required space and the available space on the new nodes.

* The installed products listing the products that are installed in the existing CRS home.

If everything is satisfactory, click Next and the OUI displays the Cluster Node Addition Progress screen.

The purpose of the Cluster Node Addition Progress screen is to show the status of the cluster node addition process. The table shown on this screen displays two columns showing the phase of the node addition process and the phase's status according to the following platform specific content:

For UNIX/Linux-based systems this screen shows four OUI phases:

* Instantiate Root Scripts:  This phase instantiates rootaddnode.sh with the public and private node names that were entered on the Cluster Node Addition page.

* Copy the CRS Home to the New Nodes:  This phase copies the CRS home to the new nodes unless this is not required because the CRS home is on a cluster file system.

* Run rootaddnode.sh and root.sh:  This phase displays a dialog prompting the DBA to run rootaddnode.sh on the local node from which the OUI is running. The system then prompts the DBA to run root.sh on the new nodes.

* Save Cluster Inventory:This phase updates the node list associated with the CRS home and its inventory.

For Windows-based systems, this screen shows only three OUI phases:

* Copy CRS Home to New Nodes:  Copies the CRS home to the new nodes unless this is not required because the CRS home is on the Oracle Cluster File System.

* Performs Oracle Home Setup:  Updating the Registry entries for the new nodes, creating the services, and creating folder entries.

* Save Cluster Inventory:  Updates the node list associated with the CRS home and its inventory.

For all platforms, the Cluster Node Addition Progress page's Status column displays one of three possible modes:

* IN PROGRESS: while the phase is in progress

* SUSPENDED: when the phase is pending execution,

* SUCCEEDED: after the phase completes.

Once completion is reached, click Exit to end the OUI session. After the OUI displays the End of Node Addition screen, click on Exit to end the OUI session.

Adding Nodes at the Oracle Clusterware Layer in UNIX/Linux and Windows

1. For Windows-based systems, the command line (Start --> run --> cmd) uses the following command to determine the node names and node numbers that are currently in use:

<CRS home>\bin\olsnodes- n

2. Next, the crssetup.exe command is used with the next available node names and node numbers to add the CRS data for the new nodes. The following syntax is used for crssetup.exe where n is the first new node number, <noden> through <noden+i> is a list of the nodes that are being added, <nodei-number> through <noden+i-number> represent the node numbers assigned to the new nodes where the number is the last node assigned prior to the crssetup.exe execution, and <pnn> through <pnn+i> is the list of private networks for the new nodes:

<CRS home>\bin\crssetup.exe

-nn <noden>,<noden-number>,<noden+1>,<noden+1-number>,...<noden+i>,<noden+i-number>

-pn <pnn>,<noden-number>,<pnn+1>,<noden+1-number>,...<pnoden+i>,<noden+i-number>

3. The values entered are the private network names or IP addresses that were entered in the above procedure in the Specify Cluster Nodes for Node Addition screen. For example:

crssetup.exe -nn node4,4,node5,5 -pn node4_pvt,4,node5_pvt,5

4. On Windows, UNIX and Linux platforms, execute the racgons utility from the bin subdirectory of the CRS home to configure the Oracle Notification Services (ONS) port number as follows:

racgons <noden>:4948 <noden+1>:4948 ... <noden+i>:4948

Once the nodes have been added at the Oracle clusterware layer, the CRS home has been successfully extended from the existing CRS home to the new nodes.

 


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