4 Oracle Real Application Clusters Postinstallation Procedures

This chapter describes how to complete the postinstallation tasks after you have installed the Oracle Database 12c Release 1 (12.1) with Oracle Real Application Clusters (Oracle RAC) software. This chapter contains the following topics:

Note:

This chapter describes only basic configurations. See also:

4.1 Required Postinstallation Tasks

Perform the following tasks after completing your installation:

4.1.1 Determine If Any Patches Are Required For Your New Software

If you did not choose to download software options during installation, then after installing Oracle RAC, verify if there are any patches needed for your system. To determine if any patches are required for your system, review the Oracle Database Readme and the Oracle Database Release Notes for Microsoft Windows.

4.1.2 Configuring 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 does not receive any of those connection requests and the clients making those connection requests report errors.

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

4.1.3 Creating the OraMTS Service for Microsoft Transaction Server

Oracle Services for Microsoft Transaction Server (OraMTS) permit Oracle databases to be used as resource managers in Microsoft application coordinated transactions. OraMTS acts as a proxy for the Oracle database to the Microsoft Distributed Transaction Coordinator (MSDTC). As a result, OraMTS provides client-side connection pooling and allows client components that leverage Oracle to participate in promotable and distributed transactions. In addition, OraMTS can operate with Oracle databases running on any operating system, given that the services themselves are run on Windows.

On releases earlier than Oracle Database 12c, the OraMTS service was created as part of a software-only installation. Starting with Oracle Database 12c, you must use a configuration tool to create this service.

To create the OraMTS service after performing a software-only installation of Oracle RAC or after adding a node to an existing cluster, perform the following steps:

  1. Open a command window.

  2. Change directories to %ORACLE_HOME%\bin.

  3. Run the OraMTSCtl utility to create the OraMTS Service, where host_name is a list of nodes on which the service should be created:

    C:\..bin> oramtsctl.exe -new -host host_name
    

See Also:

Oracle Services for Microsoft Transaction Server Developer's Guide for Microsoft Windows for more information about OraMTS, which allows Oracle databases to be used as resource managers in distributed transactions.

4.1.4 Configuring Oracle Products

Many Oracle products and options must be configured before you use them for the first time. Before using individual Oracle Database 12c Release 1 (12.1) products or options, refer to the appropriate manual in the product documentation library, which is available on the Oracle Technology Network (OTN) website at:

http://docs.oracle.com

Refer to these sections for information about configuring various products and features after installation:

4.1.4.1 Configuring Oracle Database Vault

OUI installs Oracle Database Vault by default when you install the Oracle RAC software, but you must register Oracle Database Vault with the Oracle RAC database and create database user accounts before you can use it. You must create the Database Vault Owner user and, optionally, the Database Vault Account Manager administrative user accounts.

4.1.4.2 Configuring Oracle Database Security Settings

To enable or disable the database security configuration after installation, you must use command-line Oracle Database Configuration Assistant (DBCA) options. By design, the DBCA graphical 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 either 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 Microsoft Windows for more information about enabling and disabling the database security option

4.1.4.3 Configuring Oracle Label Security

After installation, you must configure Oracle Label Security in a database before you use it. You can configure Oracle Label Security in two ways: with Oracle Internet Directory integration and without Oracle Internet Directory integration.

Configuration Requirements
With Oracle Internet Directory integration To configure Oracle Label Security with Oracle Internet Directory integration, Oracle Internet Directory must be installed in your environment and the Oracle database must be registered in the directory.
Without Oracle Internet Directory integration If you configure Oracle Label Security (OLS) without Oracle Internet Directory integration, then you cannot configure it to use Oracle Internet Directory at a later stage. To configure Oracle Label Security with Oracle Internet Directory on your database at a later time, you must remove the OLS option on the database and configure the OLS with Oracle Internet Directory integration option.

See Also:

Oracle Label Security Administrator's Guide for information about configuring Oracle Label Security

4.1.4.4 Configuring the OraClrAgnt Service for Oracle Database Extensions for .NET

Oracle Database Extentions (ODE) for .NET depends on a Windows service to operate properly. This service is called the OraClrAgnt service.

In earlier versions of Oracle Database, this CLR service was created automatically by the installer. Starting with Oracle Database 12c, after installation you use the OracleClrCtl.exe utility to create, start, stop, and delete the OraClrAgnt service. When you use the OraClrCtl.exe utility to create the service, a new service is created named OracleHomenameClrAgent, where Homename represents an Oracle Home name. The OraClrAgnt service is configured by this tool using the Oracle Home User account specified during the Oracle Database installation..

See Also:

Oracle Database Extensions for .NET Developer's Guide for Microsoft Windows for more information about the OraClrCtl.exe tool and installing and configuring the OraClrAgnt service

4.1.4.5 Configuring Oracle XML DB

Oracle XML DB is a required component of the Oracle Database installation. However, you must manually configure the FTP and HTTP ports for Oracle XML DB.

See Also:

Oracle XML DB Developer's Guide for information on configuring the FTP and HTTP protocols for Oracle XML DB

4.1.5 Recompile All PL/SQL Modules

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. Run the utlrp.sql script immediately following installation, not at a later date.

  1. (Optional) Complete setting up the Oracle Installation User environment, as described in Section 4.2.1, "Setting the Oracle User Environment Variables."

  2. Log in as an Administrator user, or as the Oracle Home user.

  3. Start SQL*Plus, as follows:

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

    Login as a SYSDBA user.

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

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

4.1.6 Configuring 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), or a supported network file system (NFS) using the Direct NFS Client.

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 the directory contents are consistent on each node. To avoid unpredictable results, you must ensure that the same file is accessed from all nodes, or that the same file is used on all nodes.

See Also:

Oracle Grid Infrastructure Installation Guide for more information about configuring storage

4.2 Recommended Postinstallation Tasks

Oracle recommends that you complete the following tasks after completing an Oracle RAC installation:

4.2.1 Setting the Oracle User Environment Variables

Unlike on other platforms, you should not set ORACLE_HOME as a fixed environment variable when running Oracle Database on Windows operating systems. This is because the Oracle software determines where executable files reside at run time.

When you invoke an Oracle executable program on Windows, for example sqlplus.exe, the ORACLE_HOME, ORACLE_BASE, and ORACLE_SID variables are determined by the PATH environment variable and the location of the executable program (which Oracle home it resides in). To use SQL*Plus to manage a different database or Oracle ASM instance, click the Windows Start button, select the correct Oracle Home for the instance you want to manage, and then select the SQL*Plus utility.

You can use Oracle Universal Installer (OUI) to specify an Oracle home as the default Oracle home and update the PATH environment variable to point to that Oracle home. Refer to Section 6.5, "Working with Multiple Oracle Home Directories on Windows" for detailed instructions on how to change the default Oracle home.

4.2.2 Setting Up User Accounts

You can set up additional user accounts to manage your database. For information about setting up additional optional user accounts, see Oracle Database Platform Guide for Microsoft Windows and Oracle Database Security Guide.

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 3.0 of MMC is available with Windows Server 2008 and later. Oracle recommends that you use the latest version of MMC that is available.

4.3 Configuring the Oracle Home User

Under certain circumstances you may have to perform additional configuration steps for the Oracle Home user, such as:

  • Creating an OCR wallet for Oracle Home user

  • Changing the password for the Oracle Home user

See the Oracle Database Platform Guide for Microsoft Windows for details on performing these tasks.

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, the account is locked because login privileges are no longer required.

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

The script installCCRSQL.exe creates an Oracle Configuration Manager user and loads the PL/SQL procedure into the database defined by the ORACLE_SID environment variable. 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:

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

Note:

  • If you specify the user name without specifying the password (with the -p paramter), then the script prompts you to enter the password.

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

4.5 Enabling and Disabling Database Options After Installation

When you install Oracle Database, some 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

To enable or disable a particular database feature for an Oracle home, shut down the database and 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

Table 4-1 describes the possible values for db_option:

Table 4-1 Database Options for Chopt Tool Command

Value Description

dm

Oracle Data Mining Database Files

olap

Oracle OLAP

partitioning

Oracle Partitioning

rat

Oracle Real Application Testing

ode_net

Oracle Database Extensions for .NET


Before you run the chopt tool, shut down any Oracle databases running from the Oracle home being modified.

Example 4-1 How to Enable the Oracle Label Security Database Option Using Chopt

In this example, the chopt tool enables Oracle Label Security in the database oradb1:

  1. Shut down the Oracle RAC database, and any other databases running out of the Oracle home directory, using the Server Control Utility (SRVCTL).

    srvctl stop database -db oradb1
    
  2. Change directories to the Oracle_home\bin directory:

  3. Run the chopt tool, as follows:

    chopt enable lbac
    
  4. Use SRVCTL to restart the databases you stopped in Step 1, for example:

    srvctl start database -db oradb1