|Oracle® Database Client Installation Guide
11g Release 1 (11.1) for Microsoft Windows
|PDF · Mobi · ePub|
This chapter describes the following postinstallation tasks:
Note:This chapter describes basic configuration only. See Oracle Database Platform Guide for Microsoft Windows and product-specific administration and tuning guides for more sophisticated configuration and tuning information.
This section covers the following topics:
Note:You cannot update Instant Client by downloading a patch. Use the procedure under "Updating Instant Client" to update Instant Client.
Use a Web browser to view the My Oracle Support Web site:
Log in to My Oracle Support.
Note:If you are not a My Oracle Support registered user, then click Register on the home page and follow the registration instructions.
On the main My Oracle Support page, click Patches & Updates.
Select Product or Family (Advanced) search.
Specify the following information, then click Search:
In the Product is field, choose
RDBMS Server from the list.
In the Release field, choose the current release number from the list.
Select the Type field from the list.
Choose Patchset from the list.
Selecting the Patchset option opens the Search results page. This page provides a list of patches that can be downloaded and saved. Clicking a patch enables you to choose options from the options menu on the top of the screen.
Open the patch Read Me file, which you can access by clicking the Read Me icon in the options menu for each patchset, and follow the installation instructions.
Some patches install with Oracle Universal Installer; others require special procedures. Oracle recommends that you always read the Read Me before proceeding.
Return to the Patch Set page, click Download, and save the file on the system.
Download Instant Client from Oracle Technology Network (
Place the new files directly on top of the previous files.
If you place the files into a different directory (and remove the previous files), be sure to update your
PATH environment variable setting to reflect the new location.
To configure Instant Client Light:
ORACLE_CLIENT_HOME directory, either rename or delete the
oraociei11.dll file is the main binary for Instant Client.
\install\instantclient\light directory, copy the
oraociicus11.dll file to the
oraociicus11.dll file is the binary for Instant Client Light.
Make sure that the
PATH environment variable points to the
Note:If the Instant Client
PATHis not set, applications will try to load the regular Instant Client libraries first. If the applications cannot find these, they will attempt to load the Instant Client Light library next.
After you run Oracle Universal Installer to install Oracle Database Client, you need to use Net Configuration Assistant (NetCA) to configure Oracle Database Client to connect to an Oracle database. At the end of installation, Oracle Universal Installer prompts you to configure the database connection. If you bypassed that option, or if you need to change the database connection later on, use the following procedure if you installed the Administrator, Runtime, or Custom installation types.
See Also:"Connecting Instant Client or Instant Client Light to an Oracle Database" if you had installed the Instant Client installation type
To connect Oracle Database Client to an Oracle Database:
From the Start menu, choose Oracle - HOME_NAME, then Configuration and Migration Tools, then Net Configuration Assistant.
In the Net Service Name Configuration window, select Add and click Next.
In the Service Name window, enter the name of the Oracle database to which you want to connect and click Next.
In the Select Protocols window, select the protocol you want and click Next.
In the Protocol window, depending on the protocol you selected, enter the appropriate information and click Next.
In the Net Test window, select whether you want to test the connection, and click Next.
In the Net Service Name window, enter a name for the net service and click Next.
Answer the remaining prompts, which allow you to configure another net service name, and then click Finish to complete the configuration.
Net Configuration Assistant creates the
tnsnames.ora file in the following location:
See Also:Oracle Database Net Services Administrator's Guide for more information about Oracle Net Configuration Assistant
Before you can connect Instant Client or Instant Client Light to an Oracle database, make sure that the
PATH environment variable specifies the directory that contains the Instant Client libraries. (By default, Oracle Universal Installer updates the
PATH variable for you during the installation process, but another user may have inadvertently reset it since then.) This directory is the Oracle home directory that you specified during installation.
For example, for regular Instant Client, it is in:
For Instant Client Light, it is in:
After you have checked the
PATH environment variable, you can use any of the following methods to specify Oracle Database connection information for client applications:
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 in that you do not have to create and manage a
tnsnames.ora file. However, your application users will need to specify the host name and port number when they want to log in to your application.
For example, suppose you are running 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. If you start SQL*Plus from the command line, you could log in as follows:
Enter user-name: system@admin@//shobeen:1521/sales_us
Similarly, in your 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:
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 about using Oracle Call Interface Instant Client
By default, when you install Instant Client, Oracle Universal Installer does not include a sample
tnsnames.ora file nor the Oracle Net Configuration Assistant utility normally used to create it. However, if you want to shield users from having to specify actual host names and port numbers, you may want to consider using a
tnsnames.ora file to set the Instant Client-to-Oracle Database connection.
You can create the
tnsnames.ora file manually by copying and modifying a version of this file from another Oracle installation, or you can use Oracle Net Configuration Assistant to create and manage it for you.
Run Oracle Universal Installer.
Select the Custom installation type.
In the Available Product Components list, select Oracle Network Utilities and click Next.
In the Summary window, click Install, then click Exit and Yes to exit Oracle Universal Installer.
After you have installed Oracle Net Configuration Assistant, follow the procedure in "Connecting Oracle Database Client to an Oracle Database" for each client computer.
Then, on each client computer, configure either of the following settings:
tnsnames.ora file in the
\network\admin directory, and make sure that the
ORACLE_HOME environment has been set to this Oracle home.
See Also:Oracle Call Interface Programmer's Guide for more information about Oracle Call Interface Instant Client connection strings
A direct address, as described under "Specifying a Connection by Using the Easy Connect Naming Method"
Oracle Net keyword-value pair
tnsnames.ora entry and
TNS_ADMIN is set to the location of
tnsnames.ora entry and the following:
tnsnames.ora file located in
ORACLE_HOME environment variable set to this Oracle home
This method allows your 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 need to specify the
tnsnames.ora entry. Instead, when a user invokes the application, the location of the database is determined by a script or the environment, depending on where you have set the
LOCAL environment variable. The disadvantage of using empty strings is that you need to configure this additional information in order for your application to connect to the database.
For information about setting up additional user accounts, see Oracle Database Platform Guide for Microsoft Windows.
Changes have been made to the content of some of the language and territory definition files in Oracle Database 10g and later releases. These updates are necessary to correct the legacy definitions that no longer meet the local conventions in some of the languages and territories that Oracle Database supports.
Oracle Database 11g customers should review their existing application code to make sure that the correct cultural conventions, which were introduced and defined in Oracle Database 10g, are being used. For customers who may not be able to make the necessary code changes to support their applications, Oracle Database offers Oracle9i locale definition files with this release of Oracle Database. If the Oracle Database server installation has been configured to use the Oracle9i files, you need to enable this functionality in each client installation as well
To enable this functionality:
cr9idata.pl script, by default located in
If the client installation type you chose does not include this directory, you can find the
cr9idata.pl script in the same directory path in a default Oracle Database installation.
Restart Oracle Database.
Appendix B, "Installing Oracle Database Client Using Response Files" for information about response files, in which you can set the
b_cr9idata variable and then run the response file with Oracle Universal Installer
Appendix C, "Configuring Oracle Database Globalization Support" for information about globalization support that is affected by this release of Oracle Database
Oracle Database Globalization Support Guide for information about the
NLS_LANG parameter, the Globalization Support initialization parameters, and the changes made to language and territory definitions in Oracle Database 10g
To set the system password, enter the following:
See Also:Oracle Database Platform Guide for Microsoft Windows for additional information about Oracle Counters for Windows Performance Monitor
You can configure Oracle Database Client to communicate with Oracle Net Services by adding the appropriate entries to the
listener.ora files. If you have a previous release or Oracle software, you can just copy information in the Oracle Net
listener.ora configuration files from the previous release to the corresponding files in the new release.
Note:The default location for the
listener.orafiles is the
This section describes tasks that you need to complete after you install the software:
The first time you start SQL Developer after installing it or after adding any extensions, you are asked if you want to migrate your user settings from a previous release. (This occurs regardless of whether there was a previous release on your system.)
Note:Migration of user settings is supported only from SQL Developer Release 1.0 to Release 1.1. It is not supported for migration from a pre-release version of 1.1 to Release 1.1.
These settings refer to database connections, reports, and certain SQL Developer user preferences that you set in a previous version by clicking Tools and then Preferences. However, some user preferences are not saved, and you must re-specify these using the new release.
To migrate user settings from SQL Developer Release 1.0:
Install Oracle SQL Developer.
When you start SQL Developer Release 1.1, click Yes when asked if you want to migrate settings from a previous release.
In the dialog box that is displayed, do not accept the default location for the settings. Instead, specify the location of your Release 1.0 settings, which might be a folder whose path ends with
If you have used a previous release of SQL Developer or a pre-release version of the current release, you may want to preserve database connections that you have been using. To preserve database connections, save your existing database connections in an XML file. To save the connections, right-click the Connections node in the Connections Navigator and select Export Connections. After you complete the installation described in this guide, you can use those connections by right-clicking the Connections node in the Connections Navigator and selecting Import Connections
If you want to use any user-defined reports or the SQL history from a previous version, see "Location of User-Related Information" for information about where these are located. If you want to use any user-defined reports or the SQL history from Release 1.0 with both Releases 1.0 and 1.1, you must save them before using Release 1.1, because Release 1.1 modifies the files to a format that is incompatible with Release 1.0.
SQL Developer preferences (specified by clicking Tools and then Preferences) from a pre-release version of the current release cannot currently be saved and reused; you must re-specify any desired preferences.
SQL Developer stores user-related information in several places, with the specific location depending on the operating system and certain environment specifications. User-related information includes user-defined reports, user-defined snippets, SQL Worksheet history, and SQL Developer user preferences.
SQL Developer user preferences are stored under the installation directory. To preserve preferences when upgrading to a more recent version of the same SQL Developer release, but not to upgrade from Release 1.0 to 1.1, use the Check for Updates feature (click Help, then Check for Updates) to upgrade your system.
This user-related information is stored in or under the
HOME environment variable location, if defined; otherwise the
SQLDEVELOPER_USER_DIR location, if defined; otherwise as indicated in the following table.
The table shows the typical default locations (under a directory or in a file) for specific types of resources on different operating systems. (Note the period in the name of any directory or folder named
|Resource Type||Windows Systems|
C:\Documents and Settings\<user-name>\.sqldeveloper\UserReports.xml
C:\Documents and Settings\<user-name>\.sqldeveloper\UserReports.xml
C:\Documents and Settings\<user-name>\.sqldeveloper\SqlHistory.xml
SQL Worksheet archive files
C:\Documents and Settings\<user-name>\.sqldeveloper\tmp\
SQL Developer user preferences
SQL Worksheet archive files contain SQL statements that you have entered. These files begin with sqldev and then have a random number (for example,
sqldev14356.sql). If you close SQL Developer with a SQL Worksheet open that contains statements, then you will be prompted to save these files.
To specify a non-default
SQLDEVELOPER_USER_DIR location, do either of the following:
SQLDEVELOPER_USER_DIR environment variable to specify another directory path.
\sqldeveloper\sqldeveloper\bin\sqldeveloper.conf file and substitute the desired directory path for
SQLDEVELOPER_USER_DIR in the following line:
If you want to prevent other users from accessing your user-specific SQL Developer information, you must ensure that the appropriate permissions are set on the directory where that information is stored or on a directory above it in the path hierarchy. For example, you may want to ensure that the
sqldeveloper folder and the
\.sqldeveloper folder under
Documents and Settings are not shareable.