Skip Headers
Oracle® Database Client Installation Guide
10g Release 1 (10.1) for UNIX Systems: AIX-Based Systems, hp HP-UX, hp Tru64 UNIX, Linux, and Solaris Operating System
Part No. B12087-05
  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. Depending on your platform, set the shared library path environment variable for your system to include the following directories:

    Platform Environment Variable Required Setting
    AIX LIBPATH
    $ORACLE_HOME/lib32:$ORACLE_HOME/lib:
    $LIBPATH
    
    HP-UX SHLIB_PATH
    $ORACLE_HOME/lib32:$ORACLE_HOME/lib:
    $SHLIB_PATH
    
    Linux LD_LIBRARY_PATH
    $ORACLE_HOME/lib:$LD_LIBRARY_PATH
    
    Solaris SPARC LD_LIBRARY_PATH
    $ORACLE_HOME/lib32:$ORACLE_HOME/lib:
    $LD_LIBRARY_PATH
    
    Solaris x86 LD_LIBRARY_PATH
    $ORACLE_HOME/lib:$LD_LIBRARY_PATH
    
    Tru64 UNIX LD_LIBRARY_PATH
    $ORACLE_HOME/lib:$LD_LIBRARY_PATH
    

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

    $ $ORACLE_HOME/bin/oemapp console
    

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 each platform:

    Platform Environment Variable
    AIX LIBPATH
    HP-UX (32-bit applications) SHLIB_PATH
    Linux, HP-UX (64-bit applications), Solaris, and Tru64 UNIX 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.

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.

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 (libclntst.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 Client installation. For example:

    • Bourne, Bash, or Korn shell:

      $ ORACLE_HOME=/u01/app/oracle/product/10.1.0/client_1 
      $ export ORACLE_HOME
      
      
    • C shell:

      % setenv ORACLE_HOME /u01/app/oracle/product/10.1.0/client_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:

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 configuration file from the previous release to the corresponding file for the new release.


Note:

The default location for the tnsnames.ora file is the $ORACLE_HOME/network/admin/ directory. However, you can also use a central location for this file, for example /var/opt/oracle on Solaris or /etc on other platforms.

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

Configuring Oracle Precompilers

The following sections describe 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
AIX and Tru64 UNIX /usr/bin $ which cc
HP-UX /usr/bin $ which cc
Linux x86 /usr/bin $ which gcc
/opt/intel/compiler70/ia32/bin $ which icc
Linux Itanium /usr/bin $ which gcc
/opt/intel/compiler70/ia64/bin $ which ecc
Solaris /opt/SUNWspro/bin $ which cc
zSeries Linux /usr/bin $ which gcc

Configuring Pro*COBOL

The following sections describe how to set the environment for Pro*COBOL, depending on which COBOL compiler you are using:


See Also:

See your product-specific COBOL documentation for more information about setting the environment.

Setting the Environment for Micro Focus Server Express

If you are using Micro Focus Server Express, complete the following steps to set environment variables for the Pro*COBOL precompiler:

  1. Set the COBDIR environment variable to specify the COBOL installation directory.

  2. Verify that the PATH environment variable setting includes the directory that contains the COBOL compiler executable ($COBDIR/bin).

    Table 4-2 shows the default directory and the appropriate command to verify the path setting, depending on your platform.

    Table 4-2 Micro Focus Server Express COBOL Compiler Directory

    Platform Path Command
    AIX /usr/lpp/cobol64/cobol/bin
    $ which cob
    
    /usr/lpp/cobol32/cobol/bin
    $ which cob32
    
    Linux x86 /opt/lib/cobol/bin
    $ which cob
    
    HP-UX and Solaris SPARC /opt/lib/cobol/bin
    $ which cob
    $ which cob32
    
    Tru64 UNIX /usr/lib/cobol/bin
    $ which cob
    
    zSeries Linux /opt/microfocus/cobol/bin
    $ which cob
    $ which cob32
    

  3. Verify that the shared library path environment variable includes the $COBDIR/lib directory.


    See Also:

    See your product-specific COBOL documentation for more information about COBDIR and COBLIB environment variables.

Setting the Environment for Acucorp ACUCOBOL-GT

If you are using Acucorp ACUCOBOL-GT, complete the following steps to set environment variables for the Pro*COBOL precompiler:

  1. Verify that the PATH environment variable setting includes the directory that contains the COBOL compiler executable.

    Table 4-3 shows the default directory and the appropriate command to verify the path setting, depending on your platform.

    Table 4-3 Acucorp ACUCOBOL-GT COBOL Compiler Directory

    Platform Path Command
    Solaris SPARC /opt/COBOL/bin
    $ which ccbl
    
    zSeries Linux /opt/COBOL31/bin
    $ which ccbl
    
    /opt/COBOL/bin
    $ which ccbl
    

  2. Verify that the shared library path environment variable includes the /opt/COBOL/lib directory (or the /opt/COBOL31/lib directory if you are using the 31-bit compiler on zSeries Linux).

  3. Set the A_TERMCAP environment variable to specify the location of the a_termcap file and set the A_TERM environment variable to specify a supported terminal from that file, for example:

    • Bourne, Bash, or Korn shell:

      $ A_TERMCAP=/opt/COBOL/etc/a_termcap
      $ A_TERM=vt100
      $ export A_TERMCAP A_TERM
      
      
    • C shell:

      % setenv A_TERMCAP /opt/COBOL/etc/a_termcap
      % setenv A_TERM vt100
      
      

Configuring Pro*FORTRAN

Verify that the PATH environment variable setting includes the directory that contains the FORTRAN compiler executable. Table 4-4 shows the default directory and the appropriate command to verify the path setting, depending on your platform.

Table 4-4 FORTRAN Compiler Directory

Platform Path Command
AIX /usr/bin $ which xlf
HP-UX /opt/fortran90/bin $ which f90
Solaris /opt/SUNWspro/bin $ which f95
Tru64 UNIX /usr/bin $ which f77

AIX Only: Configuring SQL*Module for Ada

The following sections describe post-installation tasks for SQL*Module for Ada.

Verifying the PATH Environment Variable Setting

Verify that the PATH environment variable setting includes the directory that contains the Ada compiler executable. To display the path of the Ada executable, enter the following command:

$ which ada

The default directory for the Ada executable is /usr/lpp/powerada/ada95/bin.

Verifying the OC Systems PowerAda Compiler Configuration File

Verify that the OC Systems PowerAda 5.3 compiler configuration file is configured. The file is located in the PowerAda installation directory. Check the following file, depending on your shell:

  • Korn shell:

    setup
    
    
  • C shell:

    setup.csh
    
    

See Also:

For more information about these setup files, see the PowerAda documentation.

Linux x86 and Linux Itanium Only: Configure OCCI

Two sets of Oracle C++ Call Interface (OCCI) libraries are installed with release 10.1.0.3 on Linux systems. One set is for use with GNU C++ compiler version 2.96 and the other set is for use with GNU C++ version 3.2. The libraries are installed in the following locations:

  • Libraries for use with GNU C++ version 2.96:

    $ORACLE_HOME/lib/gcc2.96/libocci10.a
    $ORACLE_HOME/lib/gcc2.96/libocci10.so.10.1
    
    
  • Libraries for use with GNU C++ version 3.2:

    $ORACLE_HOME/lib/gcc3/libocci10.a
    $ORACLE_HOME/lib/gcc3/libocci10.so.10.1
    
    

Although the libraries are installed on all Linux distributions, they are not supported on all distributions. The following table shows the supported GNU C++ version for each distribution:

Linux Distribution GNU C++ Versions Supported
Red Hat Enterprise Linux AS/ES 2.1 Only 2.96
Red Hat Enterprise Linux AS/ES 3 Both 2.96 and 3.2
SUSE Linux Enterprise Server 8 and 9 Only 3.2

To create the required symbolic links in the $ORACLE_HOME/lib directory to the appropriate libraries for your distribution, you must run the following script after all database or client installations:

$ORACLE_HOME/bin/occi_links.sh


Note:

On Red Hat Enterprise Linux 3, this script creates links to the libraries for GNU C++ version 3.2 by default. If you want to use GNU C++ version 2.96, you must manually create the symbolic links to the appropriate libraries. For example:
$ ln -s  $ORACLE_HOME/lib/gcc2.96/libocci*  $ORACLE_HOME/lib