| Oracle® Database Client Installation Guide 11g Release 2 (11.2) for Apple Mac OS X (Intel) E38228-02 |
|
|
PDF · Mobi · ePub |
| Oracle® Database Client Installation Guide 11g Release 2 (11.2) for Apple Mac OS X (Intel) E38228-02 |
|
|
PDF · Mobi · ePub |
This chapter describes how to complete postinstallation tasks after you have installed the Oracle Database Client software. It includes information about the following topics:
You must perform the tasks listed in "Required Postinstallation Tasks". Oracle recommends that you perform the tasks listed in "Recommended Postinstallation Tasks" after all installations.
If you install and intend to use any of the products listed in "Required Product-Specific Postinstallation Tasks", then you must perform the tasks listed in the product-specific subsections.
You must perform the tasks described in the following sections after completing an installation:
To update Instant Client:
Download Instant Client from Oracle Technology Network:
http://www.oracle.com/technetwork/database/features/instant-client/index-097480.html
If you want to place the files in the existing directory, then ensure that the directory is empty.
If you want to place the files into a different directory (and remove the previous files), ensure that you update the DYLD_LIBRARY_PATH environment variable setting to reflect the new location.
Note:
A restriction on Instant Client or Instant Client Light is that you cannot perform patch upgrades using the
opatch utility because the Instant Client installation does not create an inventory, which the patch upgrade process must access for patch upgrades. The absence of an inventory also means that the installed intern patch reporting and conflict detection before a patch attempt are not possible.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 the platform to specify the directory that contains the Instant Client libraries. For example, if your Instant Client is located in the /bin/oracle/instantclient_11_2 directory, then set the DYLD_LIBRARY_PATH environment variable to this directory.
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
For example:
//shobeen:1521/sales_us
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 and the TWO_TASK environment variables to specify a service name from the tnsnames.ora file.
Note:
It is not required that you specify theORACLE_HOME environment variable.Oracle recommends that you perform the tasks described in the following sections after completing an installation:
Before you can connect Instant Client (including Instant Client Light) to an Oracle database, ensure that the DYLD_LIBRARY_PATH environment variable specifies the directory that contains the Instant Client libraries.
For example, if the shared libraries for Instant Client or Instant Client Light (if you have installed Instant Client Light) are in the /bin/oracle/instantclient_11_2 directory, then set the DYLD_LIBRARY_PATH environment variable to the following path:
/bin/oracle/instantclient_11_2
After checking the DYLD_LIBRARY_PATH environment variable, you can use any of the following methods to specify Oracle Database connection information for client applications:
Specifying a Connection by Using the Easy Connect Naming Method
Specifying a Connection Using an Empty Connect String and TWO_TASK
You can specify a connection address to an Oracle Database directly from a client application, without having to configure a tnsnames setting for the Instant Client. This method is convenient as you do not have to create and manage a tnsnames.ora file. However, the application users must specify the host name and port number when they want to log in to the application.
For example, if you run SQL*Plus on the client computer and want to connect to the sales_us database, which is located on a server whose host name is shobeen and port number is 1521, then you can log in as follows:
sqlplus system/admin@//shobeen:1521/sales_us
Similarly, in the application code, you can use Oracle Call Interface net naming methods to create the Instant Client-to-Oracle Database connection. For example, the following formats in the OCIServerAttach() call specify the connection information:
Specify a SQL connect URL string using the following format:
//host[:port][/service_name]
For example:
//shobeen:1521/sales_us
Alternatively, you can specify the SQL connect information as an Oracle Net keyword-value pair. For example:
"(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp) (HOST=shobeen) (PORT=1521)) (CONNECT_DATA=(SERVICE_NAME=sales_us)))"
See Also:
Oracle Call Interface Programmer's Guide for more information on using Oracle Call Interface Instant ClientYou can set the connect string to an empty connect string (""), and then set the TWO_TASK environment variable to one of the following values:
A direct address, as described under "Specifying a Connection by Using the Easy Connect Naming Method"
Oracle Net keyword-value pair
A tnsnames.ora entry and TNS_ADMIN is set to the location of tnsnames.ora
A tnsnames.ora entry and the following:
tnsnames.ora file located in $ORACLE_HOME/network/admin
The ORACLE_HOME environment variable set to this Oracle home
This method allows the applications to specify internally a connection string if the application code itself uses an empty connection string. The benefit of an empty connect string is that the application itself does not have to specify the tnsnames.ora entry. Instead, when a user starts the application, the location of the database is determined by a script or the environment, depending on where you have set the TWO_TASK environment variable. The disadvantage of using empty strings is that you must configure this additional information in order for the application to connect to the database.
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 user session. It also declares the character set of the client, which is the character set of data entered or displayed by an Oracle client program, such as SQL*Plus.
Note:
The character set of the data displayed is determined by the environment of the operating system, such as keyboard driver and fonts in use. TheNLS_LANG character set should match the operating system.Refer to the "Setting Up a Globalization Support Environment" section in Oracle Database Globalization Support Guide for information about Globalization Support.
The following sections describe postinstallation tasks that you must perform if you install and intend to use Oracle Precompliers:
Note:
You must perform postinstallation tasks only for products that you intend to use.This section describes postinstallation tasks for 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.
See Also:
Pro*C/C++ Programmer's Guide for more information about setting environment variables
|
 Copyright © 2011, 2013, Oracle and/or its affiliates. All rights reserved. Legal Notices |
|