3
Using the Oracle Universal Installer for Real Application Clusters

This chapter describes how to use the Oracle Universal Installer (OUI) to install the Oracle9i Enterprise Edition and the Real Application Clusters software. The topics in this chapter include:

• Starting the Oracle Universal Installer

• Using the General Purpose, Transaction Processing, and Data Warehouse Database Configuration Types

• Using the Customized Database Configuration Type

  Note: Perform the procedures in this chapter only after configuring your disk subsystem as described in Chapter 2, and before continuing with the procedures for using the Oracle Database Configuration Assistant (DBCA) as described in Chapter 4.

Starting the Oracle Universal Installer

Follow these procedures to use the Oracle Universal Installer to install the Oracle Enterprise Edition and the Real Application Clusters software.

1. Before running the Oracle Universal Installer, from the node where you intend to run the Installer, verify that you have administrative privileges on the other nodes. Do this using one of the operating system-specific verification methods in Table 3-1.

   Table 3-1 Privilege Verification Methods

   Operating System	Verification Method
   On UNIX	Perform a remote copy (rcp) to the other nodes, including the local node.
   On Windows NT and Windows 2000	Enter the following command for each node that is a part of the cluster where node_name is the node name returned from the lsnodes.exe utility that is in the preinstall_rac directory on the installation CD: NET USE \\node_name\C$ Oracle Corporation recommends using the same user name and password on each node in a cluster or use a domain user name. If you use a domain user name, log on under a domain with a username and password that has administrative privileges on each node.

Then for UNIX platforms only, set the environment variables as described in the following two steps, otherwise, proceed to step 4.

2. If the installation you are about to perform creates the first ORACLE_HOME on your cluster for Real Application Clusters, then set the SRVM_SHARED_CONFIG environment variable to the name of the 100MB volume raw device or shared file that you set up for the configuration storage by entering, for example:

   setenv SRVM_SHARED_CONFIG shared_filename
   
   

   If your platform supports a cluster file system, make sure the partition on which this file resides has least 100MB of free space.

3. Set the DBCA_RAW_CONFIG environment variable. Do this, for example, by executing the following where filename is the name of the ASCII file containing the configuration information:

   setenv DBCA_RAW_CONFIG filename 
   

   For the Customized configuration type, if this is the first installation on your cluster and you have not set the environment variable, then the Installer prompts you for the name of the 100MB file by displaying the Raw Device Name page.

   Note: All installations must be identical across all nodes in your cluster.

4. Run the installer using one of the following procedures for your platform:
   • On UNIX, run the Installer by executing the runInstaller command from the root directory of the first Oracle CD. The Installer displays the Welcome page.

   • On Windows NT and Windows 2000, run the Installer by executing the setup.exe command. The installer displays the Welcome page.

5. On the File Locations page in the Path field under the Destination heading, enter the name of the Oracle home into which you are going to install the Oracle Enterprise Edition and Real Application Clusters software.

6. On the Available Products page, select Oracle9i.

7. On the Install Types page, select Enterprise Edition. The Installer displays the Database Configuration page.

Before continuing, read the following description about how the Oracle Database Configuration Assistant creates your database and about the underlying configuration that it creates. This section also describes the configuration types.

However, if you are familiar with the DBCA and have decided on a database configuration type, proceed to one of the following sections:

• "Using the General Purpose, Transaction Processing, and Data Warehouse Database Configuration Types"

• "Using the Customized Database Configuration Type"

Selecting a Database Configuration Type

When you run the Oracle Universal Installer and select the Oracle9i Enterprise Edition, you can select the General Purpose, Transaction Processing, Data Warehouse, or Customized database configuration type for Real Application Clusters. For the first three configuration types, you must complete the procedures described later in this chapter. Then the Installer runs without further input.

If you select the Customized configuration in the Installer, then you can use the DBCA to create the database as described in Chapter 4 or create the database manually as described in Chapter 5. You can also select the Customized configuration and use the DBCA to create a database using a customized version of one of the preconfigured templates. These templates correspond to the Installer's configuration types of General Purpose, Transaction Processing, and Data Warehouse. The DBCA can also use the New Database template to create a database.

To manually configure your environment, you can select the Software Only database configuration option. However, Oracle Corporation strongly recommends that you use one of the preconfigured database options or use the New Database option and the DBCA.

Descriptions for Using the Configuration Types in Real Application Clusters

The configuration type that you select determines how you proceed. Table 3-2 describes the installation types.

Table 3-2 Oracle Universal Installer Database Configuration Types

Configuration Type	Description	Advantages
Data Warehouse, Transaction Processing, General Purpose	Installs a preconfigured starter database, licensable Oracle options (including Oracle9i Real Application Clusters), networking services, Oracle9i utilities, and online documentation. At the end of the installation, the Database Configuration Assistant creates a Real Application Clusters database and configures it for use.	Minimal input required. You can create your database more quickly than with the Customized type.
Customized	Allows you customize your database options and storage components.	Enables you to create arbitrary tablespaces and datafiles and customize all aspects of your database.
Software Only	Installs only the software. Does not configure the listeners or network infrastructure.	--

The General Purpose, Transaction Processing, and Data Warehouse Configuration Types

If you select one of the first three configuration types on the Installer's Database Configuration screen, complete the procedures in this chapter under the heading "Using the General Purpose, Transaction Processing, and Data Warehouse Database Configuration Types". These three configuration types use preconfigured templates. As mentioned, after you complete these procedures, the OracleNet Configuration Assistant and the DBCA run without further input.

The DBCA processing for these configuration types creates a starter database and configures the Oracle network services. As mentioned, if your platform does not support a cluster file system, then the DBCA verifies that you configured the raw devices for each tablespace.

Note: If you have not properly configured the raw devices as described in Chapter 2, the DBCA cannot create your database.

If you select the Customized configuration you must enter specific information as described in the next section.

Using The Customized Configuration Type

If you select the Customized configuration type, the Oracle Universal Installer runs the Oracle Database Configuration Assistant which offers you a choice of four database templates:

• General Purpose

• Transaction Processing

• Data Warehouse

• New Database

The first three templates create a database that is optimized for that particular environment. You also can customize these templates as required.

The New Database type, however, creates a database without using preconfigured options. Therefore, you must enter specific raw device information for the datafiles to complete a New Database installation as described in Chapter 4, "Creating Databases with the Oracle Database Configuration Assistant".

The following section provides more detail on Oracle Database Configuration Assistant processing when it creates a Real Application Clusters database.

Oracle Database Configuration Assistant Processing

The Oracle Database Configuration Assistant (DBCA) runs as part of the Oracle Universal Installer installation process. When the Installer begins processing, the Oracle Net Configuration Assistant runs. If you configured directory access with the Oracle Net Configuration Assistant, the DBCA will add an entry for the database service to the directory. Clients that you configured with directory access can also access the network information for the database service and connect to the database without a tnsnames.ora file.

After the OracleNet Configuration Assistant completes its processing, the DBCA creates your database using the optimal flexible architecture (OFA). This means the DBCA creates your database files, including the default server parameter file, using standard file naming and file placement practices. The primary phases of DBCA processing are:

• Verify that you correctly configured the shared disks for each tablespace (for non-cluster file system platforms)

• Create the database

• Configure the Oracle network services

• Start the database instances and listeners

You can also use the DBCA in standalone mode to create a database.

See Also: The Oracle Net Services Administrator's Guide if you experience problems, for example, with the listener configuration, and for further information about Lightweight Directory Access Protocol (LDAP)-compliant directory support

Using the General Purpose, Transaction Processing, and Data Warehouse Database Configuration Types

Continuing from Step 7 , execute the following procedures to complete a General Purpose, Transaction Processing, or Data Warehouse configuration:

1. On the Database Configuration page, select General Purpose, Transaction Processing, or Data Warehouse. If the Installer displays the Node Selection page, skip the next step and proceed to step 3.

2. If the Installer does not display the Node Selection page, perform clusterware diagnostics by executing the lsnodes -v command and analyzing its output according to the following platform-specific instructions.
   • UNIX Clusterware Diagnostics

     For UNIX platforms, execute the lsnodes -v command from the /tmp/OraInstall directory. Refer to your vendor's clusterware documentation if the output indicates that your clusterware is not properly installed.

   • Windows NT and Windows 2000 Clusterware Diagnostics

     For these Windows platforms, execute the lsnodes -v command from the preinstall_rac directory.

     lsnodes -v 
     
     

   Refer to your clusterware documentation if the detailed output indicates that your clusterware is not running.

3. Select the nodes that you want to include as part of your Real Application Clusters database. Note that the local node is always selected even though it may not be highlighted on the Node Selection page. Click Next.

4. The Installer displays the Upgrading or Migrating an Existing Database page. Do not use this screen; it is not intended for Real Application Clusters. Click Next.

5. The Installer displays the Database Identification page on which you should enter a global database name. This is a name that comprises the database name and database domain, such as db.us.acme.com. Accept or change the common prefix that is to be used for the Oracle sid for each instance.

   Each instance has a sid that comprises the common prefix you enter in this step and a thread ID that is automatically generated. For example, if you enter db for the sid, the first database instance is given a sid of db1db1, and the second instance is given a sid of db2. Click Next.

6. The Installer displays the Database Character Set page on which you must select a character set and click Next.

7. The Installer displays a summary page. Review the components to be installed and click Install to complete the process.

During installation, the installer does not display messages indicating which components are installed on the remote nodes.

When you complete these procedures, you are ready to administer and deploy your Real Application Clusters environment as described in Oracle9i Real Application Clusters Administration and Oracle9i Real Application Clusters Deployment and Performance.

Using the Customized Database Configuration Type

Continuing from Step 7 on , execute the following procedures to complete a Customized configuration:

1. On the Database Configuration page, select Customized. The Oracle Universal Installer displays the Node Selection page.

2. If the DBCA displays the Node Selection page, skip this step and proceed to step 3. Otherwise, perform clusterware diagnostics by executing the lsnodes -v command and analyzing its output according to the following platform-specific instructions.
   • UNIX Clusterware Diagnostics

     For UNIX platforms, execute the lsnodes -v command from the /tmp/OraInstall directory. Refer to your vendor's clusterware documentation if the output indicates that your clusterware is not properly installed.

   • Windows NT and Windows 2000 Clusterware Diagnostics

     For these Windows platforms, execute the lsnodes -v command from the preinstall_rac directory.

     lsnodes -v 
     
     

   Refer to your clusterware documentation if the detailed output indicates that your clusterware is not running.

3. Select the nodes that you want to include as part of your Real Application Clusters database. Note that the local node is always selected even though it may not be highlighted on the Node Selection page. Click Next.

4. If you have not already set the raw device environment variable and if this is the first Oracle installation on this cluster, then the Installer displays the Raw Device Name page. Enter the name of a raw device that is at least 100MB in size, or a cluster file system file on the Raw Device Name page and Click Next.

5. If the Installer detects a pre-existing Oracle database, the Installer displays the Upgrading or Migrating an Existing Database page. Do not use this page because it is not intended for Real Application Clusters. Click Next.

6. The Installer displays the Database Identification page on which you must enter a global database name. This is a name that comprises the database name and database domain, such as db.us.acme.com. Accept or change the common prefix that is to be used for the Oracle sid for each instance.

   Each instance has a sid that comprises the common prefix you enter in this step and a thread ID that is automatically generated. For example, if you enter db for the sid, the first database instance is given a sid of db1, and the second instance is given a sid of db2. Click Next.

   The Installer displays the Database Character Set page on which you must select a character set and click Next.

7. The Installer displays a summary page. Review the components to be installed and click Install to complete the process.

During installation, the Installer does not display messages indicating that the components are being installed on the remote nodes.

When you complete these procedures, proceed to Chapter 4, "Creating Databases with the Oracle Database Configuration Assistant".