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 


 

 

 


 

 

 

 

 

Creating a Single Instance on a Cluster to Oracle Database 10g RAC

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


There are three possible scenarios where a single instance database can exist on a cluster machine, they are:

* The Oracle home where the database is running is cluster installed.

* The Oracle home where the database is running is cluster installed, but the RAC feature is disabled.

* The Oracle home where the database is running is not cluster installed.

If the above situations exist, the following sections should be used to convert the single instance database on a clustered machine into a RAC instance for all three of these scenarios.

The Instance Is On a Cluster and Running From a Cluster Enabled Oracle Home

The next procedure is used for conversion of a single instance database on a cluster running from a cluster installed Oracle home into a RAC enabled instance.

1. Use the DBCA to create a preconfigured image of the single instance database as was previously documented and shut down the single instance database.

2. To add other nodes to the cluster, add and connect these nodes to the cluster as described earlier. Verify that all of the nodes added to the cluster can access the shared storage.

To verify that the installation is configured correctly, perform the following steps:

1. Verify that the new cluster nodes can access the private interconnect. The interconnects must be properly configured before these procedures can be completed.

2. When a cluster file system is not used, determine the location where the cluster software was installed on the existing nodes. Verify that there is at least 250MB of free space on the same location on each of the new nodes in which to install the Cluster Ready Services software. In addition, make sure there is enough free space, about two Gigabytes, on each new node to install the Oracle binaries.

3. Ensure that user equivalence is established on the new nodes by executing the following platform-specific commands:

* For UNIX/Linux-based systems: Verify user equivalence to and from an existing node to the new nodes using rsh or ssh. Verify it in both directions.

* For Windows-based systems: Make sure that the following command can be executed from each of the existing nodes of the cluster where the host_name specified is the public network name of the new node:

NET USE \\host_name\C$

If the proper administrative privileges on each node are set, the operating system responds with:

Command completed successfully.

After the above procedures are complete, the new nodes are connected to the cluster and configured with the required software to make them visible to the clusterware. The new nodes are configured as members of the cluster by extending the cluster software to the new nodes as described next.

Extending Clusterware and Oracle Software to New Nodes

The next sections describe how to add new nodes to the clusterware and to the Oracle database software layers.  The topics covered will be:

* Adding Nodes at the Vendor Clusterware Layer in UNIX

* Adding Nodes at the Oracle Clusterware Layer in UNIX and Windows

The RMAN CONVERT Clause

The purpose of the CONVERT clause is to convert the format of a transport set from one platform to another to allow a quick transport of a tablespace across different platforms. Content providers can now publish structured data as transportable tablespaces and distribute it to customers who can quickly integrate this data into Oracle, regardless of their current platform within compatibility limits.

Data from a large data warehouse server can be distributed to data marts on smaller computers, such as Windows 2000 workstations.

Example uses of the command are:

CONVERT Clause Syntax:

CONVERT [TABLESPACE 'tablespace_name'[,]| DATAFILE 'filename'[,]] convert_optionList ;
convert_optionList::=
[[FROM|TO] PLATFORM [=] {identifier|quoted_string}]|
[FORMAT [=] formatSpec]|
[DB_FILE_NAME_CONVERT [=] ( 'string_pattern'[,])]|
[PARALLELISM [=] integer]]


Keywords and Parameters

TABLESPACE tablespace_name

The TABLESPACE keyword specifies the name of a tablespace in the source database to be transported to the destination database on a different platform. CONVERT TABLESPACE can only be used when connected to the source database, not from the destination database. This is because, until the tablespace transport has been completed, the destination database has no way of recognizing the tablespace name for use with the CONVERT TABLESPACE statement.

DATAFILE datafile_name

This specifies the name of a to-be-converted data file that is to be transported into the destination database.


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