Skip Headers
Oracle® Real Application Clusters Installation Guide
11g Release 2 (11.2) for Microsoft Windows

Part Number E10818-02
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Index
Index
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
View PDF

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 2 (11.2) with Oracle Real Application Clusters (Oracle RAC) software. It also describes how to use the chopt tool to enable or disable database features.

This chapter contains the following topics:

Note:

This chapter describes only basic configurations. Refer to:

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 My Oracle Support Web site for required patch updates for your installation.

Note:

Browsers require an Adobe Flash plug-in, version 9.0.115 or higher to use My Oracle Support. Check your browser for the correct version of Flash plug-in by going to the Adobe Flash checker page, and installing the latest version of Adobe Flash.

If you do not have Flash installed, then download the latest version of the Flash Player from the Adobe web site:

http://www.adobe.com/go/getflashplayer

To download required patch updates:

  1. Use a Web browser to view the My Oracle Support Web site:

    https://support.oracle.com

  2. Log in to My Oracle Support.

    Note:

    If you are not a My Oracle Support registered user, then click Register for My Oracle Support and register.
  3. On the main My Oracle Support page, click the Patches & Updates tab.

  4. In the Patch Search section, click Product or Family (Advanced Search).

  5. Specify the following information, then click Search:

    • In the Product action list, expand the entry for Oracle Database and then select your release, for example, Oracle 11.2.0.1.0. You can select multiple releases, or click Close.

    • In the Release action list, choose Oracle Database and specify the current release number.

    • If the last action list shows Platform, then use the action list to the right to specify your operating system, for example Microsoft Windows, 64-bit and Microsoft Windows Server 2003 R2. After making your choices, click Close.

    • On the right-hand side of the Patch Search section, above the Search button, click the + button to add a new filter.

    • In the new action list, change the selection to Type. In the action list to the right, select either Patch or Patchset, or both, then click Close.

  6. In the Patch Search Results list, if a patch set is available for the specified release and platform, then it is listed here.

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

  7. Click the number of the patch set in the first column of the Patch Search Results. On the right-hand side of the patch set information page, click View Read Me to view the Patch Set Notes, or the README file, for that patch. The README page contains information about the patch set and how to apply the patches to your installation.

  8. To download the patch to your local file system, click the Download button on the patch set information page.

  9. Use the unzip utility provided with Oracle Database 11g release 2 (11.2) to uncompress the Oracle patch updates that you downloaded from My Oracle Support. The unzip utility is located in the Oracle_home\bin directory.

4.1.2 Configure Exceptions for the Windows Firewall

If the Windows Firewall feature is enabled on one or more of the nodes in your cluster, then virtually all TCP network ports are blocked to incoming connections. As a result, any Oracle product that listens for incoming connections on a TCP port will not receive any of those connection requests and the clients making those connections will report errors.

If the Windows Firewall feature is enabled on one or more nodes of your Oracle RAC cluster, you must create exceptions for Oracle RAC applications and ports as described in Oracle Grid Infrastructure Installation Guide for Microsoft Windows.

4.1.3 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 2 (11.2) 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.1 Configuring Oracle Database Vault

If you installed Oracle Database Vault during Oracle RAC installation, then you need to register Oracle Database Vault with the database and create database user accounts.

See Also:

Oracle Database Vault Administrator's Guide for more information about configuring Oracle Database Vault after installation

4.1.3.2 Configuring Oracle Database Security Settings

To enable or disable the database security configuration after installation, you must use command line DBCA options. By design, the DBCA graphic user interface (GUI) does not have the option to enable or disable secure configuration. For example, to enable the security settings after installation, you would use a command of the following form, where myRACdb1.example.com is the name of the local database instance, or the DB_UNIQUE_NAME:

dbca –configureDatabase –sourceDB myRACdb1.example.com -SID
–enableSecurityConfiguration true

See Also:

Oracle Database Installation Guide for your platform for more information about enabling and disabling the database security option

4.1.4 Configure Storage for External Tables, Shared Files, or Directory Objects

If your Oracle RAC database uses files that are external to the database, then the external files should be located on shared storage that is accessible to all nodes. Each node should use the same mount point to access the file. Acceptable shared file systems include Database File System (DBFS), Oracle ASM Cluster File System (Oracle ACFS), Oracle Cluster File System (OCFS) for Windows, or a supported network file system (NFS).

The database Directory Object used to write and read files external to the database must point to a shared storage location, and each node must use the same mount point for the same shared storage location. For example, each node might have a Directory Object called DPUMP for the mount point C:\app\acfsmounts\dpump, which accesses Oracle ACFS shared storage.

Note:

There is no checking of the contents of the external files or directory object specified as part of the external table to ensure that they are consistent on each node. To avoid unpredictable results, you must make sure the same file is accessed from all nodes, or make sure the same file is used on all nodes.

4.2 Recommended Postinstallation Tasks

Oracle recommends that you complete the following tasks after installing Oracle RAC:

4.2.1 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 immediately following installation, not at a later date.

  1. Start SQL*Plus, as follows:

    Click Start, select Programs (or All Programs), then Oracle - HOME_NAME, then Application Development, and then SQL*Plus.

  2. Run the utlrp.sql script, where Oracle_home is the Oracle home path:

    SQL> @Oracle_home\rdbms\admin\utlrp.sql
    

See Also:

Oracle Database Administrator's Guide for information about connecting to the database using SQL*Plus

4.2.2 Set Up User Accounts

For information about setting up additional optional user accounts, refer to Oracle Database Platform Guide for Microsoft Windows.

When you complete these procedures, you are ready to perform the initial configuration tasks described in Chapter 5, " Configuring Server Parameter Files in Oracle RAC".

4.2.3 Configuring Oracle Administration Assistant for Windows

Oracle Administration Assistant for Windows requires the Microsoft Management Console and HTML Help 1.2 or later to run. Microsoft Management Console (MMC) version 2.0 of MMC ships with Windows Server 2003; version 3.0 of MMC is available with Windows Server 2003 R2, Windows Server 2008 and Windows Server 2008 R2. Oracle recommends the latest MMC version available.

See Also:

Microsoft documentation at:
http://www.microsoft.com/

4.2.4 Using Oracle9i Language and Definition Files with Oracle Database 11g

You can use Oracle9i database language and territory definition files with Oracle Database 11g release 2 (11.2). To enable this functionality:

  1. Run the cr9idata.pl script, by default located in Oracle_home\nls\data\old.

    Alternatively, before you install Oracle Database, you can run the Oracle Universal Installer setup command with the b_cr9idata variable set to true, as follows:

    setup.exe oracle.rsf.nlsrtl_rsf:b_cr9idata=true
    
  2. Set the ORA_NLS10 environment variable to point to the directory where you installed the new language and territory definition files, which by default are in Oracle_home\nls\data.

  3. Restart the Oracle database.

4.3 Enabling and Disabling Database Options

When you install Oracle Database, by default certain options are enabled and others are disabled. You can view the enabled Oracle Database options by querying the V$OPTION view using SQL*Plus.

See Also:

Oracle Database Administrator's Guide for information about connecting to the database using SQL*Plus

If you need to enable or disable a particular database feature for an Oracle home, then use the chopt tool. The chopt tool is a command-line utility that is located in the Oracle_home\bin directory. The syntax for chopt is as follows:

chopt [ enable | disable] db_option

The possible values for db_option are described in the following table.

Value Description
dm Oracle Data Mining RDBMS Files
dv Oracle Database Vault
lbac Oracle Label Security
olap Oracle OLAP
partitioning Oracle Partitioning
rat Oracle Real Application Testing
ode_net_2 Oracle Database Extensions for .NET 2.0

Before you run the chopt tool, you should shutdown any Oracle databases running from the Oracle home being modified. For example, to enable the Oracle Label Security option in your Oracle binary files, perform the following tasks:

  1. Shutdown the Oracle RAC database, and any other databases running out of the Oracle home directory, using SRVCTL.

    srvctl stop database -d myRACdb
    
  2. Use the Windows Services console to stop the service for each Oracle database that runs from the Oracle home being modified.

    For example, if your Oracle RAC database is named myRACdb, then on the first node of the cluster you would stop the OracleServiceMYRACDB1 service.

  3. Change directories to the Oracle_home\bin directory.

    cd %ORACLE_HOME%
    
  4. Run the chopt tool, as follows:

    chopt enable lbac
    
  5. Use the Windows Services console to restart the services you stopped in Step 2.

  6. Use SRVCTL to restart the databases you stopped in Step 1, for example:

    srvctl start database -d myRACdb
    

4.4 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.exe collectconfig -s SID -r \
SYSDBA-USER

The script installCCRSQL.exe 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.exe 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.

By default, the connection to the database is through operating system authentication, "/as sysdba." To specify a different user and password, you can use these options:

-r SYSDBA-USER: The login name for the user with a SYSDBA role

-p SYSDBA-PASSWORD: The password for the user with a SYSDBA role

Note:

  • If you specify the user without specifying the password, then you will be prompted to enter the password.

  • If you specify only the password without specifying the user name, then the user SYS is used by default.

4.4.1 Additional Step for Oracle Enterprise Manager Grid Control

If the database is used as a repository for Oracle Enterprise Manager Grid Control, then you must also run the following script:

Oracle_home\ccr\admin\scripts\installCCRSQL.exe collectemrep

When you run this command, the application prompts you for the SYSMAN password. If you want to automate the install, then you can run the installCCRSQL script to specify the SYSMAN password. For example:

Oracle_home\ccr\admin\scripts\installCCRSQL.exe collectemrep -e SYSMAN PASSWORD

You can add the -s SID command to specify the SID of the Oracle Enterprise Manager Grid Control Database instance. You must run this script from the Oracle_home in which the Oracle Enterprise Manager Grid Control database has been hosted.

If you are not using operating system authentication to connect to the database, then you must use the -r and -p parameters to specify the following:

-r SYSDBA-USER: The login name of the SYSDBA user

-p SYSDBA-PASSWORD: The password for the SYSDBA user

If you do not specify the -p parameter, then you are prompted to enter the password for the specified user.