Oracle® Real Application Clusters Installation and Configuration Guide
10g Release 1 (10.1.0.3) for Linux x86-64
Part No. B14406-01
This chapter describes phase two of the installation procedures for installing the Oracle Database 10g with Real Application Clusters (RAC). This chapter also describes some of the Oracle Universal Installer (OUI) features. The procedures in this chapter apply to -based systems. This chapter contains the following topics:
This section describes OUI features that you should understand before beginning phase two of the RAC installation process. When you run the OUI and select the 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 the fourth type, or the Advanced configuration, then you can use the Database Configuration Assistant (DBCA) to create the database as described in Chapter 5. Oracle recommends that you use the DBCA to create your database.
You can also select the Advanced configuration, select a preconfigured template, customize the template, and use the DBCA to create a database using the template. These templates correspond to the General Purpose, Transaction Processing, and Data Warehouse configuration types. You can also use the 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 and the 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 starter database" configuration option and refer to the manual database creation procedures posted at
The configuration type that you select, as described in Table 4-1, determines how you proceed.
Table 4-1 Oracle Universal Installer Database Configuration Types
|General Purpose, Transaction Processing, and Data Warehouse||Installs a preconfigured starter database, licensable Oracle options (including the Oracle Database 10g with RAC), networking services, Oracle Database 10g utilities, and online documentation. At the end of the installation, the 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.||
If you select one of the first three configuration types on the OUI Select Database Configuration page, then complete the procedure in this chapter under the heading "Installation Setup Procedures". These three configuration types use preconfigured templates. After you complete these procedures, the Oracle Network Configuration Assistant (NETCA) and the DBCA run without further input and the OUI displays a progress indicator during the installation.
The DBCA processing for these configuration types creates a starter database and configures the Oracle network services. If you choose raw devices on the Specify Database File Storage Option page, then the DBCA verifies that you configured the raw devices for each tablespace.
If you select the Advanced configuration, then you must enter specific information as described in the next section.
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.
After installation, the OUI starts the NETCA. After the NETCA completes its processing, the OUI runs the DBCA to create your database using the optimal flexible architecture (OFA). This means that the 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 the Oracle network services
Start the listeners and database instances
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 LDAP support
The remainder of this chapter explains how to use the OUI to install the Oracle Database 10g with RAC.
Perform the following procedures to install the Oracle Database 10g software with RAC.
Note:The Oracle home name and path that you use in this step must be different from the home that you used during the CRS installation in phase one. In other words, you must not install Oracle Database 10g with RAC software into the same home in which you installed the CRS software.
If you enter a pre-existing Oracle home and the Oracle home is not registered with the OUI inventory, then the OUI displays a warning that the Oracle home that you selected is
non-empty. Click OK on this OUI warning dialog to continue installing in that directory. If the Oracle home exists, if the Oracle home is registered with the OUI inventory, and if the Oracle home was created with a cluster install, then the OUI displays the Selected Nodes page as described in Step 4. If you enter an Oracle home that does not exist, then the OUI displays the Specify Hardware Cluster Installation Mode page described in Step 5 of this procedure.
Note:If the OUI does not detect an inventory entry for a CRS installation, or if the Oracle home that you select is an existing non-RAC, single-node home, then the OUI assumes that you are performing a single-node, non-RAC installation.
The Selected Nodes page is an informational page that displays the selected nodes that are associated with a cluster home. Click Next on this page and the OUI displays the Select Installation Type page described in Step 6.
Note:Even if you are using a clustered file system, then the Selected Nodes page should display all the nodes you intend to use for your RAC databases.
When you click Next on the Selected Nodes page, the OUI verifies that the Oracle home directory is writable on the remote nodes and that the remote nodes are operating. The OUI also re-validates user equivalence.
If the OUI detects a network or user equivalence problem on any node that you have included in this installation, then the OUI displays a warning on the Selected Nodes page. This warning appears next to the node and indicates that you should correct a problem on the affected node before proceeding. To resolve problems, examine the OUI actions recorded in the following file:
On the Specify Hardware Cluster Installation Mode page, select an installation mode. The Cluster Installation mode is selected by default when the OUI detects that you are performing this installation on a cluster. In addition, the local node is always selected for the installation. Select additional nodes that are to be part of this installation session and click Next.
See Also:If you select Local Installation, then refer to the Oracle Database Installation Guide, 10g Release 1 (10.1.0.3) for AIXHU-UXLinux x86-64SolarisTru64 UNIXOracle Database Platform Guide for Windows to perform a single-node, non-RAC installation on a UNIXWindows cluster, or to the appropriate quick start guide.
When you click Next on the Specify Hardware Cluster Installation page, the OUI verifies that the Oracle home directory is writable on the remote nodes and that the remote nodes are operating. The OUI also re-validates user equivalence.
If the OUI detects a network or user equivalence problem on any node that you have included in this installation, then the OUI displays a warning on the Specify Hardware Cluster Installation Selection page. This warning appears next to the node and indicates that you should correct a problem on the affected node before proceeding. To resolve problems, examine the OUI actions recorded in the installation log file. The installation log file is:
You can either make corrections and click Next, or you can deselect nodes that have errors and click Next. When you click Next, the OUI displays the Select Installation Type page.
Note:Each node in a cluster must have a CRS home to enable the clusterware to operate on each node. However, the Oracle home can be on a subset of the nodes that are part of your installation.
On the Select Installation Type page you can select Enterprise Edition, Standard Edition, or Custom Install type. If you select Enterprise Edition or Standard Edition, then your installation will include the components related to the chosen edition. If you select the Custom install, then select the individual components that you want to install from the list of available components. Note that if you have purchased a Standard Edition license and you perform a Custom installation, then only install the products covered by the Standard Edition license.
After you make your selection and click Next on the Select Installation Type page, the OUI displays one of the following pages, depending on your configuration and selections:
The Product-specific Prerequisite Checks page verifies the operating system kernel parameters or attributes and calculates the
ORACLE_BASE location. Click Next and the next page that the OUI displays depends on your configuration and selection options as follows:
Available Products Components page: This page is displayed if the OUI detects a previous release of the database and is described in Step 8.
Upgrading an Existing Database page: This page is displayed if you selected a Custom install and is described in Step 9.
Select Database Configuration page: This page is displayed if you did not select a Custom install and there is no database to upgrade. This page is described in Step 10.
On the Upgrading an Existing Database page, you can choose to upgrade one or more existing databases or continue with the installation without performing any upgrades. If you wish to upgrade an existing database, then select the check box labelled "Upgrade an Existing Database" and then select the databases to upgrade from the list provided. If you prefer not to upgrade any of the listed databases, then leave the "Upgrade an Existing Database" check box unchecked.
If you selected "Upgrade an Existing Database", then the OUI continues with the Summary page, described in Step 18, when you click Next. If you did not select "Upgrade an Existing Database", then the OUI continues with the Select Database Configuration page, described in Step 10, when you click Next.
On the Available Products Components page, select the components you wish to install and click Next. This opens the Component Locations page in some cases, such as when insufficient disk space is available. Choose the location for your install and click Next. The OUI will display the Privileged Operating System Groups page described in Step 17.
The Select Database Configuration page, provides options for you to create a preconfigured database as part of the installation process or to install the software without creating a database. If you want to create a database as part of your installation, then select General Purpose, Transaction Processing, Data Warehouse, or Advanced. If you only want to install the software, then select "Do not create a starter database". Click Help for more information about these choices.
Note:If you are installing on a Linux system which uses an ASM library driver, then you must select either the Advanced option or a software only install. Additionally, you must specify
If you choose to create a General Purpose, Transaction Processing, or a Data Warehouse database, then when you click Next, the OUI displays the Specify Database Configuration Options page, described in Step 11. If you choose the Advanced option or select "Do not create a starter database", then when you click Next, the OUI displays the Privileged Operating System Groups page, described in Step 17.
On the Specify Database Configuration Options page, enter a global database name. A global database name is a name that includes the database name and database domain, such as
db.us.acme.com. The name that you enter on this page must be unique among all the global database names used in your environment. Accept or change the common prefix for the Oracle
sid for each instance. Each instance has a
sid that comprises the common prefix that you enter in this step and an instance ID that is automatically generated. Note that a SID prefix cannot exceed characters. Also select a database character set and, on Linux systems only, select any database examples to install from the Sample Schemas.
When you click Next on the Specify Database Configuration Options page, the OUI displays the Select Database Management Option page.
On the Select Database Management Option page, if you are installing on a UNIX-based system and you have already completed the Grid Control Management Agent installation, then you can select either Grid or Local Database control. Otherwise, only Local Database control for database management is supported for RAC. When you use the local Database Control, you can choose the email option and enter the outgoing SMTP server name and email address.
If you perform an installation that does not include Enterprise Manager, for example, a custom software install without Enterprise Manager, an installation with no Enterprise Manager configuration, or a database creation with your own scripts, then you can configure Enterprise Manager later with the OUI, the DBCA, or the Enterprise Manager Configuration Assistant (EMCA) utility.
See Also:Enterprise Manager Grid Control Installation and Basic Configuration for details about installing Grid Control with the OUI utility and Enterprise Manager Advanced Configuration Guide for details about installing Database Control with the DBCA and the EMCA utilities.
When you click Next on the Select Database Management Option page, the OUI displays the Specify Database File Storage Option page.
If you select Automatic Storage Management (ASM): Then the OUI displays an ASM Management Options page showing the disk partition locations from which you must select. These partitions appear in the default location as follows:
On Linux systems, the default partitions dependent on the operating system, as follows:
|Operating System||Default Search String|
If you select File System: Then enter the full path of the location for the datafiles destination on your shared or cluster file system and click Next.
If you select raw devices: Then enter a location for the raw device mapping file and click Next. If the
DBCA_RAW_CONFIG environment variable is set, then the location already is set with the value for this variable.
When you click Next on the Specify Database File Storage Option page, the OUI displays the Specify Backup and Recovery Options page.
If you enable backup on the Specify Backup and Recovery Options page, then you can choose File System or ASM. You will also enter the user name and password. When you click Next on the Specify Backup and Recovery Options page, the next page the OUI displays depends on your configuration and selection options:
If you have selected ASM as a storage option, then the next page is either the Select ASM Disk Group page, if there is an existing ASM instance and disk group available, or the Configure Automatic Storage Management page, described in Step 15, if you need to define your ASM environment.
If you have not selected ASM as a storage option, then the next page is the Specify Database Schema Passwords page, described in Step 16.
The Configure Automatic Storage Management page lists the available disk partition locations. Select the disks that you prepared for your ASM disk groups. To continue to the Specify Database Schema Passwords page, click Next.
On the Specify Database Schema Passwords page, you can choose different passwords for SYS, SYSTEM, DBSNMP, and SYSMAN, or you can choose one password for all of the privileged accounts. When you click Next on the Specify Database Schema Passwords page, the next page that the OUI displays depends on your configuration and selection options as follows:
On Privileged Operating System Groups page, you enter the group name for the
SYSOPER users. When you click Next on the Privileged Operating System Groups page, the OUI displays the Create Database page, which you can ignore if you are upgrading. Finally, the OUI proceeds to the Summary page.
The Summary page displays the software components that the OUI will install and the space available in the Oracle home with a list of the nodes that are part of the installation session. Verify the details about the installation that appear on the Summary page and click Install or click Back to revise your installation.
Review the information on the VIPCA Welcome page, click Next, and the VIPCA displays the Public Network Interfaces page.
On the IP Address page enter an unused (unassigned) public virtual IP address for each node displayed on this page and click Next. After you click Next, the VIPCA displays a Summary page. Review the information on this page and click Finish. A progress dialog appears while the VIPCA configures the virtual IP addresses with the network interfaces that you selected. The VIPCA then creates and starts the VIPs, GSD, and Oracle Notification Service (ONS) node applications. When the configuration completes, click OK to see the VIPCA session results. Review the information on the Configuration Results page, and click Exit to exit the VIPCA.
On Linux systems, run the
root.sh procedure, one node at a time, on each of the nodes that is part of this installation. The VIPCA will not run again on the remote node because the node applications for the remote node are already configured.
Click OK on the OUI dialog to continue the installation. This enables the remaining Oracle configuration assistants to run in the order shown in the following list so that the assistants can perform post-installation processing:
At the end of the database creation, DBCA configures Database Control and starts the services. Database Control is immediately available to administer and monitor your newly installed Oracle Database 10g with Real Application Clusters environment.
You have completed the second and final phase of the installation. Proceed to Chapter 6, "Real Application Clusters Post-Installation Procedures" to perform the post-installation tasks.
Installations of RAC on nodes in Windows-based systems with 256 MB of RAM and 500 MB of virtual memory have the following limitations:
Computers with 256 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, 256 MB and 500 MB respectively, do not install the database. 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 > Programs > Oracle - HOME_NAME > Configuration and Migration Tools > Database Configuration Assistant.
To upgrade an existing database, run DBUA from the Start Menu. Choose Start > Programs > Oracle - HOME_NAME > Configuration and Migration Tools > 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 > Control Panel > System > Advanced > Environment Variables
In the "System variables" dialog, select the Path variable and ensure that the value for the Path variable contains
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.
Perform the following procedures to de-install Oracle Database 10g RAC and CRS software. You must de-install the Oracle database software first before de-installing the Cluster Ready Services (CRS) software. These steps to complete these de-installation tasks are described in the following sections:
Note:These sections describe a complete de-installation of the RAC, ASM, and CRS 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, on UNIX-based platforms, review the
See Also:Oracle Real Application Clusters Administrator's 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
This section describes the procedure to de-install the Oracle Database 10g RAC software. Before you perform these steps, consider making 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 that depend on the software being de-installed.
Delete all of the databases that are dependent on the Oracle home that you are deleting by using the DBCA "Delete a database" option.
If ASM runs from the same Oracle home that you are de-installing, then ensure that there are no other database dependencies on this ASM instance and remove the ASM configuration by logging on as the
oracle user and completing the following steps:
Connect to the ASM instance and run the following command on all of the nodes that are affected by the de-installation of this Oracle home to identify the database instances that are using ASM:
SQL> select INSTANCE_NAME from GV$ASM_CLIENT;
Note:This command only lists the 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.
For each instance listed in the output of the statement that you ran in Step a, stop the respective databases.
Oracle recommends that you backup the database files for all of the databases that are currently using this ASM instance.
Using your connection to the ASM instance, run the following command to identify the disk groups that are managed by the ASM instance:
SQL> select * from V$ASM_DISKGROUP;
For each diskgroup listed in the output of the statement that you ran in Step d, run the following command to drop the disk group:
SQL> drop diskgroup diskgroup_name including contents;
diskgroup_name is the name of the diskgroup.
Shutdown ASM on all of the nodes on which this Oracle home exists. Do this by running the command srvctl
stop asm -n
node_name for all nodes on which this Oracle home exists.
To remove the ASM configuration, run the following command for all nodes on which this Oracle home exists:
srvctl remove asm -n node_name
node_name is the name of a node from which you want to remove the ASM instance.
To remove the ASM configuration, run the following command on all nodes on which this Oracle home exists:
srvctl remove asm -n node_name
node_name is the name of a node from which you want to remove the ASM instance.
If you are de-installing from a Linux-based system with ASMLIB, then run the following procedure. First, run this command to list the disks that you need to delete:
Second, run the following command to delete every disk listed by the previous command:
Third, re-run the
oracleasm listdisks command to confirm that the disks are all deleted. Repeat this command on each of the RAC cluster nodes confirm that the disks have been deleted from all the nodes.
root, run the following commands on all nodes of your RAC cluster:
/etc/init.d/oracleasm stop/etc/init.d/oracleasm disable
If you are using a shared cluster file system for your Oracle home, then run the following commands on the local node:
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 Oracle home, then run the commands from the previous step, Step j, on each node on which the Oracle home exists.
If the listener runs from this Oracle home, then use the NETCA to remove the listener and its configuration.
If the CRS node applications for VIP, ONS, and GSD were created in this Oracle home, then you can remove them and re-create them in another Oracle Database 10g Oracle home, or you can modify the Oracle home for these applications so that they use an alternate Oracle Database 10g Oracle home. Both of these alternative procedures are described in the following two points.
Perform one of the following procedures:
Stop and remove the CRS node applications on each node that is associated with the Oracle home that you are deleting. Do this by running the command
srvctl stop nodeapps -n
node_name for all of the nodes that are affected by the deletion of the Oracle home. Then remove the CRS node applications by running one of the following commands:
Respond to the prompts to confirm your operations for each node. If other Oracle Database 10g RAC Oracle homes exist, then re-create the node applications in that Oracle home by running the command
srvctl create nodeapps.
Alternatively, you can modify the CRS node application Oracle home by running the following command:
srvctl modify nodeapps -o oracle_home
See Also:Oracle Real Application Clusters Administrator's Guide for more information about using RAC scalability features of adding and deleting nodes and instances from RAC databases and for details of the SRVCTL command syntax.
After you complete the previous steps in this procedure, run the OUI and 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 the OUI and want to perform another RAC installation. then you must start a new OUI session.
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 the CRS software using one of the following procedure:
Run the command
/install/rootdelete.sh to disable the CRS applications that are running on the cluster node. The
rootdelete.sh script requires three arguments. If you are running this command on a remote node of the cluster, then use
remote as the first argument, otherwise use
local as the first argument. If the
ocr.loc file is on a shared file system, then use
sharedvar. Otherwise use
nosharedvar as the second argument. If the CRS home is on a shared file system, then use
sharedhome, otherwise use
nosharedhome as the third argument. Repeat this step on each node of the cluster from which you want to de-install CRS.
Run the script
/install/rootdeinstall.sh on a local node to remove the OCR.
This section describes the following de-installation procedures for removing CRS from Windows environments:
De-install the Oracle CRS home by executing the CRS setup script
Run the OUI and in the Welcome page, click Deinstall Products to display the list of installed products on which you can select the CRS home to de-install.
If you have services with names such as
name, then remove them by executing the following command:
crsuser remove user_name
user_name is a user name.
Perform the following procedures to de-install the Oracle 10g CRS software from a Windows environment that also has 9.2 RAC:
\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 Oracle CFS (Cluster File System), then make sure that on all nodes the registry key
HKLM\SOFTWARE\Oracle\osd9i\ocr exists, and has a string value
CfsOcrRoot that points to a release 9.2 OCR (CFS) location.
\bin\ocrconfig -downgrade to downgrade the Cluster Registry to a release 9.2 OCR.
On each node, copy
\oui\bin\setup.exe to invoke Oracle Universal Installer (OUI) and on the Welcome page click Deinstall products to list all the installed products. Select Oracle CRS 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
From a 9.2 RAC Oracle Home on each node run the command
\bin\gsdservice.exe -install. Then start the
On each node, copy