|Oracle9i Real Application Clusters Installation and Configuration
Release 1 (9.0.1)
Part Number A89868-02
This section explains how to enable your single instance database to support Real Application Clusters. It also explains how to begin a project with a single instance Oracle database and migrate to Real Application Clusters. This section covers the following topics:
You may decide to migrate to a cluster database when you have designed your application with Real Application Clusters in mind. However, do not migrate to Real Application Clusters if:
You can migrate to Real Application Clusters and use a non-shared file system. To do this, copy the
ORACLE_HOME to the identical location on each node in your cluster. You can also use Oracle with a clustered file system.
To migrate to Real Application Clusters, consider both the hardware and software requirements and the administrative issues as described in this section.
To migrate to Real Application Clusters you must have:
Note the following administrative issues of conversion:
This procedure explains how to migrate a database from single instance to cluster-enabled Oracle. This procedure assumes you are currently using a file system for your single instance Oracle. To use Real Application Clusters, you must migrate the database from the file system to raw devices.
If your database already uses a shared file system, review the additional notes about these procedures under the heading "Migrating to Real Application Clusters When Using Raw Devices or Shared File Systems".
To migrate a database from a single instance to Real Application Clusters, complete the following procedures:
See your vendor documentation for information about setting up Real Application Clusters hardware.
Create the raw devices needed for the datafiles, control files, and redo log files for Real Application Cluster databases as explained in "Configuring Shared Disk Subsystems for Real Application Clusters".
Because each tablespace on the single instance database must have a matching, identical tablespace on the Real Application Clusters database, it is important that you consolidate, add, or rename the tablespaces on the single instance at this time if needed.
Each additional node in the cluster requires at least two redo log files. Typically, a single instance database only has two redo log files. Therefore, add redo log files for each node using the
ALTER DATABASE ADD LOGFILE statement.
Export the entire database from the single instance database. Use a tool such as the Export utility by entering the following:
file.dmp represents the data from the full database export of the database, and
file.log represents the log of the operation.
Oracle9i Database Utilities for further information about this tool
For UNIX, refer to your vendor's operating system-dependent documentation for instructions about installing operating system-dependent cluster software.
For Windows NT and Windows 2000, use the Oracle-supplied preinstall tool to install the Oracle OSD clusterware.
Except on the server already running the Oracle9i Enterprise Edition, install Oracle9i Enterprise Edition along with the Oracle9i Real Application Clusters option as described in Oracle9i Real Application Clusters Installation and Configuration.
If your current single instance database does not have the supporting hardware, perform a clean install on new cluster hardware. On the server already running Oracle9i Enterprise Edition, install Oracle9i Real Application Clusters using one of the preconfigured database configuration types.
Create a new database on the raw partitions. Depending on the install type and subsequent configuration options, you can create a database with the following methods:
Import the entire database into the empty database using a tool such as the Import utility. To run the Import utility:
file.dmp represents the data from the full database export of the database and
file.log represents the log of the operation.
Oracle9i Database Utilities for more information about this tool
If the original database from which the export file was generated contains tablespaces that are not in the new database, the Import utility attempts to create those tablespaces with associated datafiles. Resolve this by ensuring both databases contain the same tablespaces. The datafiles do not have to be identical. Only the tablespace names need to be the same.
You should make the following parameter changes to accommodate Real Application Clusters:
INSTANCE_NUMBERparameter to a unique value for each instance.
For more information on this procedure, refer to Oracle9i Real Application Clusters Administration.
If your database is already using raw devices on shared disk storage, or if you are using certain operating system file system architectures that are vendor-provided, you do not have to rebuild the database as described in the previous procedures. Instead:
The procedure in this case is much simpler than the procedure described in "Migrating Databases from Single Instance to Cluster-Enabled Environments". The process may only require that you execute an operating system
copy command to move your files to a new location, rather than having to rebuild the database.
Oracle9i Database Migration for procedures for migrating from 7.3, 8.0, and 8i to 9.0.1
If you are upgrading from Oracle8i to Oracle9i, migrate your configuration information using the following post-installation procedure. Do this for each Real Application Clusters database:
conffile is located:
The environment variable referred to in this example is an Oracle8i environment variable.