Skip Headers
Oracle® Real Application Clusters Installation Guide
11g Release 1 (11.1) for Linux and UNIX

B28264-07
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Index
Index
Go to Master Index
Master Index
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
PDF · Mobi · ePub

2 Installing Oracle Database 11g with Oracle Real Application Clusters

This chapter describes phase two of the installation procedures for installing Oracle Database 11g release 1 (11.1) with Oracle Real Application Clusters (Oracle RAC). Phase one is the completion of installing Oracle Clusterware, as described in Oracle Database Oracle Clusterware Installation Guide for your platform.

See Also:

Oracle Database Installation Guide for your platform for additional information, such as how to open compressed files, and other information about setting up files for installation

Also, during installation, click Help to find explanations of options and prompts for each installation screen

This chapter contains the following topics:

2.1 Verifying System Readiness for Installing Oracle Database with CVU

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

/mountpoint/runcluvfy.sh stage -pre dbinst -n node_list [-r {10gR1|10gR2|11gR1}] 
[-osdba osdba_group][-verbose]

In the preceding syntax example:

For example, to perform a pre-installation check for Oracle Database 11g release 1 (11.1) with Oracle RAC installation on a two-node cluster with the mountpoint /mnt/dvdrom, and with nodes node1 and node2, enter the following command:

$ /mnt/dvdrom/cluvfy/runcluvfy.sh stage -pre dbinst -n node1,node2 -verbose

Oracle recommends that you select the option -verbose to receive progress updates as the 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 your Oracle Clusterware installation is not functioning. Review and correct the relevant system configuration steps, and run the test again.

See Also:

Oracle Database Oracle Clusterware Installation Guide for your platform

2.2 Reviewing Oracle Application Express Requirements

With the Oracle Database 11g release, Oracle Application Express is provided as an Oracle Database option, rather than as an Oracle Application option. If you intend to install Oracle Database after installing Oracle Clusterware, and you have an existing Oracle Database installation that you are upgrading, then review the following Oracle Application Express requirements:

2.2.1 Browser Requirements for Oracle Application Express

To view or develop Oracle Application Express applications, Web browsers must support Java Script, and the HTML 4.0 and CSS 1.0 standards. The following browsers meet this requirement:

  • Mozilla 1.2 or a later version

  • Firefox 1.0 or a later version

2.2.2 Installing APEX with Existing Oracle HTML Server Installations

Oracle Application Express must have access to Oracle HTTP Server and mod_plsql to run. The following products include the versions of HTTP Server and mod_plsql that meet this requirement:

  • Oracle 9i Database release 2 (9.2) or a later version

  • Oracle 9i Application Server release 1 (1.0.2.2) or a later version

2.2.3 Oracle Text Requirement for Oracle Application Express

Oracle Text must be installed so that you can use the searchable online Help in Oracle Application Express. By default, Oracle Text is installed as part of Oracle Database.

See Also:

Oracle Text Application Developer's Guide for more information about Oracle Text

2.2.4 Oracle XML DB Requirement for Oracle Application Express

To upgrade an existing database to Oracle Database 11g release 1 (11.1), Oracle XML DB must be installed in the Oracle database that you want to upgrade. If you are using a preconfigured database created either during an installation or by Database Configuration Assistant (DBCA), then Oracle XML DB is already installed and configured.

See Also:

Oracle XML DB Developer's Guide for more information about manually adding Oracle XML DB to an existing database

2.3 Selecting a Configuration Option

This section describes OUI features that you should understand before beginning phase two of the Oracle RAC installation process.

See Also:

Appendix C, " Converting to Oracle Real Application Clusters from Single-Instance Oracle Databases" for information about how to convert single-instance databases to Oracle RAC

On the Select Configuration page, you are given the following options:

If you are installing Oracle Database software, then Oracle recommends that you use one of the preconfigured database options, or select the Advanced option on the Select Configuration page, and configure a custom starter database.

If you want to configure your environment and create your database manually, then select Do not create a database on the Select Configuration page, and refer to the manual database creation procedures posted at the following Web site:

http://otn.oracle.com

See Also:

If you have an existing Oracle installation, then document version numbers, patches, and other configuration information, and review upgrade procedures for your existing installation. Review Oracle upgrade documentation before proceeding with installation, to decide how you want to proceed.

For late-breaking updates and best practices about preupgrade, post-upgrade, compatibility, and interoperability discussions, refer to "Oracle Upgrade Companion." "Oracle Upgrade Companion" is available through Note 466181.1 on OracleMetaLink:

https://metalink.oracle.com/

2.4 Automatic Storage Management Configuration

If you want to use Automatic Storage Management, then select Configure Automatic Storage Management (ASM), and provide information as prompted. Click Help if you need assistance.

Before you start Oracle Automatic Storage Management installation, ensure that you have the list of paths to the storage devices on which you want to configure ASM disk groups.

If you are installing ASM 11g release 1 (11.1) on a system with an existing ASM installation, you choose to upgrade the existing ASM installation, and you have running databases on that system, then you must stop ASM on those systems before you start the upgrade. To do this, enter the following command:

srvctl stop asm -n ASM_nodename

Note:

You can have only one version of ASM installed and running on a cluster.

2.5 Preparing for a Rolling Upgrade of Automatic Storage Management

Starting with Oracle ASM 11g, you can perform rolling upgrades of ASM. This can be performed with 11.1 and later releases; it is not backward-compatible. To prepare for a rolling upgrade, perform a software-only installation of ASM on all nodes in the cluster.

Note the following if you intend to perform rolling upgrades of ASM:

See Also:

Oracle Database Upgrade Guide and Oracle Database Storage Administrator's Guide for additional information about preparing an upgrade plan for ASM, and for starting, completing, and stopping ASM upgrades

2.6 Oracle Database Vault Configuration

You can install Oracle Database Vault using a Custom installation. Review the following information if you want to install Oracle Database Vault:

2.6.1 Oracle Database Vault Requirements

Oracle Database Vault requires the following:

  • An Oracle Database Enterprise Edition installation (single-instance or Oracle RAC)

  • Oracle Enterprise Manager Console.

  • If performing a Custom installation, then the Custom template needs to be selected when configuring the database with Oracle Database Vault.

  • Oracle Clusterware running (for installation in an Oracle RAC environment)

    Note:

    You must have root access if you need to start up Oracle Clusterware.

    The command crsctl start crs also starts the database. Before you start OUI to install Oracle Database Vault, shut down the database.

  • A listener configured for the database into which you are installing Oracle Database Vault. To ensure that the new listener process starts during the installation, you must shut down existing listeners before starting Oracle Universal Installer.

  • Oracle Database Vault installation owner write access to the Oratab file (/etc/oratab) and to the oraInst.loc file (/etc/oraInst.loc). This access is provided either by using the same installation owner as you use with the Oracle Database installation, or another user with oinstall group membership.

  • An existing password file for the Oracle Database. In addition, the password file authentication parameter, REMOTE_LOGIN_PASSWORDFILE, must have been set to EXCLUSIVE or SHARED.

    You can set the REMOTE_LOGIN_PASSWORDFILE parameter in the init.ora file. Use the orapwd utility to create and manage password files.

    See Also:

    Oracle Database Administrator's Guide for more information on creating and maintaining a password file

2.6.2 Oracle Database Vault Accounts

Oracle Database Vault prompts for two accounts that you can create during installation. These are the Oracle Database Vault Owner and the Oracle Database Vault Account Manager accounts. You must supply an account name and password for the Oracle Database Vault Owner during installation. Creating an Oracle Database Vault Account Manager is optional.

2.6.2.1 Oracle Database Vault Owner

The Oracle Database Vault Owner account is granted the DV_OWNER role. This account can manage Oracle Database Vault roles and configuration.

The Oracle Database Vault Owner user name can be a minimum of 2, and a maximum of 30 characters long. The account password can be a minimum of 8, and a maximum of 30 characters.

The password that you choose for the Oracle Database Vault Owner account must be a secure one. The following password restrictions are enforced:

  • The password must include at least one alphabet, one digit, and one nonalphanumeric character (symbol).

  • The password cannot be the same as the account name.

  • The password cannot contain any consecutive repeating characters.

2.6.2.2 Oracle Database Vault Account Manager

The Oracle Database Vault Account Manager is granted the DV_ACCTMGR role. This account is used to manage database user accounts. The Oracle Database Vault Account Manager is created to facilitate separation of duties. If you do not choose to create the Oracle Database Vault Account Manager account, then the DV_ACCTMGR role is granted to the Oracle Database Vault Owner account by default.

The Oracle Database Vault Account Manager user name can be a minimum of 2, and a maximum of 30 characters long. The account password can be a minimum of 8, and a maximum of 30 characters.

The same password restrictions that apply to Oracle Database Vault Owner are applicable to Oracle Database Vault Account Manager as well.

2.6.3 Multiple Oracle Database Vault Homes

You can install Oracle Database Vault more than once on the same system, in different Oracle homes.

2.6.4 Starting the Listener with Oracle Database Vault Installations

You need to start the listener and database on all Oracle RAC nodes other than the one on which the installation is performed. You must use the Server Control (srvctl) utility to start and stop Oracle Database Vault Oracle RAC instances. Do not use SQL*Plus to start and stop Oracle RAC instances.

For example:

$ORACLE_HOME/bin/lsnrctl start listener_name
$ORACLE_HOME/bin/srvctl start instance -d database_name -i instance_name

2.6.5 Installing Oracle Database Vault

You can install Oracle Database Vault with a Custom installation, either when you install Oracle RAC, or after you install Oracle RAC.

2.6.5.1 Installing Oracle Database Vault During Oracle RAC Installation

To install Oracle Database Vault while installing Oracle RAC:

  1. Start Oracle Universal Installer, and select Custom installation.

  2. In addition to the default installation components, select Oracle Label Security (OLS) and Oracle Database Vault.

  3. Provide the required administrative user accounts and passwords, and proceed with installation.

2.6.5.2 Installing Oracle Database Vault After Oracle RAC Installation

To install Oracle Database Vault after installing Oracle RAC:

  1. Install the Oracle RAC Enterprise Edition database.

  2. Stop all database processes

  3. Start Oracle Universal Installer, and select Custom installation.

  4. Select Oracle Label Security (OLS) and Oracle Database Vault, and install.

  5. Start the Oracle RAC database.

  6. Start DBCA, and select the option Configure Database

  7. In the component list, select Oracle Label Security and Oracle Database Vault

  8. Provide the required administrative user accounts and passwords, and proceed with configuration.

2.7 Oracle Database Configuration Type Descriptions

When you run OUI, 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 3. Oracle recommends that you use DBCA to create your database.

2.7.1 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 the preconfigured database templates, 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 the 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.

2.7.2 Using the Advanced Configuration Type

If you select the Advanced configuration type, then OUI runs DBCA, which displays General Purpose, Transaction Processing, Data Warehouse, and a fourth configuration type, Custom Database.

Use the Advanced Configuration type to address specific requirements, such as creating a database in a nondefault character set, or adding translation of product user interface into languages other than English. By default, the installation configures the character set of a new database based on the language of the operating system.

See Also:

Oracle Database Globalization Support Guide for detailed information on character sets and language configuration

The first three templates are customizable versions of the preconfigured database types. The Custom Database type creates a database without using preconfigured options.

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

See Also:

Oracle Database Installation Guide for your platform for information about configuring globalization

2.8 Oracle Configuration Manager Option

During installation, you are prompted to provide information needed to enable Oracle Configuration Manager. This option enables you to associate information about your Oracle RAC configuration with your OracleMetaLink account. In the event that you need to place a service request with Oracle Support, that configuration information can help to provide a more rapid resolution to the service issue.

You can enable Oracle Configuration Manager during or after installation, or choose not to enable it. To enable it during installation, you must have the following information available:

Refer to OracleMetalink (https://metalink.oracle.com) if you encounter registration failures and are uncertain that the correct country code has been specified. You can find the country associated with your OracleMetaLink account in the Profile section under the Licenses link.

See Also:

Oracle Configuration Manager Installation and Administration Guide for further information

2.9 Database Security Options

During installation, you are prompted to select database security configuration.The Secure Configuration option configures the database with database auditing options, and password policy and expiration settings.

For new database installations, the default configuration for Oracle Database 11g release 1 (11.1) includes the Secure Configuration option. If you want to disable these enhanced security controls, then you can check the Disable security settings box. Oracle Database is then installed with default options for Oracle Database 10g release 2. After installation, you can change security settings by starting DBCA and modifying security settings. You can enable or disable auditing or password security settings, or revert to a previous security setting.

For database upgrades, the upgraded database retains your existing database security configuration, to ensure compatibility with existing applications. After installation, you can use DBCA to enable or disable the Secure Configuration auditing or password security settings for testing.

Note:

Oracle strongly recommends configuring your database with the Secure Configuration option either during installation, or after installation using DBCA.

2.10 Selecting Database Passwords

Apply the following guidelines when specifying passwords:

2.11 Actions of OUI, DBCA, and Other Assistants During Installation

After installation, OUI starts the Network Configuration Assistant (NETCA). After NETCA completes its processing, OUI runs DBCA to create your database, in accordance with Optimal Flexible Architecture (OFA) guidelines. An installation created following OFA guidelines 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 the following:

You can also use DBCA in standalone mode to create or delete a database or ASM installation, or to switch database management from Oracle Enterprise Manager Database Control to Oracle Enterprise Manager Grid Control.

Note that with Oracle Database release 11.1, service management is no longer performed for Oracle RAC databases. Use Oracle Enterprise Manager DB Control or Grid Control for all administration and monitoring of services.

See Also:

Oracle Database 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) support

In Oracle Database 10g and later releases, some database language and territory definition files have been updated to better reflect locale conventions used in associated locales.

If the resulting changes in default NLS parameter values break your existing applications, you can revert the changes by installing Oracle9i compatibility definition files. To install Oracle9i files in place of Oracle11g files, you must run OUI from a command line, as described in "Using Oracle Universal Installer to install Oracle RAC", and use the following statement to set the b_cr9idata variable to true:

runInstaller oracle.rsf.nlsrtl_rsf:b_cr9idata=true

See Also:

Oracle Database Globalization Support Guide for additional information about updates to the Oracle Database language and territory definition files

2.12 Installing Oracle Database with Other Languages

If you want to use languages other than the default (English), either for the database or for applications running on the database, then you must use the Custom Installation method.

See Also:

Oracle Database Globalization Support Guide

2.13 Selecting a Database Name

The global database name can be up to 30 characters in length, and must begin with an alphabetic character. The domain portion of the global database name can be no more than 128 characters and can contain only alphabetic and numeric characters, as well as the period (.) character.The SID prefix must begin with an alphabetic character.

2.14 Using Oracle Universal Installer to install Oracle RAC

Perform the following procedures to install the Oracle Database software with Oracle RAC:

  1. Ensure that you can access other nodes with SSH. If you are prompted for a pass phrase, then obtain it from the system administrator.

    If it is required, then the pass phrase provides credentials to set up Secure Shell (SSH). OUI requires secure shell keys to be loaded for the terminal session from which OUI runs.

  2. Open the terminal from which you intend to run OUI, log in as the oracle user (the user account that you want to own the Oracle Database software installation), and enter the following commands:

    $ exec /usr/bin/ssh-agent $SHELL
    $ /usr/bin/ssh-add
    

    If your system has been configured to require a pass phrase, then enter the pass phrase for each key when prompted.

    For example:

    [rac@node1 .ssh]$ exec /usr/bin/ssh-agent $SHELL
    [rac@node1 .ssh]$ ssh-add
    Enter passphrase for /home/crs/.ssh/id_rsa
    Identity added: /home/oracle/.ssh/id_rsa (/home/crs/.ssh/id_rsa)
    Identity added: /home/oracle/.ssh/id_dsa (/home/crs/.ssh/id_dsa)
    

    These commands start the ssh-agent on the node, and load the SSH RSA and DSA keys into memory.

  3. Ensure that you have su or sudo credentials, as you will be prompted to run a script as the root user during installation.

  4. Start the runInstaller command from the Disk1 directory of the Oracle Database 11g release 1 (11.1) installation media. When OUI displays the Welcome page, click Next.

  5. Provide information or run scripts as root when prompted by OUI. If you need assistance during installation, click Help. If you encounter problems during installation, then examine the OUI actions recorded in the installation log file. The log file is located in the Oracle Inventory directory in the following location:

    OraInventory/logs/installActionsdate_time.log
    

    Note:

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

    If you are upgrading, then you must use the same type of Oracle home. For example, you should not change from local Oracle homes to a shared Oracle home.

    The following is a list of additional information to note about installation:

    • If you are installing on Linux systems, you are using the ASM library driver (ASMLIB), and you select Automatic Storage Management (ASM) during installation, then ASM default discovery finds all disks that ASMLIB marks as ASM disks.

    • If you are installing on Linux systems, you are not using ASMLIB, and you select ASM during installation, then ASM default discovery finds all disks marked /dev/raw/* for which the oracle account has read/write permission. You can change the disk discovery string during the install if the disks you want to use for ASM are located elsewhere.

      If you are installing Oracle RAC from the Standard Edition, then you must use ASM for your database storage.

      On the Select Database Management Option page, if 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 Oracle RAC. When you use the local Database Control, you can choose the e-mail option and enter the outgoing SMTP server name and e-mail address.

      If you perform an installation that does not include Oracle Enterprise Manager (for example, a custom software install without Oracle Enterprise Manager, an installation with no Oracle Enterprise Manager configuration, or a database creation with your own scripts), then you can configure Oracle Enterprise Manager later with OUI, DBCA, or the Oracle Enterprise Manager Configuration Assistant (EMCA) utility.

When you have completed the second and final phase of the installation, proceed to Chapter 4, "Oracle Real Application Clusters Postinstallation Procedures" to perform the postinstallation tasks.

Caution:

After installation is completed and you have created the database, if you decide that you want to install additional Oracle Database 11g release 1 (11.1) products in the database, then you must stop all processes running in the Oracle home before you attempt to install the additional products. For the Oracle Universal Installer to relink certain executables and libraries, all database processes must be down. Refer to Appendix E, "How to Stop Processes in an Existing Oracle Real Application Clusters Database" for additional information.