5 Installing Oracle Database 10g with Real Application Clusters

This chapter describes phase two of the installation procedures for installing Oracle Database 10g with Real Application Clusters (RAC). This chapter also describes some of the Oracle Universal Installer (OUI) features. This chapter contains the following topics:

Verifying System Readiness for Installing the Oracle Database with CVU
Selecting a Database Configuration Type
Installation of Oracle Database 10g with RAC Using Oracle Universal Installer
Installation on Windows-Based Systems with the Minimum Memory Requirements
De-Installing Real Application Clusters Software

Verifying System Readiness for Installing the Oracle Database with CVU

To help to verify that your system is prepared to install Oracle Database with RAC successfully, enter a Cluster Verification Utility (CVU) command using the following command syntax:

cluvfy stage -pre dbinst -n node_list [-r { 10gR1 | 10gR2 } ] [-verbose]

In the preceding syntax example:

The variable node_list is the list of nodes in your cluster, separated by commas

For example, to perform a pre-installation check for an Oracle Database with RAC installation on a two-node cluster with nodes node1 and node2, enter the following command:

cluvfy stage -pre dbinst -n node1,node2 -verbose

Oracle recommends that you select the option -verbose to receive progress updates as CVU performs its system checks. The -verbose option provides detailed test reporting, which you can use to identify the cause of any checks that fail.

If the cluster verification check fails, then review and correct the relevant system configuration steps, and run the test again. Use the system configuration checks described in "Troubleshooting Installation Setup for Windows" to assist you.

Troubleshooting Installation Setup for Windows

If you run CVU and your system fails system configuration checks, then review the CVU report, and use the output to resolve failed configuration checks.

User Equivalence Check Failed

Cause: Failure to establish user equivalency across all nodes.

Action: From the node where you intend to run OUI, verify that you have administrative privileges on the other nodes. To do this, enter the following command for each node that is a part of the cluster:

net use \\node_name\C$

where node_name is the node name.

If you find a node where you are not able to log on, then you must correct the user information on that node. Oracle recommends that you use 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, then log on under a domain with a username and password that has administrative privileges on each node.

When you have corrected the path configuration information on the node, run the CVU check again.

Node Reachability Check Failed

Cause: Failure of one or more nodes to be properly connected for communication.

Action: Possible causes of this message include the following:

Improper network configuration
The node running CVU is unable to connect to one or more nodes in the cluster

Use the following command to check your current configuration on each node:

ipconfig /all

Selecting a Database Configuration Type

This section describes OUI features that you should understand before beginning phase two of the RAC installation process. When you run OUI and select Oracle Database 10g, you can select the General Purpose, Transaction Processing , Data Warehouse, or Advanced database configuration type.

For the first three configuration types, you can complete additional procedures that are described later in this chapter. If you select Advanced configuration, then you can use Database Configuration Assistant (DBCA) to create the database as described in Chapter 6. Oracle recommends that you use DBCA to create your database.

You can also select the Advanced configuration, select a preconfigured template, customize the template, and then use DBCA to create a database using the template. These preconfigured templates correspond to the General Purpose, Transaction Processing, and Data Warehouse configuration types. You can also use DBCA with the Advanced template to create a database.

Oracle recommends that you use one of the preconfigured database options, or use the Advanced option with DBCA to create your database. However, if you want to configure your environment and create your database manually, then select the Do not create a database configuration option, and refer to the manual database creation procedures posted at the following Web site:

http://otn.oracle.com.

Configuration Type Descriptions

The configuration type that you select, as described in Table 5-1, determines how you proceed.

Table 5-1 Oracle Universal Installer Database Configuration Types

Configuration Type	Description	Advantages
General Purpose, Transaction Processing, and Data Warehouse	Installs a preconfigured starter database, Oracle options (including Oracle Database 10g with RAC), networking services, Oracle Database 10g utilities, and online documentation. At the end of the installation, DBCA creates and configures your RAC database.	Minimal input required. You can create your database more quickly than with the Advanced type.
Advanced	Enables you to customize your database options and storage components.	Enables you to create arbitrary tablespaces and datafiles and customize all aspects of your database.
Do not create a starter database	Installs only the software. Does not configure the listeners or network infrastructure and does not create a database.

General Purpose, Transaction Processing, and Data Warehouse Configuration Types

The General Purpose, Transaction Processing, and Data Warehouse configuration types use preconfigured database templates. During installation, if you select one of these preconfigured database types, then OUI starts Oracle Network Configuration Assistant (NETCA) and DBCA, and installs the preconfigured database without further input. During database installation, OUI displays a progress indicator.

DBCA processing for these three configuration types creates a starter database, and configures Oracle network services. If you choose raw devices on the Specify Database File Storage Option page, then DBCA verifies that you configured the raw devices for each tablespace.

If you select Advanced configuration, then you must enter specific information as described in the next section.

Using the Advanced Configuration Type

If you select the Advanced configuration type, then OUI runs DBCA, which displays four preconfigured database template choices:

General Purpose
Transaction Processing
Data Warehouse
Advanced

The first three templates create a database that is optimized for that environment. You also can customize these templates. The Advanced type, however, creates a database without using preconfigured options.

The following section provides more detail about OUI and DBCA processing when creating a RAC database.

Behavior of OUI, DBCA, and Other Assistants During Installation

After installation, OUI starts NETCA. After NETCA completes its processing, OUI runs DBCA to create your database using Optimal Flexible Architecture (OFA). This means that DBCA creates your database files, including the default server parameter file (SPFILE), 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 if you are using raw storage
Create the database
Configure Oracle network services
Start the listeners and database instances

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

Installation of Oracle Database 10g with RAC Using Oracle Universal Installer

Perform the following procedures to install Oracle Database 10g software with RAC.

Start the setup.exe command from the base directory of the Oracle Database 10g Release 2 (10.2) media. When OUI displays the Welcome page, click Next.
Provide information when prompted by OUI. If you need assistance during installation, click Help. If you encounter problems during installation, examine the OUI actions recorded in the installation log file. The log file is located in the Oracle Inventory directory with a name that includes the timestamp (date_time) of the install process, as shown in this example:
```
C:\Program Files\Oracle\Inventory\logs\installActionsdate_time.log 
```
In the preceding syntax example, the variables date and time represents the date and the time of the log file.

Note:
The Oracle home name and path that you provide during database installation must be different from the home that you used during Oracle Clusterware installation in phase one. You must not install Oracle Database 10g with RAC software into the same home in which you installed Oracle Clusterware software.

The following is a list of additional information to note about installation:
- If you select Automatic Storage Management (ASM) during installation, then the default partitions for ASM disk partition locations from which you must select ASM disks are marked as follows:
```
\\.\orcldisk*
```
  If you are installing RAC from the Standard Edition, then you must use ASM for your database storage. Even if you can click other database storage options, they are only supported by the Enterprise Edition and you should not select them.
  
  Note:
  The only partitions that OUI displays for Windows systems are logical drives that are on drives that do not contain a primary partition, and have been stamped with asmtool.
Ensure that the path name for your new Oracle home is defined across the cluster by completing the following procedure on each remote node that is part of your current cluster installation:
1. On each remote node, navigate to Start, and select Control Panel, then System, then Advanced, and then Environment Variables
2. In the "System variables" dialog, select the Path variable and ensure that the value for the Path variable contains oracle_home\bin, where oracle_home is your new Oracle home. If the variable does not contain this value, then click Edit and add this value to the start of the path variable definition in the Edit System Variable dialog. When you have added the value, click OK.
3. Click OK in the Environment Variables page, click OK in the System Properties page, and then close the Control Panel

When have completed all steps for the second and final phase of the installation, proceed to Chapter 7, "Oracle Real Application Clusters Post-Installation Procedures" to perform the post-installation tasks.

Note:

If you need to change the VIP on a RAC node, then you should change it using a SRVCTL command, using the following syntax:

srvctl modify nodeapps -A new_address

Refer to Oracle Database Oracle Clusterware and Oracle Real Application Clusters Administration and Deployment Guide for additional information.

Installation on Windows-Based Systems with the Minimum Memory Requirements

Installations of RAC on nodes in Windows-based systems with 512 MB of RAM and 500 MB of virtual memory have the following limitations:

Computers with 512 MB of memory are not able to run Oracle Database Upgrade Assistant (DBUA), DBCA, or NETCA during an Oracle Universal Installer installation session.
Depending on how many applications are running on the computer, you may need to further increase the paging file size or reduce the size of the System Global Area (SGA) if you run out of virtual memory. Note that if temporary files and the paging file are both stored on the same physical drive, then a situation can occur where the space requirements for one can limit the size of another. If your system has limited free space, then first install the Oracle Database software. After the installation is finished, run NETCA to configure listeners and then DBCA to create a database.

On computer systems that barely meet the minimum memory and virtual memory requirements, 512 MB and 500 MB respectively, do not install the database. Instead, follow these guidelines:

Select Enterprise Edition Installation and deselect "Do not create a starter database"
Select Custom Installation, select "Do not create a starter database" from the Select Database Configuration page.
Select Advanced Installation, select the Custom installation type from the Select Installation Type page, and select No on the Create Database page when prompted to create the database.
Cancel DBCA from the Configuration Assistants page.

After installation, run the appropriate configuration assistant for your needs:

To create a new database, run DBCA from the Start Menu. Choose Start, then Programs, then Oracle - HOME_NAME, then Configuration and Migration Tools, and then Database Configuration Assistant.
To upgrade an existing database, run DBUA from the Start Menu. Choose Start, then Programs, then Oracle - HOME_NAME, then Configuration and Migration Tools, and then Database Upgrade Configuration Assistant.

To ensure that all nodes in your cluster use the new Oracle home, ensure that the path name for the new Oracle home is defined on each node in the cluster by completing the following procedure:

On each node, navigate to Start, then to Control Panel, then to System, then to Advanced and then to Environment Variables
In the "System variables" dialog, select the Path variable and ensure that the value for the Path variable contains oracle_home\bin, where oracle_home is your new Oracle home. If the variable does not contain this value, then click Edit and add this value to the start of the path variable definition in the Edit System Variable dialog and click OK.
Click OK in the Environment Variables page, then click OK in the System Properties page, and then close the Control Panel.

De-Installing Real Application Clusters Software

If you need to de-install Real Application Cluster software, then you must run OUI to de-install the software on the same node from which you performed the installation, and you must de-install Oracle database software first before de-installing Oracle Clusterware software.

Perform the following procedures to de-install Oracle Database 10g RAC and Oracle Clusterware software, as described in the following sections:

De-Installing Oracle Database 10g RAC Software
De-Installing Oracle Clusterware from Windows Environments
De-Installing Automatic Storage Management

Note:
These sections describe a complete de-installation of the RAC, ASM, and Oracle Clusterware software where RAC and ASM share the Oracle home and no other Oracle home exists.
If you have multiple Oracle homes on the cluster, then check for any dependencies that might affect your other databases. Such dependencies can include listeners, ASM instances, and so on that run in the Oracle home to be deleted. To identify dependencies, review the oratab file to identify common Oracle homes.

See Also:
Oracle Database Oracle Clusterware and Oracle Real Application Clusters Administration and Deployment Guide for more information about using RAC scalability features of adding and deleting nodes and instances from RAC databases, and for information about viewing OCR content

De-Installing Oracle Database 10g RAC Software

This section describes the procedure to de-install Oracle Database 10g RAC software. Before you perform these steps, Oracle recommends that you make a backup of any databases that run from the Oracle home you are about to delete. You should then stop any instances and processes on all nodes, including services, that depend on the software that you are de-installing.

Drop all of the databases that are dependent on the Oracle home that you are deleting by using DBCA "Delete a database" option and selecting the correct database or databases to be dropped.
Drop any existing Oracle Database 10g with RAC software by using DBCA "Delete a database" option, and selecting the correct database or databases to be dropped.
If the database is in the Oracle home from which the ASM database runs, then ensure that there are no other database dependencies on these group of ASM instances, and then remove the ASM configuration by logging on as the oracle user and completing the following steps:
1. Connect to the ASM instance and run the following command to determine database instances using this ASM instance.:
```
SQL> select INSTANCE_NAME from GV$ASM_CLIENT;
```
  Note:
  This command only lists database instances that are running. It is possible that other instances are associated with the ASM instance, but they are not currently running. If you removed a database from this Oracle home but the output from the command shows that this ASM instance is supporting a database instance in another Oracle home, then do not remove the ASM instance or the Oracle home.
2. For each instance listed in the output of the statement you run in Step a, stop the respective databases.
3. Oracle recommends that you back up the database files for all of the databases that are currently using this ASM instance.
4. Using your connection to the ASM instance, run the following command:
```
SQL> select * from V$ASM_DISKGROUP;
```
5. For each diskgroup listed in the output of the statement you run in Step d, run the following command:
```
SQL> drop diskgroup diskgroup_name including contents;
```
  where diskgroup_name is the name of the diskgroup.
6. Shut down ASM on all RAC nodes, and verify that all ASM instances are stopped.
7. Run OUI. On the Welcome page, click Deinstall Products to de-install the Oracle home from which ASM was running.
8. To remove the ASM entry from the OCR, run the following command for all nodes on which this Oracle home exists:
```
srvctl remove asm -n nodename
```
  where nodename is the name of a node from which you want to remove the ASM instance.
9. If you are using a shared cluster file system for your Oracle home, then run the following commands on the local node:
```
delete %ORACLE_HOME%\database\*ASM*
delete %ORACLE_BASE%\admin\+ASM
```
  You may need to remove subordinate files or directories before these commands complete successfully.
10. If you are not using a shared cluster file system for your Oracle home, then run the commands from the previous step, Step i, on each node on which the Oracle home exists.
11. Run the following command on each node that has an ASM instance:
```
oradim -delete -asmsid +ASMnode_number
```
  where node_number is the node identifier.
If the listener runs from this Oracle home, then use NETCA to remove the listener and its configuration.
If the RAC software you are deleting uses a different Oracle home from the Oracle home that your ASM environment uses, then start OUI. On the Welcome page, click Deinstall Products to display the list of installed products on which you can select the Oracle home to de-install.

Note:
You cannot perform a RAC installation from the same OUI session in which you perform a RAC de-installation. In other words, if you de-install RAC with OUI and want to perform another RAC installation. then you must start a new OUI session.

De-Installing Oracle Clusterware from Windows Environments

De-install each Oracle Database 10g RAC home by running the procedure in the previous section, "De-Installing Oracle Database 10g RAC Software". Then complete the de-installation by removing Oracle Clusterware software using one of the following procedures:

De-Installing Oracle Clusterware with No Previous Cluster Software Versions
De-Installing Oracle Clusterware, with Clusterware Downgrade to 9.2

De-Installing Oracle Clusterware with No Previous Cluster Software Versions

Perform the following steps to de-install Oracle 10g Oracle Clusterware software from a Windows environment:

Stop and remove the Oracle Clusterware node applications on each node that is associated with the Oracle home that you are deleting. Do this by running the following command for all of the nodes that are affected by the deletion of the Oracle home:
```
srvctl stop nodeapps -n node_name
```
where node_name is the node name. Repeat this command for each node in the cluster.

Then remove Oracle Clusterware node applications by running the following commands:
```
svrctl remove nodeapps -n node_name
```
where node_name is the node name. Repeat this command for each node in the cluster, responding to any operating-system prompts to confirm your operations for each node.
Click Start and navigate to Settings, then to Control Panel, then to Administrative Tools, and then to Services. Stop the service OracleRemExecService.
Start OUI. On the Welcome page, click Deinstall Products to display the list of installed products. Select the Oracle Clusterware home you want to de-install.
If you have services with names such as OracleCRSTokenname, then remove them by running the following command:
```
crsuser remove user_name
```
where user_name is a user name.
Shut down and restart each node that is a member of your cluster.
If you are not using a cluster file system, then on each node, use Windows Explorer to delete the Oracle directory, its subdirectories, and their contents.

De-Installing Oracle Clusterware, with Clusterware Downgrade to 9.2

Perform the following procedures to de-install Oracle 10g Oracle Clusterware software from a Windows environment that also has 9.2 RAC:

Run CRS_Home\bin\GuiOracleOBJManager.exe to make sure that the symbolic link named srvcfg exists and points to a disk partition, if you are not using OCFS to store the OCR.
If Oracle9i release 9.2 clusterware uses OCFS, then ensure the following is true for all nodes:
- The registry key HKLM\SOFTWARE\Oracle\osd9i\ocr exists
- The registry key HKLM\SOFTWARE\Oracle\osd9i\ocr has a string value CfsOcrRoot that points to a release 9.2 OCR (OCFS) location
On each node, use the following command to stop all node processes (virtual IPs, gsds, and ons):
```
srvctl stop nodeapps -n nodename
```
In the preceding syntax example, replace the variable nodename with the name of the node on which you want to stop node processes. Shut down all clusterware processes.
Run CRS_Home\bin\ocrconfig -downgrade -version 9.2 to downgrade the Cluster Registry to a release 9.2 OCR.
On each node, copy CRS_Home\cfs\OcfsFindVol.exe to %SYSTEMROOT%\system32\osd9i\cfs.
Run CRS_Home\oui\bin\setup.exe to start OUI. On the Welcome page click Deinstall products to list all the installed products. Select the Oracle Clusterware home name from the displayed products, and click Remove to deconfigure and de-install the product.
On each node, run %SYSTEMROOT%\system32\osd9i\olm\OracleOBJService.exe /install to re-install the Oracle 9.2 object service. Then start Oracle Object Service.
On each node, run %SYSTEMROOT%\system32\osd9i\cfs\OcfsFindVol.exe /i:%SYSTEMROOT%\system32\osd9i\cfs\OcfsFindVol.exe to re-install the Oracle Cluster Volume service. Then start the OracleClusterVolumeService.
From an Oracle9i Release 9.2 RAC Oracle home on each node run the command ORACLE_HOME\bin\gsdservice.exe -install. Then start the OracleGSDService.
On each node, copy %SYSTEMROOT%\system32\osd9i\orafencedrv.sys %SYSTEMROOT%\system32\drivers\orafenceservice.sys

De-Installing Automatic Storage Management

To remove the Automatic Storage Management (ASM) instances, complete the following tasks:

There is one listener for each node that Oracle Clusterware manages, and that is started and stopped with nodeapps. It is named nodename_LISTENER, and it is located in the Oracle home. Use NetCA to remove this listener and its Oracle Clusterware resources. If necessary, re-create this listener in another Oracle home.
If this is the Oracle home from which the ASM instance runs, then enter the following commands to remove the ASM configuration:
```
srvctl stop asm -n node
srvctl remove asm -n node
```
If you are not using a cluster file system for your ASM Oracle home, then run the Server Control stop and remove commands listed in the previous step on each node on which the Oracle home exists.
If you are using a shared cluster file system for your ASM Oracle home, then run the following commands on the local node:
```
delete %ORACLE_HOME%\database\*ASM*
delete %ORACLE_BASE%\admin\+ASM
```
You may need to remove subordinate files or directories before these commands complete successfully.
If you are not using a shared cluster file system for your ASM Oracle home, then run the commands from the previous step, step 4, on each node on which the Oracle home exists.
Run the following command on each node:
```
%ORACLE_HOME%\bin\oradim.exe -delete -asmsid +ASMnode_number
```
where node_number is the node identifier.