| Oracle® Real Application Clusters Installation and Configuration Guide 10g Release 1 (10.1) for AIX-Based Systems, hp HP-UX PA-RISC (64-bit), hp Tru64 UNIX, Linux, Solaris Operating System (SPARC 64-bit) Part No. B10766-01 |
|
 |
 |
| Oracle® Real Application Clusters Installation and Configuration Guide 10g Release 1 (10.1) for AIX-Based Systems, hp HP-UX PA-RISC (64-bit), hp Tru64 UNIX, Linux, Solaris Operating System (SPARC 64-bit) Part No. B10766-01 |
|
|
|
This chapter describes the phase two 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 topics in this chapter are:
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 Customized 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 Customized configuration, then you can use the DBCA to create the database as described in Chapter 9. Oracle recommends that you use the DBCA to create your database.
You can also select the Customized 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 Custom template to create a database.
To manually configure your environment and manually create your database, select the Software Only database configuration option and refer to the manual database creation procedures posted at http://otn.oracle.com. However, Oracle recommends that you use one of the preconfigured database options or use the Custom option and the DBCA to create your database.
The configuration type that you select, as described in Table 8-1, determines how you proceed.
Table 8-1 Oracle Universal Installer Database Configuration Types
If you select one of the first three configuration types on the OUI Database Configuration page, then complete one of the platform-specific procedures in this chapter under the heading "Installation Setup Procedures". These three configuration types use preconfigured templates. After you complete these procedures, the Oracle Net Configuration Assistant 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 do choose raw devices on the Storage Options page, 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 Appendix C, then the DBCA cannot create your database. |
If you select the Customized configuration, then you must enter specific information as described in the next section.
When you select the Customized configuration type, the OUI runs the DBCA which displays four preconfigured database template choices:
General Purpose
Transaction Processing
Data Warehouse
Custom
The first three templates create a database that is optimized for that environment. You also can customize these templates. The Custom type, however, creates a database without using preconfigured options. Therefore, if you are not using a cluster file system, then you must enter specific raw device information for the datafiles to perform a Custom installation as described in Chapter 9, " Creating RAC Databases with the Database Configuration Assistant ".
The following section provides more detail about OUI and DBCA processing when creating a RAC database.
After installation, the OUI starts the Oracle Net Configuration Assistant. After the Oracle Net Configuration Assistant 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.
If the user who installed CRS is different from the user who installs RAC, then all of the user-level pre-install steps must be completed.
Verify user equivalence by executing the ssh command on the local node with the date command argument using the following syntax:
ssh node_name date ssh node_name xclock
The output from these commands should be the timestamp of the remote node identified by the value that you use for node_name. In additionally, the system should display the remote node's xclock. When you execute these commands, you should not see any other errors, warnings, or additional output. If ssh is in the /usr/local/bin directory, then use ssh to configure user equivalence.
The OUI cannot use ssh to verify user equivalence if ssh is in another location in your PATH. In this case, use rsh to confirm user equivalence.
|
Note: When you test user equivalence by executing thessh or rsh commands, the system should not respond with questions nor should you see additional output, for example, besides the output of the date command and the xclock. You should also not have any echo messages in your .login or .cshrc files. |
Perform a network connectivity test to ensure that all nodes on which you want to perform this installation can communicate with each other. Ensure that the public and private network interfaces have the same interface names on each node of your cluster.
Set directory and file creation permissions using the umask command so that you can write as oracle user to all of the Oracle homes in the RAC database environment in which you are performing this installation.
Create directories for the Oracle home and Oracle datafiles according to OFA standards.
|
Note: The Oracle home that you create for installing Oracle Database 10g with the RAC software cannot be the same Oracle home that you used during the clusterware installation. |
Perform the following procedures to install the Oracle Database 10g with RAC.
Execute the runInstaller command from the root directory of the Oracle Database 10g Release 1 (10.1.0.2) CD-ROM.
When the OUI displays the Welcome page, click Next, and the OUI displays the Specify File Locations page.
The Source field on the Specify File Locations page is pre-populated with the path to the file Oracle Database 10g products.xml. Enter the Oracle home name and location in the target destination and click Next.
|
Note: The Oracle home 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 on that directory. If the Oracle home exists and it is registered with the OUI inventory and the Oracle has a cluster home, 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 Install Type page described in Step 6.
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:
OraInventory/logs/installActionsdate_time.log
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) for UNIX Systems to perform a single-node, non-RAC installation on a cluster, or refer to the appropriate platform-specific 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 following file:
OraInventory/logs/installActionsdate_time.log
You can either make corrections and click Next, or you can deselect nodes that have errors and click Next and the OUI displays the Install 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 Install Type page you can select Enterprise Edition, Standard Edition, or Custom Install type. If you select Enterprise Edition or Standard Edition and click Next, then the OUI displays the Prerequisite Check page. The Custom install type enables you to select the individual components that you want to install from the list of available components. If you have purchased a Standard Edition license and you perform a Custom installation, then ensure that you only install the products covered by the Standard Edition license.
The Prerequisite Check page verifies the operating system kernel parameters or attributes and calculates the ORACLE_BASE location. Click Next. If the OUI discovers a database to upgrade, then the OUI displays the Upgrading an Existing Database page that lists the databases that are available to upgrade. Select a database to upgrade as described in Step 8. If you do not select a database to upgrade and click Next, then the OUI displays the Create Starter Database page as described in Step 9. Additionally, if the OUI does not find any databases to upgrade, then the OUI displays the Create Starter Database Page as described in Step 9 if you choose Enterprise Edition or Standard Edition.
On the Upgrading an Existing Database page, select the check box labelled "Upgrade an Existing Database" and then select the databases to upgrade from the list below. Click Next, and this by-passes the database creation process and the OUI displays the Summary page as described in Step 15.
On the Create a Starter Database Page select General Purpose, Transaction Processing, Data Warehouse, or Advanced. Choose to either create a database or to perform a Software Only installation, click Next, and the OUI displays the Database Configuration Options Page.
If you select "Do Not Create Starter Database", then select a Software Only installation. Click Next, and the OUI performs a software installation without performing any configuration tasks.
If you choose the "Custom Install Type", then the OUI performs a prerequisite check for the operating system kernel parameters or attributes and the OUI calculates the ORACLE_BASE location.
After you make your selection on this page and click Next, the OUI displays the Database Configuration Options page.
On the 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. Also select a database character set and select any database examples to install. Note that a SID cannot exceed five characters in length. Click Next and the OUI displays the Database Management Option for Database Control page (Grid or Local Database). If you choose the local Database Control, then you can choose the email option and enter the outgoing SMTP server name and email address. If there is an existing Enterprise Manager Grid available, then there will be a drop-down menu in which you can indicate that you want to use Enterprise Manager Grid Control for database management. Click Next, and the OUI displays the Data Storage Option page.
Select a data storage option on the Data 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 which is in following format:
/dev/rdsk/*
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 Data Storage Option page, the OUI displays the Backup and Recovery page.
If you enable backup on the Backup and Recovery page, then you can choose File System or ASM. You will also enter the user name and password. When you click Next on the Backup and Recovery page, the OUI displays the Schema Password page.
On the Schema Password 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 Schema Password page, the OUI displays the Operation System Group page.
On the Operation System Group page enter the group name for the SYSDBA and SYSOPER users. When you click Next on the Operation System Group page, the OUI displays 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.
During the installation, the OUI copies software to the local node and then copies the software to the remote nodes. Then the OUI prompts you to run the root.sh script on all the selected nodes. The root.sh script starts the Virtual Internet Protocol Configuration Assistant (VIPCA) and displays the VIPCA Welcome page. Before you run root.sh, make sure that your display environment variables are properly set.
Review the information on the VIPCA Welcome page, click Next, and the VIPCA displays the Public Network Interfaces page.
On the Public Network Interfaces page determine the network interface cards (NICs) to which you want to assign your public VIP addresses, click Next, and the VIPCA displays the IP Address 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.
Repeat the root.sh procedure on all nodes that are part of this installation. The VIPCA will not run again on the remote node because the remote node is already configured.
After running root.sh on all the nodes in the previous step, 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:
Net Configuration Assistant (NetCA)
Database Configuration Assistant (DBCA)
At the end of the installation, the OUI starts Enterprise Manager Database Control in standalone mode. 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 10, " Real Application Clusters Post-Installation Procedures" to perform the post-installation tasks.
|
Note: Use the DBCA and the OUI to deinstall RAC. |
Execute the following procedures to de-install Oracle Database 10g RAC software. First deinstall the Oracle database software, then deinstall the Cluster Ready Services (CRS) software as described in the following sections:
Execute the following procedures to deinstall the Oracle Database 10g RAC software:
Remove the Oracle Database 10g with RAC by using the DBCA to drop the database.
If this is the Oracle home from which the per-node listener named LISTENER_nodename runs, then use NetCA to remove this listener and its CRS resources. If necessary, re-create this listener in another home.
If this is the Oracle home from which the per-node ASM instance runs, then use the command srvctl stop asm -n node followed by srvctl remove asm -n node to remove its CRS resources. Remove any oratab entry beginning with +ASM. If necessary, re-create the ASM instance in another home.
If VIP, ONS and GSD node applications are created using this Oracle home, then you must stop and remove these node applications. To stop CRS node applications, execute the command srvctl stop nodeapps -n node. Repeat the same command for each node in the cluster. To remove CRS node applications, execute the command $ORACLE_HOME/install/rootdeletenode.sh. If other Oracle Database 10g RAC Oracle homes exist, then recreate the node applications by running the root.sh script in that 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 |
|
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 deinstall RAC with the OUI and want to perform another RAC installation. then you must start a new OUI session. |
Execute the following procedures to deinstall the CRS software:
Deinstall each Oracle Database 10g RAC home by executing the procedures under the previous heading, "De-Installing Oracle Database 10g RAC Software".
Execute the command CRSHome/install/rootdelete.sh to disable the CRS applications that are on 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, 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 for each node of the cluster from which you want to deinstall CRS.
Execute the script CRS Home/install/rootdeinstall.sh on a local node to remove the OCR.
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 deinstall.
