It also describes the steps required to plug the database into Netbackup and perform a database bare metal recovery (BMR). See Configuring SQL*Plus Instant Client on Windows.The following documentation provides instructions for building an Oracle database residing on a Sun Solaris 10 (Version 5.10) operating system. On Windows, TNS_ADMIN and LOCAL may be set in the System Properties. This UNIX example connects to the database known as MYDB4: This removes the need to explicitly enter the connection identifier whenever a connection is made in SQL*Plus or SQL*Plus Instant Client. Sqlplus TWO_TASK (on UNIX) or LOCAL (on Windows) environment variable can be set to a connection identifier. This example assumes the ORACLE_HOME environment variable is set, and the $ORACLE_HOME/network/admin/tnsnames.ora or %ORACLE_HOME%\network\admin\tnsnames.ora file defines the Net Service Name MYDB3: If ORACLE_HOME is set when running Instant Client applications, it must be set to a directory that exists. This is the only reason to set the ORACLE_HOME environment variable for SQL*Plus Instant Client.
This search path includes looking in the directory specified by the ORACLE_HOME environment variable for network/admin/tnsnames.ora. Sqlplus TNS_ADMIN is not set, then an operating system dependent set of directories is examined to find tnsnames.ora.
For example, on UNIX, if your tnsnames.ora file is in /home/user1 and it defines the Net Service Name MYDB2: If you want to use Net Service Names configured in a local Oracle Net tnsnames.ora file, then set the environment variable TNS_ADMIN to the directory containing the tnsnames.ora file. See the Oracle Database Net Services Reference for more information. The use of LDAP is recommended to take advantage of the new features of Oracle Database 10 g. Sqlplus hr/ Service Names can be stored in a number of places, including LDAP. mydomain: port/MYDBĪlternatively you can use a Net Service Name: To connect to a database you must specify the database using an Oracle Net connection identifier.Īn example using an Easy Connection identifier to connect to the HR schema in the MYDB database running on mymachine is: SQL*Plus Instant Client is always 'remote' from any database server. If you have installed the lightweight Instant Client, see Lightweight Instant Client for information about supported NLS_LANG settings.Ĭonnecting to a Database with SQL*Plus Instant Client For example, to set NLS_LANG for a Japanese environment, create a user environment variable NLS_LANG set to JAPANESE_JAPAN.JA16EUC. See the Oracle Database Globalization Support Guide for more information. A default locale will be assumed if no variables are set. Set Oracle globalization variables required for your locale. Set the user environment variable SQLPATH to the directory containing the Instant Client files so glogin.sql is found.įor example, create a user variable SQLPATH set to c:\instantclient. Remove any other Oracle directories from PATH.įor example, add c:\instantclient10_2 to the beginning of PATH.
HOW TO INSTALL ORACLE 10G WINDOWS
The environment may be configured using SET commands in a Windows command prompt or made permanent by setting Environment Variables in System Properties.įor example, to set environment variables in Windows 2000 using System Properties, open System from the Control Panel, click the Advanced tab and then click Environment Variables.Īdd the directory containing the Instant Client files to the PATH system environment variable. See the Oracle Database Globalization Support Guide for more information.Ĭonfiguring SQL*Plus Instant Client on Windows Remove any other Oracle directories.įor example, to set LD_LIBRARY_PATH on Solaris in the Bourne or Korn shells: The sub-directory structure enables multiple versions of Instant Client to be available.Īdd the name of the directory containing the Instant Client libraries to LD_LIBRARY_PATH. The RPMs downloaded from OTN install into Oracle specific sub-directories in the /usr file system. Configuring SQL*Plus Instant Client on Linux (from RPMs)
0 kommentar(er)
