Skip Headers
Oracle® Database Installation Guide
10g Release 1 (10.1.0.3) for Linux x86-64
Part No. B14399-01
  Go To Table Of Contents
Contents		 Go To Index
Index
Previous
Previous 		Next
Next 		 

4 Post-installation Tasks

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

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

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


Note:

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

Required Post-installation 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 your installation. To download required patches:

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

    http://metalink.oracle.com

  2. Log in to OracleMetalink.


    Note:

    If you are not an OracleMetalink registered user, 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.

Running Oracle Enterprise Manager Java Console

In addition to using Oracle Enterprise Manager Database Control or Grid Control to manage an Oracle Database 10g database, you can also use the Oracle Enterprise Manager Java Console to manage databases from this release or previous releases. The Java Console is installed by the Administrator installation type.


Note:

Oracle recommends that you use Grid Control or Database Control in preference to the Java Console when possible.

To start the Java Console, follow these steps:

  1. Set the ORACLE_HOME environment variable to specify the Oracle home directory where you installed Oracle Client.

  2. Set the shared library path environment variable of the system to include the following directories:

    Platform Environment Variable Required Setting
    Linux x86-64 LD_LIBRARY_PATH 
    $ORACLE_HOME/lib32:$ORACLE_HOME/lib:$LD_LIBRARY_PATH

  3. Enter the following command to start the Java Console: 

    $ $ORACLE_HOME/bin/oemapp

Connecting with Instant Client

If you installed the Instant Client installation type, you can configure users' environments to enable dynamically linked client applications to connect to a database as follows:

  1. Set the appropriate shared library path environment variable for your platform to specify the directory that contains the Instant Client libraries. For the Instant Client installation type, this directory is the Oracle home directory that you specified during the installation, for example: 

    /u01/app/oracle/product/10.1.0/client_1

    The following table shows the appropriate environment variable for the platform:

    Platform Environment Variable
    Linux x86-64 LD_LIBRARY_PATH

  2. Use one of the following methods to specify database connection information for the client application:

    • Specify a SQL connect URL string using the following format: 

      //host:port/service_name

    • Set the TNS_ADMIN environment variable to specify the location of the tnsnames.ora file and specify a service name from that file.

    • Set the TNS_ADMIN environment variable and set the TWO_TASK environment variable to specify a service name from the tnsnames.ora file.


Note:

You do not have to specify the ORACLE_HOME environment variable.

Configuring Oracle Products

Many Oracle products and options must be configured before you use them for the first time. Before using individual Oracle Database products or options, see the appropriate manual in the product documentation library, available on the Oracle Documentation Library CD-ROM, the DVD-ROM, or on the OTN Web site.

Recommended Post-installation Tasks

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

Backing Up 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 the 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 the Bourne, Bash or Korn shell: 

      $ . /usr/local/bin/oraenv

    • For the 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: 

    SQL> STARTUP

  5. Run the utlrp.sql script: 

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

Setting Up User Accounts

For information about setting up additional user accounts, see the Oracle Database Administrator's Reference for UNIX Systems.

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, 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:

    • Bourne shell (sh), Bash shell (bash), or Korn shell (ksh): 

      $ ORACLE_HOME=/u01/app/oracle/product/10.1.0/db_1 
$ export ORACLE_HOME

    • C shell (csh or tcsh): 

      % setenv ORACLE_HOME /u01/app/oracle/product/10.1.0/db_1

  3. Enter the following command: 

    $ $ORACLE_HOME/bin/genclntst

Required Product-Specific Post-installation Tasks

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


Note:

You need only perform post-installation 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, you might want to 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.


Note:

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 thesethis files, for example /var/opt/oracle/etc.

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 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, 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, you cannot configure it to use Oracle Internet Directory at a later stage.


Note:

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:

For more information about Oracle Label Security enabled with Oracle Internet Directory, see the Oracle Label Security Administrator's Guide.

Installing Natively Compiled Java Libraries for Oracle JVM and Oracle interMedia

If you plan to use Oracle JVM or Oracle interMedia, 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.

For information about how to install products from the Companion CD, see 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, you can install two supplied knowledge bases (English and French) from the Oracle Database 10g Companion CD.


Note:

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. For more information about creating and extending knowledge bases, see the Oracle Text Reference.

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

Configuring Oracle Messaging Gateway

To configure Oracle Messaging Gateway, see the section about Messaging Gateway in the Oracle Streams Advanced Queuing User's Guide and Reference manual. When following the instructions listed in that manual, refer to this section for additional platform-specific 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: 

    (ADDRESS = (PROTOCOL=IPC)(KEY=EXTPROC))

  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 = platform-specific_env_vars)
    (ORACLE_HOME = oracle_home)
    (PROGRAM = extproc_agent)
  )

    In this example:

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

      The following table lists the environment variables and required values that you must specify for each platform. In 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.

      Platform ENVS Parameter Setting
      Linux x86-64 
      EXTPROC_DLLS=/oracle_home/lib32/libmgwagent.so,
LD_LIBRARY_PATH=/oracle_home/jdk/jre/lib/i386:/oracle_home/jdk/jre/lib/i386/server
server:/oracle_home/lib32

    • oracle_home is the path of the Oracle home directory.

    • extproc_agent is the external procedure agent executable file. The following table lists the correct executable file for each platform:

      Platform Agent Executable File
      Linux x86-64 extproc32

    The following examples show sample listener.ora files on Linux x86-64:


    Note:

    In the following examples, the PLSExtProc service is the default service for PL/SQL external procedures. 

    • SID_LIST_LISTENER =
  (SID_LIST =
    (SID_DESC =
      (SID_NAME = PLSExtProc)
      (ORACLE_HOME = /u01/app/oracle/product/10.1.0/db_1)
      (PROGRAM = extproc)
    )
    (SID_DESC =
      (SID_NAME = mgwextproc)
      (ENVS =  EXTPROC_DLLS=/u01/app/oracle/product/10.1.0/db_1/lib32/
libmgwagent.sl,LD_PRELOAD=/u01/app/oracle/product/10.1.0/db_1/jdk/jre/
lib/PA-RISC/server/libjvm.sl,SHLIB_PATH=/u01/app/oracle/product/10.1.0/db_1/jdk/jre/lib/PA_RISC:/u01/app/oracle/product/10.1.0/db_1/jdk/jre/lib/PA_RISC/server:/u01/app/oracle/product/10.1.0/db_1/lib32)
        (ORACLE_HOME = /u01/app/oracle/product/10.1.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 = 
(DESCRIPTION= 
   (ADDRESS_LIST= (ADDRESS= (PROTOCOL=IPC)(KEY=EXTPROC))) 
   (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/JRE/lib/i18n.jar
JRE runtime ORACLE_HOME/JRE/lib/rt.jar
Oracle JDBC ORACLE_HOME/jdbc/lib/ojdbc14.jar
Oracle internationalization ORACLE_HOME/jdbc/lib/orai18n.jar
SQLJ ORACLE_HOME/sqlj/lib/translator.zipORACLE_HOME/sqlj/lib/runtime12.zip
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


Note:

All the lines in the mgw.ora file should be less than 1024 characters.

Configuring Oracle Precompilers

The following sectiondescribes post-installation tasks for Oracle precompilers.


Note:

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. Table 4-1 shows the default directories and the appropriate commands to verify the path setting, depending on your platform and compiler.

Table 4-1 C/C++ Compiler Directory

Platform Path Command
Linux x86-64 /usr/bin $ which gcc

Installing Oracle Database 10g Products from the Companion CD

The Oracle Database 10g Companion CD contains additional products that you can install. Whether you need to 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, Oracle strongly recommends that you complete the Oracle Database 10g Products installation from the Companion CD:

To install Oracle Database 10g Products from the Companion CD, follow these steps:


Note:

For more detailed installation information, see the Oracle Database Companion CD Installation Guide, which is available on the Companion CD.

  1. Insert the Oracle Database 10g Companion CD or the Oracle Database 10g DVD-ROM into the disc drive.

  2. If necessary, log into the system as the user who installed Oracle Database (typically the oracle user).

  3. To start the Installer, enter the following commands where directory_path is the CD-ROM mount point directory or the path of the companion directory on the DVD-ROM: 

    $ cd /tmp

    $ /directory_path/runInstaller

    If the Installer does not appear, see the "X Windows Display Errors" section for information about troubleshooting.

  4. Use the following guidelines to complete the installation:

    • On the Specify File Locations screen, select the Oracle home name and path for the Oracle Database 10g installation where you want to install the products.

    • On the Select a Product to Install screen, select Oracle Database 10g Products.

    • Unless you want to install Legato Single Server Version, eEnter 3 at the prompt displayed by the root.sh script.


Note:

For more information about any of the Installer screens, click Help.

  Previous
Previous 		Next
Next
  Go To Table Of Contents
Contents		 Go To Index
Index