4 Oracle Real Application Clusters Postinstallation Procedures

This chapter describes how to complete the postinstallation tasks after you have installed the Oracle Database 11g release 1 (11.1) with Oracle Real Application Clusters (Oracle RAC) software.

This chapter contains the following topics:


This chapter describes only basic configurations. Refer to Oracle Database 11g Administrator’s Guide for UNIX Systems, and the product administration and tuning guides for more detailed configuration and tuning information. Refer also to Oracle Database Installation Guide for your platform, for additional postinstallation configuration information.

4.1 Required Postinstallation Tasks

You must perform the following tasks after completing your installation:

4.1.1 Download and Install Patch Updates

Refer to the OracleMetaLink Web site for required patch updates for your installation. To download required patch updates:

  1. Use a Web browser to view the OracleMetaLink Web site:


  2. Log in to OracleMetaLink.


    If you are not an OracleMetaLink registered user, then click Register for MetaLink and register.
  3. On the main OracleMetaLink page, click Patches & Updates.

  4. In the Patches section, click Simple Search.

  5. Specify the following information, then click Go:

    • In the Search By field, select Product or Family, and then specify RDBMS Server.

    • In the Release field, specify the current release number.

    • In the Patch Type field, specify Patchset/Minipack.

    • In the Platform or Language field, select your platform.

  6. In the Results list, find the latest patch set for Oracle Database.

    Patch sets for Oracle databases are identified in the Description column as Patchset x.x.x.x PATCH SET FOR ORACLE DATABASE SERVER.

  7. In the Patch column, click the number of the patch that you want to download.

  8. On the Patch Set page, click View README and read the page that appears. The README page contains information about the patch set and how to apply the patches to your installation.

  9. Return to the Patch Set page, click Download, and save the file on your system.

  10. Use the unzip utility provided with Oracle Database 11g release 1 (11.1) to uncompress the Oracle patch updates that you downloaded from OracleMetaLink. The unzip utility is located in the $ORACLE_HOME/bin directory.

4.1.2 Configure Oracle Products

Many Oracle products and options must be configured before you use them for the first time. Before using individual Oracle Database 11g release 1 (11.1) database products or options, refer to the manual in the product documentation library which is available in the DOC directory on the Oracle Database installation media, or on the OTN Web site.

4.1.3 Relocate Instance-related Memory-mapped files from OCFS2 Using Symbolic Links

If you install Oracle RAC on a standard local file system, then this section does not concern you.

If your Oracle Clusterware installation is created on OCFS2, then you must relocate the healthcheck files (hc_*.dat), that typically reside in $ORACLE_HOME/dbs, to a local file system, and create symbolic links to it from the original path. This is required as OCFS2 version 1.2 for Linux does not support shared writable mmap access that the Oracle software uses to manipulate these files.

To relocate the files:

  1. Stop the Oracle Database instance.

  2. Move the $ORACLE_HOME/dbs/hc_*.dat files to a directory on a local file system.

  3. Create symbolic links from the $ORACLE_HOME/dbs directory to the hc_*.dat files on the local file system.

  4. Restart the Oracle Database instance

4.2 Recommended Postinstallation Tasks

This section explains the tasks that Oracle recommends you perform after completing an installation.

4.2.1 Recommended Database Postinstallation Tasks

Oracle recommends that you complete the following tasks after installing Oracle RAC: Back Up the root.sh Script

Oracle recommends that you back up the root.sh script after you complete an installation. If you install other products in the same Oracle home directory, then the Oracle Universal Installer (OUI) updates the contents of the existing root.sh script during the installation. If you require information contained in the original root.sh script, then you can recover it from the root.sh file copy. Set the Oracle User Environment Variables

On each node, in the oracle user profile file, set the environment variables ORACLE_BASE and ORACLE_HOME, and ORACLE_SID; also add ORACLE_HOME/bin to the path file.

For example:

export ORACLE_BASE=/u01/app/oracle
export ORACLE_HOME=/u01/app/oracle/11.1.0/db_1
export ORACLE_SID=sales1

If the environment variables ORACLE_HOME and ORACLE_SID are not set, and you try to use SQL*Plus or other tools, then you receive an error message requesting that you set these variables. Recompile all PL/SQL modules

Oracle recommends that you run the utlrp.sql script after creating or upgrading a database. This script recompiles all PL/SQL modules that might be in an invalid state, including packages, procedures, and types. This is an optional step but Oracle recommends that you do it during installation and not at a later date.

  1. Complete setting up the oracle user environment, as described in "Set the Oracle User Environment Variables" in the preceding section.

  2. Start SQL*Plus, as follows:

    $ sqlplus "/ AS SYSDBA"
  3. Run the utlrp.sql script:

    SQL> @?/rdbms/admin/utlrp.sql Set Up User Accounts

For information about setting up additional optional user accounts, refer to Oracle Database 11g Administrator’s Guide for UNIX Systems.

When you complete these procedures, you are ready to perform the initial configuration tasks described in Chapter 6, " Configuring the Server Parameter File in Oracle Real Application Clusters Environments".

4.2.2 Logging in to Oracle Enterprise Manager Database Control

If you configure Oracle Enterprise Manager Database Control during installation, then you can use it to manage your database. Alternatively, you can use Oracle Enterprise Manager Grid Control to manage your database.

To use Database Control, you must access it on the node where you installed the database. If you want to log in to Database Control from another cluster node, then you need to reconfigure Oracle Enterprise Manager to start the Database Control interface on that other node.

See Also:

the emca command line help for instructions to perform reconfiguration

Use the following instructions to log in to Database Control:

  1. On the node from which you installed the database, open a Web browser to access the Database Control URL, and use the following URL syntax:


    In the preceding example:

    • host is the name of the computer on which you installed Oracle Database

    • port is the port number reserved for the Database Control or Grid Control during installation

    If you do not know the correct port number to use, then look for the following line in the file $ORACLE_HOME/install/portlist.ini, which lists the assigned port:

    Enterprise Manager Console HTTP Port (db_name) = 1158

    The installation reserves the first available port from the range 5500 to 5519.

    For example, if you install Oracle Database on host example, and the Database Control uses port 1158, then use the following URL:


    Oracle Enterprise Manager displays the Database Control login page.

  2. Log in to the database using the user name SYS and connect as SYSDBA.

    Use the password that you specified for the SYS account during the installation.


    You can also log in to the Database Control using the SYSTEM or SYSMAN accounts, or you can grant login privileges to other database users.

4.3 Oracle Configuration Manager Postinstallation Configuration for Oracle RAC

If you have installed Oracle Configuration Manager, then you must run a script to create a database account to collect database configuration collections. You must create this account in both Connected and Disconnected modes. The database account stores the PL/SQL procedures that collect the configuration information, and the account owns the database management system (DBMS) job that performs the collection. After the account has been set up, as login privileges are no longer required, the account is locked.

To configure the database for configuration collection, run the following script:

$ORACLE_HOME/ccr/admin/scripts/installCCRSQL.sh collectconfig -s SID -r\ 

The script installCCRSQL.sh creates an Oracle Configuration Manager user and loads the PL/SQL procedure into the database defined by the ORACLE_SID. You can also specify the database SID by using the -s option in the command line, as in the following example, where the SID is orcl:

$ORACLE_HOME/ccr/admin/scripts/installCCRSQL.sh collectconfig -s orcl

For Oracle RAC, you must run the database script against only one instance, such as the local instance on which you performed installation. However, Oracle Configuration Manager must be installed in all instance homes.

See Also:

Oracle Configuration Manager Installation and Administration Guide for further information

4.4 Oracle Database Vault Postinstallation with DVCA for Oracle RAC

After installing Oracle Database Vault for an Oracle RAC instance, you need to run Oracle Database Vault Configuration Assistant (DVCA) with the -action optionrac switch on all other Oracle RAC nodes. This sets instance parameters and disables SYSDBA operating system authentication.

You need to run this command on all Oracle RAC nodes other than the node on which the Oracle Database Vault installation is performed. This step is required to enable the enhanced security features provided by Oracle Database Vault.


The listener and database instance should be running on the nodes on which you run DVCA.

Use the following syntax to run DVCA:

# dvca -action optionrac -racnode host_name -oh oracle_home 
-jdbc_str jdbc_connection_string -sys_passwd sys_password 
[-logfile ./dvca.log] [-silent] [-nodecrypt] [-lockout]


  • action is the action to perform. optionrac performs the action of updating the instance parameters for the Oracle RAC instance. This flag also provides the option of disabling SYSDBA operating system access for the instance.

  • raccnode is the host name of the Oracle RAC node on which the action is being performed. Do not include the domain name with the host name.

  • oh is the Oracle home for the Oracle RAC instance.

  • jdbc_connection_string is the JDBC connection string used to connect to the database. For example: jdbc:oracle:oci:@orcl1.

  • sys_password is the password for the SYS user.

  • logfile is an optional flag to specify a log file name and location. You can enter an absolute path, or enter a path that is relative to the location of the $ORACLE_HOME/bin directory.

  • silent is the option to run in command line mode. This option is required if you are not running DVCA in an xterm window.

  • nodecrypt is the option to read plaintext passwords as passed on the command line.

  • lockout is the flag to use to disable SYSDBA operating system authentication.


You can re-enable SYSDBA access by recreating the password file with the nosysdba flag set to n (No). The orapwd utility enables you to do this.

4.5 Upgrading Databases with Oracle Database Vault to Oracle Database 11g

If you have an existing Oracle Database 10g release 2 installation ( with Oracle Database Vault, then you must disable Oracle Database Vault before you can upgrade to Oracle Database 11g release 1 (11.1).


If you have Oracle Database 10g release with Oracle Database Vault, then you must upgrade to release before upgrading to Oracle Database 11g.

To disable Oracle Database Vault, complete the following procedure:

  1. Stop all processes (Listener, Oracle Enterprise Manager, and Oracle Database), as described in Appendix E.

  2. Change directory to the Oracle Database rdbms/lib directory. For example:

    $ cd $ORACLE_HOME/rdbms/lib
  3. Enter the following command:

    $ make -f ins_rdbms.mk dv_off
  4. Change directory to the Oracle home bin directory, and relink Oracle Database. For example:

    $ cd $ORACLE_HOME/bin
    $ relink oracle
  5. Restart all processes (Listener, Oracle Enterprise Manager, and Oracle Database).

  6. If you are upgrading an Oracle RAC database, then repeat steps 1 through 5 on each member node of the RAC Database on the cluster.

  7. On the local node, enter the following command syntax, where Oracle_home is the Oracle Database home, Database_name is the name of the database, Sys_password is the SYS password for the database, DV_owner is the user account that owns Oracle Database Vault, DV_owner_passwd is the Oracle Database Vault owner password, DV_acct_manager is the user account of the Oracle Database Vault account manager, and DV_acct_passwd is the password of the Oracle Database Vault account manager:

    dvca -action disable -oh Oracle_home -service Database_name -sys_passwd Sys_password -owner_account DV_owner -owner_passwd DV_owner_passwd -acctmgr_account DV_acct_manager -acctmgr_passwd DV_acctmanager_passwd -logfile ./dvca.log -nodecrypt

    For example:

    $ dvca -action disable -oh /u01/app/oracle/10.2.0/db_1 -service sales
    -sys_passwd mySyspw -owner_account DVowner -owner_passwd myDVownerpw
    -acctmgr_account DVacctmgr -acctmgr_passwd myDVmgrpw -logfile ./dvca.log
  8. Install Oracle Database 11g, using a custom Oracle RAC software only installation with Oracle Label Security and Oracle Database Vault. Repeat steps 2 through step 4 in the Oracle Database 11g home.


    You do not need to start or stop processes in a software-only installation home
  9. From the Oracle Database 11g release 1 (11.1) Oracle home, start DBUA to upgrade the Oracle Database

  10. On all nodes, enable Oracle Database Vault in the Oracle Database 11g release 1 (11.1) Oracle home.

    $ cd $ORACLE_HOME/rdbms/lib
    $ make -f ins_rdbms.mk dv_on
    $ cd $ORACLE_HOME/bin
    $ relink oracle

    Restart all processes after relinking is completed.