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

B28251-06
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

4 Oracle Real Application Clusters Post-Installation Procedures

This chapter describes how to complete the post-installation tasks after you have installed Oracle Database 11g with Oracle Real Application Clusters (Oracle RAC) software. It contains the following sections:

Note:

This chapter only describes basic configurations. Refer to the Oracle Database Platform Guide for Microsoft Windows and the product administration and tuning guides for more detailed configuration and tuning information.

4.1 Required Post-Installation Tasks

You must perform the following tasks after completing your installation:

4.1.1 Back Up the Voting Disk after Installation

After your Oracle Database 11g with RAC installation is complete, and after you are sure that your system is functioning properly, make a backup of the contents of the voting disk using ocopy.exe which resides in the Oracle Database home.

Also make a backup of the voting disk contents after you complete any node additions or node deletions, and after running any deinstallation procedures.

4.1.2 Download and Install Patches

Refer to the My Oracle Support Web site for required patches for your installation. To download required patches:

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

    https://metalink.oracle.com

  2. Log in to My Oracle Support.

    Note:

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

  4. On the Select a Patch Search Area page click New My Oracle Support Patch Search.

  5. On the Simple Search page click Advanced.

  6. On the Advanced Search page click the search icon next to the Product or Product Family field.

  7. In the Search and Select: Product Family field, enter RDBMS Server in the For field and click Go.

  8. Select RDBMS Server under the Results heading and click Select.

    RDBMS Server appears in the Product or Product Family field and the current release appears in the Release field.

  9. Select your platform from the list in the Platform field and click Go.

  10. Any available patches appear under the Results heading.

  11. Click the number of the patch that you want to download.

  12. 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.

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

  14. Use the unzip utility provided with Oracle Database 11g to uncompress the Oracle patches that you downloaded from My Oracle Support. the unzip utility is located in the ORACLE_HOME\bin directory.

Note:

If you find patches for your Oracle Clusterware and for your Oracle Database, you must apply the patches for your Oracle Clusterware home before you apply the patches for your Oracle home.

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 database products or options, refer to the manual in the product documentation library which is available on the documentation media or on the OTN Web site.

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 Post-Installation Tasks

Depending on the options that you selected to install, Oracle recommends that you perform the following tasks after completing an installation:

4.2.1 Verifying Enterprise Manager Operations

Run the following command to verify the Enterprise Manager configuration in your newly installed Oracle RAC environment:

srvctl config database -d db_name

SRVCTL displays the name of the node and the instance for the node. The following example for a database named orcl shows a node named iwinrac01 running an instance named orcl1. Run the following command:

C:\> srvctl config database -d orcl 

The output should be similar to:

iwinrac01 orcl1 C:\oracle\product\11.1.0\db_1
iwinrac02 orcl2 C:\oracle\product\11.1.0\db_1

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 into Database Control from another cluster node, then you need to reconfigure 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:

    https://host:port/em

    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 mgmt42, and the Database Control uses port 1158, then use the following URL:

    https://mgmt42:1158/em
    

    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.

    Note:

    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.2.3 Postinstallation Database Configuration for Oracle Configuration Manager

Run the following script to configure the database to enable Oracle Configuration Manager (OCM) to collect configuration information:

ORACLE_BASE\ORACLE_HOME\ccr\admin\scripts\installCCRSQL.exe collectconfig -s SID -r SYSDBA-USER

The installCCRSQL.exe script 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_BASE\ORACLE_HOME\ccr\admin\scripts\installCCRSQL.exe collectconfig -s orcl

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, you will be prompted to enter the password.

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

4.2.3.1 Additional Step for E-Business Suites

If the database is used as a repository for an Oracle E-Business Suite, then you must also run the following script from the ORACLE_HOME in which the E-Business database has been hosted:

ORACLE_BASE\ORACLE_HOME\ccr\admin\scripts\installCCRSQL.exe ebs_collectconfig -u Oracle_Applications_User 

The -u parameter is mandatory. If you do not specify this parameter, then the application prompts you for the Oracle Applications User. If the -u parameter is specified, then you will be prompted for the Oracle Applications Password.

If you want to automate the install, then you can run the installCCRSQL.exe script with an additional -w option to specify the Oracle Applications Password. For example:

ORACLE_BASE\ORACLE_HOME\ccr\admin\scripts\installCCRSQL.exe ebs_collectconfig -u Oracle_Applications_User -w Oracle_Applications_Password

You can add the -s SID command to specify the SID of the Oracle Applications Database instance.

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

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

If only the -r parameter is specified, you are prompted to enter the password. The -p parameter for specifying the password is optional.

4.2.3.2 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_BASE\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.exe script to specify the SYSMAN password. For example:

ORACLE_BASE\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 the -r parameter is specified, the -p parameter is optional and will be prompted for.