2 Preinstallation Tasks

This chapter describes the tasks that you must complete before you start Oracle Universal Installer. It includes information about the following tasks:

2.1 Checking Hardware Requirements


Oracle Database 11g Release 2 (11.2) must be installed on an ODS-5 formatted disk. See Section 1.2, "Changes and Enhancements" for more information.

The following sections list the minimum hardware requirements for installing Oracle Database products on an HP OpenVMS system:

2.1.1 Minimum Hardware Requirements

The following are the minimum hardware requirements for installing Oracle Database 11g Release 2 (11.2):


A minimum of 2 GB RAM is required to install Oracle Database products. However, Oracle Corporation suggests having at least 4 GB RAM. Oracle Database Client products require 1 GB RAM. Also, consider the associated applications used on your system when calculating RAM.

To determine the amount of RAM installed on the system and the amount of paging currently configured on the system, enter the following command:


To review memory reservations on the node, run the following command:

System Memory Resources on 13-JUL-2002 09:57:11.72 

Memory Reservations (pages):   Group   Reserved  In Use  Type
ORA_PROD_SGA                   SYSGBL  5120      0       Allocated
ORA_PROD_SGA                   SYSGBL  5         0       Page Table
Total (40.04 Mbytes reserved)          5125      0

See Also:

Chip Set

All HP OpenVMS Itanium chip sets are supported.

DVD Drive

This product is available for download and an optional DVD disk is provided upon request. Please ensure that you have a DVD drive that is supported by HP OpenVMS. Oracle uses ODS-5 format installation media.

2.1.2 Images

Oracle Database Enterprise Edition is installed with three default images, namely, LIBCLNTSH.SO, ORACLE.EXE, and ORA_JAVA_VMS_SHR.EXE.

LIBCLNTSH.SO is linked with Oracle Database Client images, reduces their size by removing direct references to Oracle Net Services and other common routines. ORACLE.EXE is the Oracle server image and will not be present in a Client-only installation. ORA_JAVA_VMS_SHR.EXE is the Oracle Java VM shared image.

In addition, HP OpenVMS 11g Release 2 (11.2) has the following four shareable images used by the server: LIBCORENLS11.SO, LIBORASHR11.SO, LIBSKGXN2.SO, and LIBSKGXP11.SO.

2.1.3 Disk Space Requirements

Oracle Universal Installer enables you to select an installation category and type. Your choices determine how much disk space is required. The disk space requirements do not include the size of the database. A production Oracle Database that supports many users requires significant disk space and memory.

Table 2-1 Disk Space Requirements for Oracle Database Server

Installation Type Required Disk Space

Enterprise Edition

10 GB

Standard Edition

10 GB


Depends on the components selected, but a minimum of 5 GB

Staging area (copying dvd contents to disk)

5 GB

2.1.4 Oracle Advanced Security

Oracle Advanced Security is an add-on product that is added to the standard Oracle Net Services Server or Oracle Net Services Client. If you purchase it, then install it on both the server and the client.

The SSL version compatibility is SSL3.0 or later.Kerberos and Secure Sockets Layer (SSL) have requirements for authentication protocols that are supported by Oracle Advanced Security. No additional authentication protocol software is required to relink Oracle products. The requirements for Kerberos and SSL are as follows:

  • Kerberos

    Requires MIT Kerberos version 5 Release 1.1. The Kerberos authentication server must be installed on a physically secure system.

  • SSL

    Requires a wallet that is compatible with the Oracle Wallet Manager version 11.2. Wallets that were created by using earlier releases of the Oracle Wallet Manager are not upward-compatible. Oracle Advanced Security provides and installs SSL.

See Also:

For more information about Oracle Advanced Security and system management products, see Oracle Database Advanced Security Administrator's Guide


No additional authentication protocol software is required to relink Oracle products. However, Oracle does not provide third-party authentication servers (for example, Kerberos). The appropriate authentication server for these protocols must be installed and configured separately.

SSL is provided and is always installed with Oracle Advanced Security.

2.2 Checking Software Requirements

This section provides information about checking the software requirements.

Checking for Required Software

Depending on the products that you intend to install, verify that the following software is installed on the system. The procedure following the table describes how to check these requirements.

Item Requirement
Operating system HP OpenVMS Itanium versions 8.4 and 8.4-1H1
Oracle Universal Installer X Window and X/Motif software:
Oracle Messaging Gateways Download the SupportPac MA88 from


Pro*C/C++, Oracle XML Developer's Kit (XDK)
  • HP C 7.3-289
  • HP C++ 7.4-004

Oracle Net Services Requirements Oracle Net Services on HP OpenVMS is developed and certified using TCP/IP Services for HP OpenVMS (UCX).

If you want to use the TCP/IP protocol adapter for Oracle Net Services, then install version 5.7 ECO 4 or later of TCP/IP Services on HP OpenVMS Itanium.

Caution: TCP/IP protocol stacks from other vendors may work with Oracle, but this is not guaranteed by Oracle. Any TCP/IP problems that cannot be reproduced using TCP/IP Services for HP OpenVMS should be referred to the TCP/IP vendor.

Vendor-provided protocol services are usually upward-compatible, so existing applications continue to work without modification. Therefore, later releases of TCP/IP are upward-compatible with Oracle Net Services, if the vendor-specified application programming interface (API) does not change with new releases.

Oracle JDBC/OCI Drivers You can use HP JDK 1.5.0 version with the Oracle JDBC/OCI drivers.

However, they are not required for the installation.

Note: HP JDK version 1.5.0 is installed as part of a standard Oracle software installation. HP JDK version 1.6.0 is supported if it is installed with the operating system.

Pro*COBOL HP COBOL 3.0-0002
Pro*FORTRAN HP FORTRAN 8.2-104939-50H96

To ensure that the system meets these requirements:

  1. To determine which version of HP OpenVMS is installed, enter the following command:


    If necessary, see the operating system documentation for information about upgrading the operating system.

  2. To display additional information about the operating system, enter the following command:


    To view information about all nodes in a cluster, add the /CLUSTER qualifier to this command.

  3. If you intend to use Oracle Messaging Gateway and require MQSeries classes for Java and MQSeries classes for Java Message Service (SupportPac MA88), download it from the following IBM Web page:


  4. If you require a Corrective Services Deliverable (CSD) for MQSeries, refer to the following website for download and installation information:


  5. To determine the version of TCP/IP installed, enter the following command:

    $ tcpip show version
    HP TCP/IP Services for OpenVMS Industry Standard 64
    Version V5.7 - ECO 4
    on an HP BL860c i2 (1.33GHz/4.0MB) running OpenVMS V8.4

Oracle Net Services HP OpenVMS Mailbox Driver

The Oracle Net Services HP OpenVMS Mailbox driver (protocol IPC) is included in NETWORK. You do not need an Oracle Net Services license to use the HP OpenVMS Mailbox driver.

Checking for Required Patches

You must ensure that the patches described in the following table are installed on the system.

Installation Type or Product Minimum Requirement
All installations The following patches, or their later versions, are required:
All installations
  • VMS84I_UPDATE V8.0

  • VMS84I_IPC V1.0

  • VMS84I_LAN V3.0

  • VMS84I_PCSI V4.0

  • VMS84I_RMS V4

IBM Messaging Gateway IBM AXPVMS MQ CLIENT V5.30
Oracle Messaging Gateway Corrective service diskette (CSD) for MQSeries:

CSD09 or later for MQSeries V5.3


In some cases, later patch sets would cumulatively include earlier patches and therefore, the preceding command would not explicitly indicate the required patch sets. In such cases, check the Patch Distribution website of Hewlett-Packard for the contents of the patches that are displayed to verify if the required patches are included or not.

To check if you have the required patches installed on the system, enter the following command:


The output of this command is a list of all software patches or products (or both) that are installed on the system. Verify that you meet the minimum requirements to install and run Oracle Database.

In addition to this document, see My Oracle Support Document 2000927.1 and Index of install related notes for Oracle Database 11g Release 2 (11.2) on HP OpenVMS, for an updated list of the following:

  • Required patches

  • ECO level check scripts

  • Preinstallation check scripts

  • Quota check scripts

My Oracle Support is available at


2.3 Installation-Specific Issues and Restrictions

The following factors can affect the installation or use of Oracle Database:

2.3.1 New Oracle Home

Do not install Oracle Database into the root directory of an existing Oracle installation containing any Oracle Software. Oracle recommends that you install Oracle Database products into a new Oracle Home.

Logical Names

Oracle Database 11g Release 2 (11.2) has two separate logical names that specify the top-level directory of the installation. ORA_ROOT is a concealed logical name used in earlier releases, and ORACLE_HOME is a nonconcealed logical name. You can use both logical names with the following restriction:

If the top-level directory is DISK$DISK1:[ORACLE11204], then the logical names are defined as follows:


Therefore, the following command is invalid:


The following commands are valid:


2.3.2 JDK

The JDK release that is shipped with Oracle Database is used by Oracle Java applications such as Oracle Universal Installer and is the only JDK that is supported to run with these applications. You must not modify this JDK, unless it is done through a patch provided by Oracle Support Services.

2.3.3 Devices

With Oracle 11g Release 2 (11.2), all file systems must reside on ODS-5 (On-Disk Structure Level 5) formatted disks. This includes the installation location, login directory, database files, and redo log files. This is required for mixed case file name support.

Oracle Database server must be able to verify that files have been written to disk. Devices that do not support this verification are not supported for use with Oracle Databases, although Oracle software can be installed on them. Datafiles always must reside on volumes with write through cache enabled.


Because of this requirement for verification, third-party software that creates one or more virtual disks in memory must not be used for data files.

2.4 Creating a User Account

This section provides installation procedure requirements. It discusses the following topics:

2.4.1 Creating an Oracle Database DBA Account

Create an HP OpenVMS user account to administer and maintain the Oracle installation. Setting up an Oracle Database account is the same as setting up any other HP OpenVMS user account.

To set up an Oracle Database account:

  1. Determine the values that you want to enter to create the account.

  2. Run the AUTHORIZE utility to add a record in the User Authorization File (UAF).

  3. Use AUTHORIZE to set the following account requirements:

    • Account quotas

    • Account privileges

    • Process rights identifiers

  4. Exit AUTHORIZE to complete the account setup.

    See Also:

    The Hewlett-Packard documentation for more information about running the AUTHORIZE utility

Determining Account Information

To add an account, you must enter the following information:

  • User name

  • User password

  • USER and GROUP numbers for the UIC (octal values)

  • Login device and directory

  • Owner

Although this guide refers to this account as the Oracle Database account or Oracle account, you can assign any name or number to the account after taking into account UIC restrictions. The Oracle Database account owns the run-time libraries and executable images for every Oracle product. Therefore, the database administrator (DBA) must manage this account and install all Oracle products from it.


In Oracle Database Administrator's Guide, the Oracle Database account is sometimes referred to as the DBA account. The Oracle Database account is not the same as the SYS or SYSTEM database user names that are created for every database. It is an HP OpenVMS account name.

The UIC group number of the Oracle Database account must be greater than the system parameter MAXSYSGROUP (which defaults to octal 10). Group numbers 1 through the value of MAXSYSGROUP are reserved for use by the HP OpenVMS operating system.If the UIC group number is not greater than the value of MAXSYSGROUP, then all Oracle Database account commands are not supported. For example:




The following command gives the value of MAXSYSGROUP (in decimal format):


2.4.2 Adding a Record in the User Authorization File

Use the AUTHORIZE utility to create or modify records in the UAF as follows:

  1. To run the AUTHORIZE utility, enter the following commands:

  2. At the UAF prompt, enter the ADD command to create the user account from which you install the product software:


In this example, the account name is ORACLE11G. Ensure that the UIC group number is 277. The UIC group number must be greater than MAXSYSGROUP.

After adding the account, you must alter the account privileges and quotas. This can be done in any order. However, in most cases, the account privileges are set before the account quotas.

See Also:

The Hewlett-Packard documentation for more information about using the AUTHORIZE utility

2.4.3 Setting Account Privileges

The following privileges are required as both authorized and default privileges for the Oracle Database DBA account:





  • LOG_IO


  • OPER











Use the AUTHORIZE utility to set the account privileges for the Oracle Database DBA account. At the UAF prompt, use the MODIFY command to add the required default and authorized privileges as follows:


2.4.4 Setting Account Quotas

Use the AUTHORIZE utility to change account quotas to meet the requirements of Oracle Database installation.

Account Quotas

Table 2-2 lists the Oracle Database account quotas, their minimum recommended values, and their equivalent HP OpenVMS quota names as displayed by the SHOW PROCESS/QUOTA and SHOW WORKING_SET DCL commands.


These quotas depend on the number of log files, databases, network connections, and other logicals on the system. You may need to customize these values.

Table 2-2 Oracle Database Account Quotas

Account Quota Minimum Value Quota Name


250 (the default)

Asynchronous system trap limit



Buffered I/O limit


2000 (the default)

Enqueue quota



Open file quota



Job table quota


0 (the default)

Max detached processes


0 (the default)

Max active jobs


2 million (recommended)

Paging file quota



Subprocess quota



Working set default



Working set extent



Working set quota

Modifying the Default Quotas

After adding a record with the default quotas, use the MODIFY command to alter the default values. The following example changes the enqueue quota (ENQLM) from the default value to a value of 150:


2.4.5 Process Rights for Database Administrators

The Oracle Database DBA account must be granted one or more process rights identifiers. These identifiers enable you to run the CONNECT /AS SYSDBA command that is required to perform database administration functions. Table 2-3 displays the combinations of adding and granting rights identifiers to this account:

Table 2-3 Adding and Granting Process Rights Identifiers

Adding... And Granting... Enables Control of...



Any database instance, provided it does not also have an ORA_sid_DBA identifier defined for it.



Database instance sid only



All database instances except sid

For example, to grant the ORA_sid_DBA rights identifier to the Oracle Database account for an instance called TEST, enter the following command:


Then, grant the rights identifier to the Oracle Database account as follows:


If you add the ORA_TEST_DBA rights identifier, but grant only ORA_DBA to the ORACLE11G account, then the account would have insufficient privileges to administer the TEST instance.

The third row of the table shows that you can add and grant different identifiers, which restricts control of a particular instance while it grants control to other instances.

You can also grant database maintenance privileges to accounts (for example, privileges to start and shut down the database) other than the Oracle Database account. However, with the Oracle Database account, the user UIC group number must be greater than MAXSYSGROUP. By granting the ORA_sid_DBA identifier, you can similarly restrict user privileges to an instance named sid.

2.4.6 Process Rights for SGA Protection

The SGA is protected by an access control list (ACL) that grants access to the identifier ORA_SGA. Before you start a database, add this rights identifier to the UAF, if it does not exist. To do this, the system manager must enter the following command:



Do not grant the ORA_SGA rights identifier to any user. Oracle software manages the assignment of the rights identifier when it starts the database.

2.4.7 Security Issues with Multiple Databases

If a site has several databases managed by different DBAs, then you may not want to grant the CMKRNL privilege to every DBA Oracle Database account. This privilege enables a DBA to activate any process rights identifiers and to install shared images.

For security reasons, Oracle recommends that the HP OpenVMS system administrator handle these tasks. This person should be responsible for starting Oracle Database instances from a controlled account with a UIC group number that is greater than the value of MAXSYSGROUP. If this is not possible, then at least one Oracle Database account must have the CMKRNL privilege.

2.4.8 Completing Account Setup

Exit the AUTHORIZE utility. If the user account that you modified is logged on at the time you exit this utility, then this user must log out and log in again before the changes take effect.

2.4.9 Verifying Privileges

Enter the following command to verify that your account has the correct privileges and rights identifiers:


2.4.10 Setting Permissions for File Creation

Set default file protections for the ORACLE11G account to ensure that GROUP and WORLD have READ and EXECUTE permissions, but not WRITE permission on installed files.

  1. Enter the $ SHOW PROTECTION command to check the current setting.

  2. If the $ SHOW PROTECTION command does not show the expected protection, then set protection in the LOGIN.COM of the ORACLE11G account as follows:

    $ SET PROTECTION=(s:RWE, o:RWED, g:RE, w:RE)/default

2.5 SYSGEN Parameters

See Also:

READMEVMS.DOC in the RDBMS directory for instructions on calculating MIN_GBLPAGES, and MIN_GBLSECTIONS

You can create and use reserved memory on an HP OpenVMS system. The following sections describe the utilities that you can use to set the values of the various SYSGEN parameters:

2.5.1 Reserved Memory Registry

Through its interface within the SYSMAN utility, the reserved memory registry enables you to configure an HP OpenVMS system with large amounts of memory set aside for use within memory-resident global sections. The AUTOGEN utility considers the preallocated reserved memory when it tunes the system.

Oracle recommends that you do not use reserved memory until the instance SGA size is stable. In most cases, this is a few weeks after the database is performing well.

The advantages to reserving memory for an SGA are as follows:

  • You can be certain that the memory is available and that the system is correctly tuned.

  • The memory is reserved at startup time as contiguous aligned physical pages. This enables the system to optimize the mapping of the SGA.

  • The memory is preallocated and zeroed. This results in faster SGA mapping and faster instance startup.

To reserve memory for an SGA, use the SYSMAN utility. The size qualifier is specified in megabytes. For example, to reserve memory for a 6 GB SGA for the SID named TEST, use the following commands:


Next, run AUTOGEN and restart the system to allow AUTOGEN to adjust other system parameters for the reduced amount of memory that is available to the rest of the system.

Memory for multiple SGAs may be reserved. Any change to the name or size of a piece of reserved memory may require restarting the system. During instance startup, Oracle Database compares the size of the reserved memory, if any, with the size of the SGA. If appropriate, one of the following messages is included in the alert log:

** Reserved memory size = size greater than created SGA size = size**
** Please reduce reserved memory size to avoid wasting memory. **

** Memory was not reserved for the SGA. SGA size = size **
** There might be performance advantages to allocating memory for
    the SGA in the VMS reserved memory registry. **

If the memory reserved for an SGA is insufficient, then the instance startup fails. In this case, you must adjust the amount of reserved memory, run AUTOGEN, and restart the system. For example, to expand the SGA to 6.5 GB for the TEST instance, enter the following commands:


Next, run AUTOGEN and save it permanently using the SAVEPARAMS parameter. This saves the change in the AGEN$FEEDBACK.DAT file.

If you do not want to save permanently then, instead of running AUTOGEN, use SYSMAN to free the memory reservation and proceed with starting the Oracle instance without reserved memory. The risk involved with this is that the system may not have enough fluid pages to create the SGA. In addition, the performance advantages of using reserved memory are not available.

See Also:

The Hewlett-Packard documentation for more information about the reserved memory registry

To review memory reservations on the node, run the following command:


System Memory Resources on 13-JUL-2001 09:57:11.72 
Memory Reservations (Pages)    Group    Reserved   In Use   Type
ORA_PROD_SGA                   SYSGBL   5120       0        Allocated
ORA_PROD_SGA                   SYSGBL   5          0        Page Table
Total (40.04 Mbytes reserved)           5120       0


Because SYSGEN parameters affect the entire operating system, the system administrator is the only person who should modify them. At some sites, the DBA and system administrator may be the same person. The instructions in this section are directed to the system administrator.

For setting or modifying SYSGEN parameters, HP OpenVMS provides the AUTOGEN utility. You can also use SYSGEN, but this is an older utility and its use is discouraged, except perhaps for checking current values. You must have the SYSPRV or BYPASS privilege to run these utilities.

AUTOGEN provides a permanent method for setting parameters, and it documents all changes. AUTOGEN also lets you recalculate any parameters that depend on other parameters that you may have changed. Remember to record parameter values before changing them, and determine in advance what results you expect from the changes you make. If the expected changes do not occur, then restore the old values before trying again.

The procedure is as follows:

  1. Run the AUTOGEN utility with the SAVPARAMS parameter by entering the following command:


    This step saves current parameters to a file named AGEN$FEEDBACK.DAT.

  2. If you have not already done so, run AUTOGEN GETDATA to ensure that the file PARAMS.DAT has been generated.

  3. Examine the parameter settings in the current PARAMS.DAT, and if they are correct, then change them in the MODPARAMS.DAT file by using the MIN_parameter=value format as follows:


    The MIN prefix indicates that you are setting a lower limit for the specified parameter. To use the MIN prefix, identify the current value of the specified parameter (using SYSGEN) and the amount by which you want to increase the parameter. The sum of these two values is used for the MIN_parameter entry.

  4. Run the AUTOGEN utility with the GENPARAMS and REBOOT parameters by entering the following command:



    The REBOOT parameter in this example causes the system to automatically restart when the SYSGEN is complete.

    This step generates new SYSGEN parameters in a file named SETPARAMS.DAT and runs the SYSGEN utility to set these parameter values as specified in the file.

    See Also:

    HP OpenVMS System Management Utilities Reference for more information about using the AUTOGEN utility

2.6 System Configuration

If the system fails to satisfy any listed requirement, then perform the tasks listed in the next section as necessary to configure the system to meet these requirements.

Table 2-4 lists the requirements for installing Oracle Database.

Table 2-4 HP OpenVMS System Configuration Summary

System Factors Requirements for Oracle Database

HP OpenVMS Parameters:

Minimum Global Pages or Sections

Verify that the values for MIN_GBLPAGES and MIN_GBLSECTIONS are greater than, or equal to, the values that were calculated for these parameters, as documented in READMEVMS.DOC.

HP OpenVMS Accounts

You need an HP OpenVMS account that is dedicated solely to installing and upgrading Oracle products. The instructions in this book are provided with the assumption that the account is called ORACLE11G.

Permissions for File Creation

Default Protections

2.7 Performing Setup Tasks As the SYSTEM User

Log in as the SYSTEM user and perform the following tasks to set up the environment for Oracle Database:

2.7.1 Creating an Oracle Database Account

The Oracle Database account is the HP OpenVMS user account that owns Oracle Database software after installation. Run Oracle Universal Installer with this user account.

Details of creating this account are covered in Section 2.4, "Creating a User Account"

Use the AUTHORIZE utility to create an oracle account with the properties listed in Table 2-5.

Table 2-5 Properties of the Oracle Database Account

Account Properties

Login Name

Any name, but this document refers to it as the Oracle Database installation owner. For example, ORACLE11G.


The group UIC number, which must be greater than MAXSYSGROUP.

Home Directory

Select a login directory consistent with other users' login directories. The login directory of the ORACLE11G account should not be used as the ORA_ROOT/ORACLE_HOME directory.


Use the Oracle Database account only for installing, maintaining and managing Oracle software. Do not use it for purposes unrelated to Oracle Database server. Do not use SYSTEM as the ORACLE11G account.

Sites with multiple ORA_ROOT directories on one system may install Oracle software with the same ORACLE11G account, or separate accounts. Each ORACLE11G account must have the same group UIC.

2.7.2 Creating an Apache Server Account

The Apache account is an HP OpenVMS user account that owns the Apache server after installation. If you use a default Apache configuration (one that listens to ports lower than 1024, which are reserved for the system), then Oracle recommends, for security reasons, that a separate account owner be set up for Apache. Configure the Apache server to assign the ownership of listener and module actions to this account. It is not necessary for the Apache user account to have privileges to run the Apache Server on port numbers that are lower than 1023. Images that are installed with privileges during installation in the oracle account ensure that this can be done.

See Section G.3.3, "Customizing the Server Environment" for information about how to configure the server to run as a user other than the 'oracle' user.

The Apache account owner should have minimal user privileges, and should not be a member of any groups where files are not intended to be visible to the public.

2.8 Performing Setup Tasks As the oracle user

Log in to the oracle Database account and perform the following tasks as necessary:

2.8.1 Setting the Display

Before starting Oracle Universal Installer, set the display by using the following command:

$ SET DISPLAY/CREATE/TRANSPORT=TCPIP/NODE=workstation_name or IP_address

Verify that you have set the display correctly by using the following command:


Do not use the host name or IP address of the system where you install the software unless you perform the installation from the X Window console of that system. Use the computer name or IP address of the workstation if you are installing from a remote system. If you are not sure of the X server and screen settings, then use 0 (zero) for both.

2.8.2 Setting Up a Batch Queue for the Oracle Enterprise Manager Agent and HAS

In this release, the architecture and implementation of the Oracle Enterprise Manager Agent has undergone a major revision. The new agent is based on an HTTP listener that communicates with the Management Server using XML and that uses Perl to perform a number of tasks. This has been implemented to run in a batch queue instead of running as detached processes. The Oracle Enterprise Manager Agent runs a main process. To support monitoring of both internal (using the same Oracle home) and external databases and listeners, the Enterprise Manager Agent submits additional batch jobs.

From the operational and management perspective, this has been implemented to run under a batch queue to get a better collective view of all processes related to the Enterprise Manager Agent running at any given time. This makes it easy to monitor and control all processes spawned by the Enterprise Manager Agent. In addition, it may be possible to delete batch jobs or processes that can potentially fail when trying to connect to databases or listeners that are not running.


Although the Enterprise Manager Agent is no longer installed as part of a database installation, it is available as part of the separate Enterprise Manager Grid Control release.

For High-Availability Services (HAS), OCSSD, EVMD, and CRSD, are collectively run as batch process. The Enterprise Manager Agent and HAS use the following method to determine the name of the batch queue on which to submit jobs:

  • If the ORA_BATCH_QUEUE_hostname logical name is defined, then the value of this logical is used.

  • If the ORA_BATCH_QUEUE_hostname logical is itself a valid queue name, then it is used.

The ORA_BATCH_QUEUE_hostname logical name need not always be defined. It is sufficient that it is defined at least once during installation. Alternatively, you can define it before running ORAUSER.COM at any time after the installation. Ensure that the Enterprise Manager Agent and HAS services can only be started up after setting up this batch queue logical name and running ORAUSER.COM.

The two components record the batch queue name in the installation, and use that as a reference for subsequent calls to the services. The default batch queue SYS$BATCH generally points to a batch queue that runs under a lower priority (usually, 2) than the priority of a normal user (usually, 4). Therefore, it is inappropriate to use the default queue for the two services. This would result in poor and, in some cases, defective performance of the two services.


Oracle recommends to use a dedicated batch queue.

The number of jobs submitted for the Enterprise Manager Agent batch queue depends on the number of monitoring targets which include databases and listeners. An approximation of two to five monitoring targets would be a good number for the job_limit. In the case of HAS, a job_limit of about 10 would be sufficient. The batch queue priority should be the same as all other Oracle processes, which is typically 4 on a standard VMS system.

2.9 Setup Tasks for Oracle Products

The following products require preinstallation steps to be completed before you install Oracle Database software:

2.9.1 Precompilers and Tools

The following sections list the preinstallation tasks for the precompilers and tools that are required for HP OpenVMS.

2.9.2 Network and System Management Products

This section describes tasks that need to be completed prior to installation if you have existing network and system management products. Setup Tasks for Oracle Net Services

If you have an existing installation of Oracle Net Services running on the same TCP ports, then shut down all listeners before installing it. To determine if the TCP port is in use, enter the following command:


If the port is in use, a device name will be displayed. Issue the following command:

$ SHOW DEVICE/FULL device_name

The output of this command will contain a process ID. Issue the following command:


The full path to the program that is running and which is using the port will be indicated in this display. This path includes the Oracle home from which you should stop the Listener.

2.10 Identifying Required Software Directories

You must identify three directories for the Oracle software as described in the following sections:

The following subsections describe the requirements for these directories.

2.10.1 Oracle Inventory Directory

The Oracle inventory directory (ORAINVENTORY) stores an inventory of all Oracle software installed on the system. It is required by, and shared by, all Oracle software installations on a single system.

The Installer creates this directory if it does not exist and sets the correct owner, group, and permissions on it.


Oracle recommends that you specify the inventory location by creating the oraInst.loc file in the sys$login:[node_name] directory. Create this directory if it does not exist. The contents of the oraInst.loc file is as follows:

VMS1 is the UIC group of the account used to install Oracle. All Oracle software installations depend on this directory. Ensure that you back it up regularly. Do not delete this directory unless you have completely removed all Oracle software from the system.

2.10.2 Oracle Base Directory

The Oracle base directory is a top-level directory for Oracle software installations. On HP OpenVMS, a typical Oracle base directory is similar to the following example:


2.10.3 Oracle Home Directory

The Oracle home directory is the directory where you choose to install the software for a particular Oracle product. You must install different Oracle products, or different releases of the same Oracle product, in separate Oracle home directories. When you run Oracle Universal Installer, it prompts you to specify the path to this directory, and a name that identifies it.

Oracle Universal Installer creates the directory path that you specify. It also sets the correct ownership and permissions. You do not need to create this directory.

Oracle Universal Installer can use either one of the following format examples:

  • OpenVMS format:

  • UNIX format:


2.11 Guidelines for Placing Oracle Recovery Files


You must select a location for the recovery files only if you enable automated backups during the installation.

Use the following guidelines to place Oracle Database or recovery files:

  • To prevent disk failure from making both the database files and the recovery files unavailable, place the recovery files on a different physical disk from the database files.

  • The disk that you select must have at least 2 GB of free space.

    The disk space requirement is the default disk quota configured for the flash recovery area. The default disk quota is specified by the DB_RECOVERY_FILE_DEST_SIZE initialization parameter. If you select the Custom installation type, then you can specify a different disk quota value. After you create the database, you can also use Oracle Enterprise Manager Grid Control to specify a different value.

    See Also:

    Oracle Database Backup and Recovery Basics for more information about sizing the flash recovery area
  • The Oracle Database account must have write protection to create the files in the specified path.

2.12 Creating Directories for Oracle Database or Recovery Files

Use the following guidelines when deciding the location of Oracle Database or recovery files:

  • You can choose either a single device or more than one device to store the database files depending on the following criteria:

    • If you want to use a single device, then choose a device on a physical device that is dedicated to the database.

      For performance and reliability, choose a redundant array of independent disks (RAID) device or a logical volume on more than one physical device and implement the stripe-and-mirror-everything (SAME) methodology.

    • If you want to use more than one device, then choose devices that are dedicated to the database.

      This method enables you to distribute physical I/O and create separate control files on different devices for increased reliability. You must choose either the Advanced database creation option or the Custom installation type during the installation to implement this method.

  • If you intend to create a preconfigured database during the installation, the device (or devices) that you choose must have at least 1.2 GB of free disk space.

    For production databases, you must estimate the disk space requirement depending on the use you want to make of the database.

  • For optimum performance, the devices that you choose should be used only by the database.

  • The Oracle Database account must have write permissions to create the files in the path that you specify.

Creating Required Directories


You must complete this procedure only if you want to place Oracle Database or recovery files on a separate device instead of placing them in the Oracle base directory.

To create directories for Oracle Database or the recovery files on separate devices:

  1. Use the SHOW DEVICE device_name command to determine the free disk space on each mounted device.

  2. From the display, identify the devices to use. Table 2-6 lists the device requirements for recovery files.

    Table 2-6 Device Requirements for Recovery files

    File Type Device Requirements

    Data files

    Choose either:

    • A single device with at least 1.2 GB of free disk space

    • Two or more devices with at least 1.2 GB of free disk space in total

    Recovery files

    Choose a device with at least 2 GB of free disk space.

    If you are using the same device for more than one type of file, then add the disk space requirements for each type to determine the total disk space requirement.

  3. Note the names of the root device directories for the devices that you identified.

2.13 Stopping Existing Oracle Processes


If you are installing additional Oracle Database 11g Release 2 (11.2) products in an existing Oracle home, then stop all processes running in the Oracle home. You must complete this task to enable Oracle Universal Installer to relink certain executables and libraries.

If you choose to create a database during the installation, then most installation types configure and start a default Oracle Net Services listener using TCP/IP port 1521 and the IPC key value EXTPROC. However, if an existing Oracle Net Services listener process uses the same port or key value, Oracle Universal Installer can only configure the new listener, but it cannot start it. To ensure that the new listener process starts during the installation, you must shut down any existing listeners before starting Oracle Universal Installer.

To determine if an existing listener process is running, and to shut it down if necessary:

  1. Log in as the Oracle Database account user.

  2. Enter the following command:

    $ PIPE SHOW SYSTEM/OWN=ORACLE | SEARCH SYS$INPUT last_8_chars_of_listener_name

    This command displays the Oracle processes that are running in the oracle account. Run the following command to identify the Oracle processes that run as listener processes:


    For each process that is running as a listener process, run the following command to determine the Oracle home in which it is running:

    $ SHOW PROCESS/CONTINUOUS process_name

    In this example, process_name is the name of the listener process that is indicated by the command that you just entered.


    If no Oracle Net Services listeners are running, then refer to Section 2.14, "Configuring Oracle User's Environment" to continue.
  3. Set up the Oracle environment for the Oracle home area where the listener is running as follows:

    $ SET DEFAULT Oracle_home_dir
    $ @ORAUSER
  4. Enter the following command to identify the TCP/IP port number and IPC key value that the listener is using:

    LSNRCTL STATUS listenername


    If the listener uses the default name LISTENER, you do not have to specify the listener name in this command.
  5. If the TCP/IP port number determined in the preceding step is 1521, or the IPC key value is EXTPROC, then enter a command similar to the following:

    LSNRCTL STOP listenername
  6. Repeat this procedure to stop all listeners running on this system.

See Also:

2.14 Configuring Oracle User's Environment

Before you start Oracle Universal Installer, you must configure the Oracle Database installation owner environment.

To achieve this, perform the following steps:

  1. Start a new terminal session.

  2. Set up the display using the SET DISPLAY command.

  3. Set up the inventory directory, and create the ORAINST.LOC file. This step is optional but recommended. If you do not create the inventory directory, then an ORAINST.LOC file is created under the sys$login:node_name directory. The default inventory location is the directory INVENTORY_node_name created as the top-level directory of ORACLE_HOME.

  4. Define the logical name ORA_BATCH_QUEUE_nodename to point to an existing batch queue. Oracle recommends that you use a dedicated Batch Queue.

    See Also:

    Appendix C, "Installing, Configuring, and Running Enterprise Manager Agent" for more information about batch queues
  5. Create a file, CLUSTER_NODES.DAT (if you are installing Oracle Clusterware), in the SYS$LOGIN directory with the list of nodes that are to comprise the Oracle RAC cluster. This file displays each node on a separate line with the primary node listed first.

  6. Enter the $ SET NOVERIFY command.

  7. Enter the $ SET PROCESS/PRIV=ALL command.

  8. To start the RUNINSTALLER refer to Section 3.3, "Installing Oracle Database Software"

2.15 The ORATAB File

The ORATAB file contains information about all Oracle installations and databases installed on the node. This information is used to discover Oracle product installations. When an Oracle product is installed, this file is updated with information about the new Oracle home. If this file is not found, then a new ORATAB file is created.

To check if the ORATAB file exists:

  1. Check for the ORATAB file in the hostname subdirectory of SYS$LOGIN. For example:

  2. If the ORATAB file is not found at the location described in Step 1, then use the file in the SYS$LOGIN directory. For example:

  3. If the ORATAB file is not found in any of the locations mentioned in the previous steps, then it means there is no ORATAB file.