4 Postinstallation Tasks

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

You must perform the tasks listed in the "Required Postinstallation Tasks" section. Oracle recommends that you perform the tasks listed in the "Recommended Postinstallation Tasks" section after all installations.

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


This chapter describes basic configuration only. Refer to Oracle Database Administrator's Reference for UNIX-Based Operating Systems and product-specific administration and tuning guides for more detailed configuration and tuning information.

Required Postinstallation Tasks

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

Downloading and Installing Patches

Check the OracleMetaLink Web site for required patches for the installation.

To download required patches:

  1. Use a Web browser to view the OracleMetaLink Web site:

  2. Log in to OracleMetaLink.


    If you are not an OracleMetaLink registered user, then click Register for MetaLink! and follow the registration instructions.
  3. On the main OracleMetaLink page, click Patches.

  4. Select Simple Search.

  5. Specify the following information, then click Go:

    • In the Search By field, choose Product or Family, then specify RDBMS Server.

    • In the Release field, specify the current release number.

    • In the Patch Type field, specify Patchset/Minipack.

    • In the Platform or Language field, select your platform.

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, refer to the appropriate manual in the product documentation library.

Recommended Postinstallation Tasks

Oracle recommends that you perform the tasks described in the following section after completing an installation:

Creating a Backup of the root.sh Script

Oracle recommends that you back up the root.sh script after you complete an installation. If you install other products in the same Oracle home directory, then Oracle Universal Installer updates the contents of the existing root.sh script during the installation. If you require information contained in the original root.sh script, then you can recover it from the backed up root.sh file.

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 might 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 date.

To run the utlrp.sql script, follow these steps:

  1. Switch user to oracle.

  2. Use the oraenv or coraenv script to set the environment for the database where you want to run the utlrp.sql script:

    • For Bourne, Bash, or Korn shell:

      $ . /usr/local/bin/oraenv
    • For C shell:

      % source /usr/local/bin/coraenv

    When prompted, specify the SID for the database.

  3. Start SQL*Plus, as follows:

    $ sqlplus "/ AS SYSDBA"
  4. If necessary, start the database:

  5. Run the utlrp.sql script:

    SQL> @?/rdbms/admin/utlrp.sql

Setting Up User Accounts

For information about setting up additional user accounts, refer to Oracle Database Administrator's Reference for UNIX-Based Operating Systems.

Setting the NLS_LANG Environment Variable

NLS_LANG is an environment variable 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 environment variable

Generating the Client Static Library

The client static library (libclntst10.a) is not generated during installation. If you want to link your applications to the client static library, then you must first generate it as follows:

  1. Switch user to oracle.

  2. Set the ORACLE_HOME environment variable to specify the Oracle home directory used by the Oracle Database installation. For example:

    • For Bourne, Bash, or Korn shell:

      $ ORACLE_HOME=/u01/app/oracle/product/10.2.0/db_1 
      $ export ORACLE_HOME
    • For C shell:

      % setenv ORACLE_HOME /u01/app/oracle/product/10.2.0/db_1
  3. Enter the following command:

    $ $ORACLE_HOME/bin/genclntst

Required Product-Specific Postinstallation Tasks

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


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

Configuring Oracle Net Services

If you have a previous release of Oracle software installed on this system, then you can copy information from the Oracle Net tnsnames.ora and listener.ora configuration files from the previous release to the corresponding files for the new release.


The default location for the tnsnames.ora and listener.ora files is the $ORACLE_HOME/network/admin/ directory. However, you can also use a central location for these files, for example /etc.

Modifying the listener.ora File

If you are upgrading from a previous release of Oracle Database, then Oracle recommends that you use the current release of Oracle Net 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.

For any database instances earlier than release 8.0.3, add static service information to the listener.ora file. Oracle Database releases later than release 8.0.3 do not require static service information.

Modifying the tnsnames.ora File

Unless you are using a central tnsnames.ora file, copy Oracle Net 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.

Configuring Oracle Label Security

If you installed Oracle Label Security, then you must configure it 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. If you configure Oracle Label Security 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 integration, Oracle Internet Directory must be installed in your environment and the Oracle database must be registered in the directory.

See Also:

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

Installing Natively Compiled Java Libraries for Oracle JVM and Oracle interMedia

If you plan to use Oracle JVM or Oracle interMedia, then Oracle strongly recommends that you install the natively compiled Java libraries (NCOMPs) used by those products from the Oracle Database 10g Companion CD. These libraries are required to improve the performance of the products on your platform.

See Also:

For information about how to install products from the Companion CD, refer to the "Installing Oracle Database 10g Products from the Companion CD" section

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, then you can install two supplied knowledge bases (English and French) from the Oracle Database 10g Companion CD.


You can extend the supplied knowledge bases depending on your requirements. Alternatively, you can create your own knowledge bases, possibly in languages other than English and French.

See Also:

Configuring Oracle Messaging Gateway

To configure Oracle Messaging Gateway, refer to the section about Messaging Gateway in Oracle Streams Advanced Queuing User's Guide and Reference. 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 lines similar to the following to the SID_LIST parameter for the listener in the listener.ora file:

    (SID_DESC =
      (SID_NAME = mgwextproc)
      (ENVS = EXTPROC_DLLS=/oracle_home/lib32/libmgwagent.dylib,
      (ORACLE_HOME = oracle_home)
      (PROGRAM = extproc32)

    In this example:

    • The ENVS parameter defines the shared library path environment variable and any other required environment variables.

      In the settings for the shared library path environment variable, you must also add any additional library paths required for non-Oracle messaging systems, for example WebSphere MQ or TIBCO Rendezvous.

    • oracle_home is the path of the Oracle home directory.

    • extproc32 is the external procedure agent executable file

      The following example shows a sample listener.ora file:


      In the following example, the PLSExtProc service is the default service for PL/SQL external procedures.
        (SID_LIST =
          (SID_DESC =
            (SID_NAME = PLSExtProc)
            (ORACLE_HOME = /u01/app/oracle/product/10.2.0/db_1)
            (PROGRAM = extproc)
          (SID_DESC =
            (SID_NAME = mgwextproc)
      (ENVS = EXTPROC_DLLS=/u01/app/oracle/product/10.2.0/db_1/lib32/libmgwagent.dylib,
      DYLD_LIBRARY_PATH =/System/Library/Frameworks/JavaVM.framework/Versions/1.4.2/Libraries: /u01/app/oracle/product/10.2.0/db_1/lib32)
             (ORACLE_HOME = /u01/app/oracle/product/10.2.0/db_1)
             (PROGRAM = extproc32)

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 $ORACLE_HOME/mgw/admin/mgw.ora file for external procedures, set the CLASSPATH environment variable to include the classes in the following table and any additional classes required for Oracle Messaging Gateway to access non-Oracle messaging systems, for example WebSphere MQ or TIBCO Rendezvous classes:

Classes Path
Oracle Messaging Gateway ORACLE_HOME/mgw/classes/mgw.jar
JRE internationalization ORACLE_HOME/jdk/JRE/lib/i18n.jar
JRE runtime ORACLE_HOME/jdk/JRE/lib/rt.jar
Oracle JDBC ORACLE_HOME/jdbc/lib/ojdbc14.jar
Oracle internationalization ORACLE_HOME/jdbc/lib/orai18n.jar
SQLJ ORACLE_HOME/oc4j/sqlj/lib/translator.jar


JMS Interface ORACLE_HOME/rdbms/jlib/jmscommon.jar
Oracle JMS implementation ORACLE_HOME/rdbms/jlib/aqapil3.jar
Java Transaction API ORACLE_HOME/jlib/jta.jar


All the lines in the mgw.ora file must consist of less than 1024 characters.

Configuring Oracle Precompilers

This section describes postinstallation tasks for Oracle precompilers.


All precompiler configuration files are located in the $ORACLE_HOME/precomp/admin directory.

Configuring Pro*C/C++

Verify that the PATH environment variable setting includes the directory that contains the C compiler executable. The default directory for the gcc compiler executable is /usr/bin.

To verify the path setting of the gcc compiler, you must use the following command:

$ which gcc

Configuring OCCI

The Oracle C++ Call Interface (OCCI) libraries for use with GNU C++ compiler version 4.0.1 are installed with this release. The libraries are installed in the following locations:


Installing Oracle Database 10g Products from the Companion CD

The Oracle Database 10g Companion CD contains additional products that you can install. Whether you must install these products depends on which Oracle Database products or features you plan to use. If you plan to use the following products or features, then you must complete the Oracle Database 10g Products installation from the Companion CD:

  • JPublisher

  • Oracle JVM

  • Oracle interMedia

  • Oracle JDBC development drivers

  • Oracle SQLJ

  • Oracle Database Examples

  • Oracle Text supplied knowledge bases

  • Oracle Ultra Search

For information about installing software from the Companion CD, refer to Oracle Database Companion CD Installation Guide for Apple Mac OS X (Intel).