| Oracle® Database Client Installation Guide 10g Release 1 (10.1) for UNIX Systems: AIX-Based Systems, hp HP-UX PA-RISC (64-bit), hp Tru64 UNIX, Linux x86, and Solaris Operating System (SPARC) Part No. B12087-01 |
|
 |
 |
| Oracle® Database Client Installation Guide 10g Release 1 (10.1) for UNIX Systems: AIX-Based Systems, hp HP-UX PA-RISC (64-bit), hp Tru64 UNIX, Linux x86, and Solaris Operating System (SPARC) Part No. B12087-01 |
|
|
|
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. |
You must perform the tasks described in the following sections after completing an installation:
Check the OracleMetalink Web site for required patches for your installation. To download required patches:
Use a Web browser to view the OracleMetalink Web site:
http://metalink.oracle.com
Log in to OracleMetalink.
|
Note: If you are not an OracleMetalink registered user, click Register for MetaLink! and follow the registration instructions. |
On the main OracleMetalink page, click Patches.
Select Simple Search.
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
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:
Set the ORACLE_HOME environment variable to specify the Oracle home directory where you installed Oracle Client.
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 | LD_LIBRARY_PATH |
$ORACLE_HOME/lib32:$ORACLE_HOME/lib: $LD_LIBRARY_PATH |
| Tru64 UNIX | LD_LIBRARY_PATH |
$ORACLE_HOME/lib:$LD_LIBRARY_PATH |
Enter the following command to start the Java Console:
$ $ORACLE_HOME/bin/oemapp
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:
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 |
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. |
Oracle recommends that you perform the tasks in the following section after completing an installation:
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.
For information about setting up additional user accounts, see the Oracle Database Administrator's Reference for UNIX Systems.
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:
Switch user to oracle.
Set the ORACLE_HOME environment variable to specify the Oracle home directory used by the Oracle Client installation. For example:
Bourne shell (sh), Bash shell (bash), or Korn shell (ksh):
$ ORACLE_HOME=/u01/app/oracle/product/10.1.0/client_1 $ export ORACLE_HOME
C shell (csh or tcsh):
% setenv ORACLE_HOME /u01/app/oracle/product/10.1.0/client_1
Enter the following command:
$ $ORACLE_HOME/bin/genclntst
The following sections describe platform-specific post-installation tasks that you must perform if you installed and intend to use the products mentioned:
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.
The following sections describe post-installation tasks for Oracle precompilers:
|
Note: All precompiler configuration files are located in the$ORACLE_HOME/precomp/admin directory. |
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.
Complete the following steps to set environment variables for the Pro*COBOL precompiler:
Set the COBDIR environment variable to specify the COBOL installation directory.
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.
Verify that the shared library path environment variable includes the $COBDIR/lib directory.
Verify that the PATH environment variable setting includes the directory that contains the FORTRAN compiler executable. Table 4-3 shows the default directory and the appropriate command to verify the path setting, depending on your platform.
The following sections describe post-installation tasks for SQL*Module for Ada.
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.
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. |
