Skip Headers

Oracle® Database Client Installation Guide
10g Release 1 (10.1.0.2.0) for 64-Bit Windows
Part No. B13804-02
  Go To Table Of Contents
Contents
Go To Index
Index

Previous Next  

4 Oracle Database Client Postinstallation Tasks

This chapter describes how to complete postinstallation tasks after you have installed the software.

This chapter contains these topics:


Note:

This chapter describes basic configuration only. See Oracle Database Platform Guide for Windows and product-specific administration and tuning guides for more sophisticated configuration and tuning information.

4.1 Required Postinstallation Tasks

You must perform the tasks described in the following section after completing an installation:

4.1.1 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, then 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

  6. Open the patch ReadMe file, which you can access by clicking the View ReadMe icon, and follow the installation instructions.

    Some patches install with Oracle Universal Installer; others require special procedures. Oracle recommends that you always read the ReadMe before proceeding.

  7. Return to the Patch Set page, click Download, and save the file on the system.

  8. Use an unzip utility to uncompress the Oracle patches that you downloaded from OracleMetaLink.

4.1.2 Configuring Oracle Database to Communicate with Automatic Storage Management

On a Windows installation of Oracle Database using Automatic Storage Management, you must enable Windows native authentication on each client. To do so, check the sqlnet.ora file, by default located in ORACLE_BASE\ORACLE_HOME\network\admin, and make sure that it has NTS enabled. For example:

sqlnet.authentication_services=(NTS)

See Also:

Oracle Database Platform Guide for Windows for more information about Windows native authentication.

4.2 Recommended Postinstallation Tasks

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

4.2.1 Connecting Oracle Database Client to an Oracle Database

When you run Oracle Universal Installer to install Oracle Database Client, you are given the option of launching Net Configuration Assistant to complete a typical configuration. This enables you to configure Oracle Database Client to connect to an Oracle database. If you chose not to run this tool but later decide you should have, use the following procedure to configure Oracle Database Client.

  1. From the Start menu, choose Oracle - HOME_NAME, then Configuration and Migration Tools, then Net Configuration Assistant.

  2. In the Welcome screen, select Local Net Service Name configuration and click Next.

  3. In the Net Service Name Configuration screen, select Add and click Next.

  4. In the Service Name screen, enter the name of the Oracle database to which you want to connect and click Next.

  5. In the Select Protocols screen, select the protocol you want and click Next.

  6. In the Protocol screen, depending on the protocol you selected, enter the appropriate information and click Next.

  7. In the Net Test screen, select whether you want to test the connection, and click Next.

  8. In the Net Service Name screen, enter a name for the net service and click Next.

  9. Answer the remaining prompts, which allow you to configure another net service name, and then click Finish to complete the configuration.


See Also:

Oracle Net Services Administrator's Guide for more information on Oracle Net Configuration Assistant

4.2.2 Connecting Instant Client to an Oracle Database

Before you can connect Instant Client 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. This directory is the Oracle home directory that you specified during installation, for example:

C:\oracle\products\10.1.0\client_1

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:

4.2.2.1 Specifying a Connection by Using Direct Addressing

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 easy in that you do not have to create and manage a tnsnames.ora file, but your application users will need to specify the hostname and port number when they want to log in to your application.

For example, suppose you are running SQL*Plus on the client machine 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 launch 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:

    //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 Client

4.2.2.2 Specifying a Connection by Configuring a tnsnames.ora File

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.

To install Oracle Net Configuration Assistant:

  1. Run Oracle Universal Installer.

  2. Select the Custom installation type.

  3. In the Available Product Components list, select Oracle Network Utilities and click Next.

  4. In the Summary screen, 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:

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

  • Place the tnsnames.ora file in the ORACLE_HOME/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 on Oracle Call Interface Instant Client connection strings

4.2.2.3 Specifying a Connection by Using an Empty Connect String and the LOCAL Variable

You can set the connect string to an empty connect string (""), and then set the LOCAL environment variable to one of the following values:

  • A direct address, as described under "Specifying a Connection by Using Direct Addressing"

  • 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 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.

4.2.3 Setting Up User Accounts

For information about setting up additional user accounts, see Oracle Database Platform Guide for Windows.

4.2.4 Running Oracle Enterprise Manager Java Console

In addition to using Oracle Enterprise Manager Database Grid Control, you can use the Oracle Enterprise Manager Java Console to manage databases from this release or previous releases. You install the Java Console by using the Administrator installation type.


Note:

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

To start the Java Console, follow these steps:

  1. From the Start menu, choose Run.

  2. Enter the following command and click OK:

    oemapp console
    

Note:

You can also start the Oracle Enterprise Manager Java Console from the Start menu. From the Start menu, choose Programs, then Oracle - HOME_NAME, then Enterprise Manager Console.

4.2.5 Using Oracle9i Language and Definition Files with Oracle Database 10g Release 1 (10.1)

You can use Oracle9i database language and territory definition files with Oracle Database 10g release 1 (10.1). If the computer where Oracle Database is installed has been configured to use this functionality, you need to enable this functionality on each client computer as well.

To enable this functionality:

  1. Run the cr9idata.pl script, by default located in ORACLE_BASE\ORACLE_HOME\nls\data\old.

    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.

  2. Set the ORA_NLS10 environment variable to point to the directory where you installed the new language and territory definition files, which by default are in ORACLE_BASE\ORACLE_HOME\nls\data.

  3. Restart Oracle Database.


See Also:


4.2.6 Configuring Oracle Counters for Windows Performance Monitor

Before you can use to view Oracle-specific counters, you must specify the SYSTEM password using Operfcfg.exe located in the ORACLE_BASE\ORACLE_HOME\bin directory.

To set the system password, enter the following:

operfcfg.exe -U SYSTEM -P password -D TNS_Alias_for_database


See Also:

Oracle Database Platform Guide for Windows for additional information about Oracle Counters for Windows Performance Monitor

4.3 Required Product-Specific Postinstallation Task—Configuring Oracle Net Services

You can configure Oracle Database Client to communicate with Oracle Net Services by adding the appropriate entries to the tnsnames.ora and listener.ora files. If you have a previous release or Oracle software, you can just copy information in the Oracle Net tnsnames.ora and listener.ora configuration files from the previous release to the corresponding files in the new release.


Note:

The default location for the tnsnames.ora and listener.ora files is the ORACLE_BASE\ORACLE_HOME\network\admin directory.