4 Postinstallation Tasks

This chapter describes how to complete postinstallation tasks after you have installed the software. It includes information about the following topics:

If you install and intend to use any of the products listed in Section 4.7, "Required Product-Specific Postinstallation Tasks" then you must perform the tasks listed in the product-specific subsections.


This chapter describes basic configuration only. See Oracle Database Administrator's Reference for HP OpenVMS Itanium and the product-specific administration and tuning guides for more sophisticated configuration and tuning information.

4.1 Database Configuration Assistant

The following sections describe the procedure for starting Database Configuration Assistant:


You must use UNIX-based syntax when you specify file and path names for files such as data files, and log files. For example, the HP OpenVMS file specification DISK$ORA:[ORAR2.DATAFILES] must be expressed as the UNIX path /disk$ora/orar2/datafiles.

4.1.1 Running Database Configuration Assistant in Interactive Mode

To start Database Configuration Assistant in interactive mode, perform the following:

  1. Set up the X Window System environment by using the following DCL command:

    SET DISPLAY/CREATE/TRANSPORT=TCPIP/NODE=workstation_name or IP_address
  2. Set default to the [BIN] directory in the Oracle home directory, and then enter the following command to start DBCA:

    $ @disk:[oracle_home_directory]ORAUSER
    $ DBCA


    Click Finish to go to the last screen. This accepts the default answers to the questions on the other screens. However, if DBCA determines that the default answers to one or more screens do not apply, the DBCA will not display the last screen.

    Database Configuration Assistant graphical user interface (GUI) is displayed.

See Also:

See Appendix B, "Running Database Configuration Assistant in Noninteractive or Silent Mode" for information about running Database Configuration Assistant in noninteractive or silent mode.

4.1.2 Using Database Configuration Assistant Response Files

An alternative to creating an argument file to pass command-line options to Database Configuration Assistant is to use a response file. A sample response file (DBCA.RSP) is provided in the ORA_ROOT:[ASSISTANTS.DBCA.LOGS] directory. Make a copy of this file and customize it as necessary. Follow the instructions that are contained in comments. The value that is specified for the CREATE_TYPE field determines which of the other sections are applicable. Each field has a comment header block with the following entries: Name, Datatype, Description, Valid values, Default value, and Mandatory (Yes/No) descriptions.

For example:

# Name          : CREATE_TYPE
# Datatype      : String
# Description   : Type of database creation
# Valid values  : "createDatabase" \ "createTemplateFromDB" \ 
#                 "createCloneTemplate"
# Default value : None
# Mandatory     : Yes
CREATE_TYPE = "createDatabase"

All mandatory values must be provided, but only for the applicable sections as indicated by the CREATE_TYPE value. After customizing the response file, start Database Configuration Assistant and pass the name of the response file at the command line as follows:

$ DBCA –SILENT –RESPONSEFILE full_response_file_name


Either HP OpenVMS-based arguments or UNIX-based arguments may be used in fields that are contained within a response file, but the response file argument that is passed to the DBCA.COM script at the command line with the RESPONSEFILE keyword must be in HP OpenVMS-based syntax.

4.1.3 Database Configuration Assistant Unsupported Options

The following Database Configuration Assistant options are not supported with this release:

  • OLAP

  • UltraSearch

  • Sales History Demonstration

4.2 Required Postinstallation Tasks

You must perform the tasks described in the following sections after completing an installation:

4.2.1 Downloading and Installing Patches

Check the My Oracle Support website for required patches for the installation. To download required patches:

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


  2. Log on to My Oracle Support.


    If you are not a My Oracle Support registered user, then click Register on the home page and follow the registration instructions.
  3. On the main My Oracle Support page, click Patches & Updates.

  4. Select Product or Family (Advanced) search.

  5. Specify the following information, then click Search:

    • In the Product is field, choose RDBMS Server from the list.

    • In the Release field, choose the current release number from the list.

    • Select the Type field from the list.

    • Choose Patchset from the list.

      Selecting the Patchset option opens the Search results page. This page provides a list of patches that can be downloaded and saved. Clicking a patch enables you to choose options from the options menu on the top of the screen.

  6. Open the patch Read Me file, which you can access by clicking the Read Me icon in the options menu for each patchset, and follow the installation instructions.

    Some patches install with OUI; others require special procedures. Oracle recommends that you always read the Read Me before proceeding.

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

  8. Use an unzip utility to uncompress the Oracle patches that you downloaded from My Oracle Support.

4.2.2 Configuring Oracle Products

Many Oracle products and options must be configured before you use them for the first time. Before using individual Oracle products or options, see the appropriate manual in the product documentation library.

4.2.3 Setting the NLS_LANG Environment Variable

NLS_LANG is a logical name that specifies the locale behavior for Oracle software. This variable sets the language and territory used by the client application and the database server. It also sets the character set for the client, which is the character set for data entered or displayed by an Oracle client program, such as SQL*Plus.

See Also:

Appendix E, "Configuring Oracle Database Globalization Support" for more information about the NLS_LANG logical name

4.3 Configuring New or Upgraded Databases

Oracle recommends that you run the UTLRP.SQL script after creating or upgrading a database. This script recompiles all PL/SQL modules that may 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 time.

4.3.1 Upgrading 10.2 Databases

Each existing 10.2 Database must be upgraded before it is used with the 11.2 release. You must shutdown each database and take a complete back up before you perform an upgrade.

To associate Oracle Database 10.2 with the new 11.2 Oracle home, use ORA_ROOT:[rdbms]migrate102.com.


HP OpenVMS does not support Database Upgrade Assistant utility.

4.3.2 Running the UT LRP.SQL Script

To run the UTLRP.SQL script:

  1. Log in to the oracle Database account.

  2. Set the default to the Oracle home directory and run the following command:

    $ @ORAUSER sid 

    where sid is the database instance ID of the target database.

  3. Start SQL*Plus as follows:

  4. If necessary, start the database:

  5. Run the UTLRP.SQL script as follows:


4.4 Changing User Passwords

Oracle recommends that you change the password for system user such as SYS, SYSTEM and SYSMAN immediately after installation. To change a password:

  1. Start SQL*Plus by using the following command:

  2. Connect with the user name and password that you want to change by using the following command:

    Enter user-name: user_name
    Enter password: password
  3. Change the password by using the following command:

    PASSWORD mumble
    Changing password for mumble
    New password: password
    Retype new password: password

4.5 Performing Configuration Tasks as the SYSTEM User

You must log in to a System Administrator account to perform the following configuration task.

Automating Database Startup and Shutdown (Optional)

You can configure the system to automatically start Oracle Database when the system starts (in your SYSTARTUP procedure) and to shut down Oracle Database when the system shuts down (in your SYSHUTDWN procedure). Automating database startup is optional, but automatic shutdown is recommended because it guards against improper shutdown of the database.

4.6 Performing Configuration Tasks as Oracle User

You must log in to the Oracle Database account to set initialization parameters.

Setting Initialization Parameters

When you create a database, the INITsid.ORA parameters are automatically set. You can manually modify the initialization parameters in the initsid.ora with an HP OpenVMS editor. Activate the modified initsid.ora file by shutting down and restarting the database.

Do not use logical names in parameter files unless they are defined at an appropriate level (in other words, at a group level or the system level).

See Also:

Oracle Database Administrator's Reference for HP OpenVMS Itanium for information about INIT.ORA parameters

4.7 Required Product-Specific Postinstallation Tasks

The following sections describe postinstallation tasks that you must perform if you install and intend to use the following products:


You must perform postinstallation tasks only for the products that you intend to use.

4.7.1 Configuring Oracle Net Services

If you have a previous release of Oracle software installed on this system, you may want to copy information from the Oracle Net Services TNSNAMES.ORA and LISTENER.ORA configuration files from the previous release to the corresponding files for the new release.These files should have a record format of stream_lf. If you copy a TNSNAMES.ORA or a LISTENER.ORA file from an earlier version, use the following command to convert the files:

 CARRIAGE_CONTROL carriage_return
 FORMAT stream_LF ^Z


The default location for the TNSNAMES.ORA and LISTENER.ORA files is the ORA_ROOT:[NETWORK.ADMIN] directory.

Modifying the listener.ora File

If you are upgrading from a previous release of Oracle Database, Oracle recommends that you use the current release of Oracle Net Services listener instead of the listener from the previous release.

To use the listener from the current release, you may need to copy static service information from the LISTENER.ORA file from the previous release to the version of that file used by the new release.

Modifying the tnsnames.ora File

Unless you use a central TNSNAMES.ORA file, copy Oracle Net Services service names and connect descriptors from the previous release TNSNAMES.ORA file to the version of that file used by the new release.

If necessary, you can also add connection information for additional database instances to the new file.

4.7.2 Configuring Oracle Label Security

If you install Oracle Label Security, you must configure it in a database before you use it. You can configure Oracle Label Security in two ways, with or without Oracle Internet Directory integration. If you configure Oracle Label Security without Oracle Internet Directory integration, you cannot configure it to use Oracle Internet Directory at a later stage.


To configure Oracle Label Security with Oracle Internet Directory integration, Oracle Internet Directory must be installed in the environment and Oracle Database must be registered in the directory.

See Also:

See Oracle Label Security Administrator's Guide for more information about Oracle Label Security enabled with Oracle Internet Directory.

4.7.3 Installing Oracle Text Supplied Knowledge Bases

An Oracle Text knowledge base is a hierarchical tree of concepts used for theme indexing, ABOUT queries, and deriving themes for document services. If you plan to use any of these Oracle Text features, you can install two supplied knowledge bases (English and French) from the Oracle Database 11g Release 2 (11.2) installation media.


You can extend the supplied knowledge bases depending on your requirements. Alternatively, you can create knowledge bases, possibly in languages other than English and French. See Oracle Text Reference for more information about creating and extending knowledge bases.

4.7.4 Configuring Oracle Messaging Gateway

To configure Oracle Messaging Gateway, refer to the section about Messaging Gateway in Oracle Streams Advanced Queuing User's Guide. When following the instructions listed in that manual, refer to this section for additional instructions about configuring the LISTENER.ORA, TNSNAMES.ORA, and MGW.ORA files.

Modifying the LISTENER.ORA File for External Procedures

To modify the ORACLE_HOME:[NETWORK.ADMIN]LISTENER.ORA file for external procedures:

  1. Back up the LISTENER.ORA file.

  2. Ensure that the default IPC protocol address for external procedures is set as follows:

  3. Add static service information for a service called mgwextproc by adding the following lines to the SID_LIST parameter for the listener in the LISTENER.ORA file:

      (SID_DESC =
        (SID_NAME = mgwextproc)
        (ORACLE_HOME = oracle_home)
        (PROGRAM = extproc)

    For example, set the SID_LIST parameter as follows:

      (SID_LIST =
        (SID_DESC =
          (SID_NAME = PLSExtProc)
          (ORACLE_HOME = somedisk:[oracle.product.11_2_0.db_1])
          (PROGRAM = extproc)
        (SID_DESC =
          (SID_NAME = mgwextproc)
            (ORACLE_HOME = somedisk:[oracle.product.11_2_0.db_1])
            (PROGRAM = extproc)

    In this example:

    • ORACLE_HOME is the path of the Oracle home directory.

    • extproc is the external procedure agent executable file.

Modifying the TNSNAMES.ORA File for External Procedures

To modify the ORACLE_HOME:[NETWORK.ADMIN]TNSNAMES.ORA file for external procedures:

  1. Back up the TNSNAMES.ORA file.

  2. In the TNSNAMES.ORA file, add a connect descriptor with the net service name MGW_AGENT as follows:

    MGW_AGENT = 
       (CONNECT_DATA= (SID=mgwextproc) (PRESENTATION=RO)))

    In this example:

    • The value specified for the KEY parameter must match the value specified for that parameter in the IPC protocol address in the LISTENER.ORA file.

    • The value of the SID parameter must match the service name in the LISTENER.ORA file that you specified for the Oracle Messaging Gateway external procedure agent in the previous section (mgwextproc).

Setting Up the MGW.ORA Initialization File

To modify the ORA_ROOT:[MGW.ADMIN]MGW.ORA file for external procedures, define the CLASSPATH logical name. A sample MGW.ORA file can be found in the ORA_ROOT:[MGW.ADMIN]SAMPLE_MGW.ORA directory.

You must include the classes in Table 4-1 and any additional classes required for Oracle Messaging Gateway to access non-Oracle messaging systems, such as WebSphere MQ or TIBCO Rendezvous classes.

Table 4-1 Classes for CLASSPATH Logical Name

Classes Path

Oracle Messaging Gateway


JRE run time


Oracle JDBC


Oracle internationalization





JMS Interface


Oracle JMS implementation


Java Transaction API


4.7.5 Oracle Precompilers

The following sections describe references and configuration files that are associated with Oracle precompilers.


For the Pro*C/C++ precompiler, the configuration file is ORA_ROOT:[PRECOMP.ADMIN]PCSCFG.CFGS. This file installs without content. Use any text editor to customize it to the site requirements. For more information about configuring the pcscfg.cfg file, see Pro*C/C++ Programmer's Guide.


For the Pro*COBOL precompiler, the configuration file is PCBCFG.CFG. This file installs without content. Use any text editor to customize it to the site requirements. For more information about configuring the pcbcfg.cfg file, see Pro*COBOL Programmer's Guide.


For the Pro*FORTRAN precompiler, the configuration file is PCCFOR.CFG. This file installs without content. Use any text editor to customize it to the site requirements. For more information about configuring the pccfor.cfg file, see Pro*FORTRAN Supplement to the Oracle Precompilers Guide.