Medicinefox268

SQL*Plus Instant Client is a standalone product with all the functionality of SQL*Plus command-line. It connects to existing remote Oracle databases, but does not include its own database. It is easy to install and uses significantly less disk space than the full Oracle Database Client installation required to use SQL*Plus command-line.

• If Windows doesn’t automatically find a new driver after the printer is added, look for one on the device manufacturer's website and follow their installation instructions. Open settings for Printers & scanners.
• By default, Windows 10 does not shipped with Oracle ODBC connection utility. In other word, I was unable to connect to my Oracle database from MS Access. Installing Oracle ODBC Driver on Windows 10 is a bit tricky.

SQL*Plus Instant Client is available on platforms that support the OCI Instant Client. See the Oracle Call Interface Programmer's Guide for more information on the OCI Instant Client.

We suggest that you use the MD5 checksums and GnuPG signatures to verify the integrity of the packages you download. Connector/ODBC is a standardized database driver for Windows, Linux, Mac OS X, and Unix platforms.

To install SQL*Plus Instant Client, you need two packages:

• SQL*Plus Instant Client package.

• Either the Basic OCI Instant Client package, or the lightweight OCI Instant Client package.

Choosing the SQL*Plus Instant Client to Install

SQL*Plus Instant Client can be installed in two ways:

• Download the packages from the Oracle Technology Network (OTN).

• Copy the same files that are in the packages from an Oracle Database 10g Client Administrator installation.

Both the SQL*Plus and OCI packages must be from the same Oracle Database version, for example, 10.2.0.1.

Basic Instant Client

SQL*Plus Instant Client using the Basic OCI package works with any NLS_LANG setting supported by the Oracle Database. It supports all character sets and language settings available in the Oracle Database.

Lightweight Instant Client

SQL*Plus Instant Client using the lightweight OCI package displays error messages in English only and supports only specific character sets. It is significantly smaller than SQL*Plus Instant Client using the Basic OCI package.

Valid values for NLS_LANG parameters with the lightweight Instant Client are:

• language must always be American.

• territory can be any valid territory supported by the Oracle Database.

• charset is one of the following character sets:

  • US7ASCII

  • WE8DEC

  • UTF8

  • AL16UTF16

  • AL32UTF8

For example:

See the Oracle Database Globalization Support Guide, and NLS_LANG Environment Variable for more information about NLS settings.

Lightweight SQL*Plus Instant Client Error with Unsupported Character Set

Attempting to start SQL*Plus Instant Client with an unsupported character set will fail with the following error:

Installing SQL*Plus Instant Client by Downloading from OTN

The OTN downloads for Linux are RPM packages. The OTN downloads for UNIX and Windows are zip files.

The SQL*Plus Instant Client package should never be installed on an ORACLE_HOME.

Installing SQL*Plus Instant Client from Linux RPM Packages

1. Download the RPM packages containing the SQL*Plus Instant Client package, and the OCI package from the OTN Instant Client page at http://www.oracle.com/technology/tech/oci/instantclient/instantclient.html. Both packages must be from the same version such as 10.2.0.1.

2. Use rpm -i for the initial install of the RPM packages, or rpm -u to upgrade to a newer version of the packages.

3. Configure SQL*Plus Instant Client. See Configuring SQL*Plus Instant Client.

Installing SQL*Plus Instant Client from the UNIX or Windows Zip Files

1. Download the zip files containing the SQL*Plus Instant Client package, and the OCI package from the OTN Instant Client page at http://www.oracle.com/technology/tech/oci/instantclient/instantclient.html. Both packages must be from the same version such as 10.2.0.1.

2. Create a new directory, for example, /home/instantclient10_2 on UNIX or c:instantclient10_2 on Windows.

3. Unzip the two packages into the new directory.

4. Configure SQL*Plus Instant Client. See Configuring SQL*Plus Instant Client.

List of Files Required for SQL*Plus Instant Client

Tables E-1, E-2 and E-3 list the required files from each of the SQL*Plus and OCI packages. The files from only one of the OCI packages are required. Other files installed that are not listed here can be ignored, or can be removed to save disk space.

Table E-1 Instant Client Files in the SQL*Plus Package

Table E-2 Instant Client Files in the Basic OCI Package

Oracle Others Driver Download For Windows 10 Bit

Table E-3 Instant Client Files in the Lightweight OCI Package

Installing SQL*Plus Instant Client from the 10g Client Release Media

1. Run the installer on the Oracle Database 10g Client Release media and choose the Administrator option.

2. Create a new directory, for example, /home/instantclient10_2 on UNIX and Linux, or c:instantclient10_2 on Windows.

3. Copy the SQL*Plus Instant Client and the OCI Instant Client files to the new directory. All files must be copied from the same ORACLE_HOME.

   See Installing SQL*Plus Instant Client on UNIX or Linux or Installing SQL*Plus Instant Client on Windows for a list of the files to copy.

4. Configure SQL*Plus Instant Client. See Configuring SQL*Plus Instant Client.

Installing SQL*Plus Instant Client on UNIX or Linux

To install SQL*Plus Instant Client using the Basic OCI package on UNIX and Linux, copy the following files:

To install SQL*Plus Instant Client using the lightweight OCI package on UNIX and Linux, copy the following files:

Installing SQL*Plus Instant Client on Windows

To install SQL*Plus Instant Client using the Basic OCI package on Windows, copy the following files:

To install SQL*Plus Instant Client using the lightweight OCI package on Windows, copy the following files:

Configuring SQL*Plus Instant Client

The SQL*Plus Instant Client executable should only be used with the matching version of the OCI Instant Client.

Note that no ORACLE_HOME or ORACLE_SID environment variables need to be set.

Configuring SQL*Plus Instant Client on Linux (from RPMs)

The RPMs downloaded from OTN install into Oracle specific sub-directories in the /usr file system. The sub-directory structure enables multiple versions of Instant Client to be available.

1. Add the name of the directory containing the Instant Client libraries to LD_LIBRARY_PATH. Remove any other Oracle directories.

   For example, to set LD_LIBRARY_PATH on Solaris in the Bourne or Korn shells:

2. Make sure the sqlplus executable installed from the RPM is the first found in your PATH. To test, enter which sqlplus which should return /usr/bin/sqlplus. If not, remove any other Oracle directories from PATH, or put /usr/bin before other SQL*Plus executables in PATH, or use an absolute or relative path to start SQL*Plus.

   For example, to set PATH in the bash shell:

   If you install multiple versions of SQL*Plus, you may need to change the symbolic link /usr/bin/sqlplus to the version of SQL*Plus matching the libraries in LD_LIBRARY_PATH. For 10.2.0.1, /usr/bin/sqlplus is a symbolic link to the SQL*Plus binary at /usr/lib/oracle/10.2.0.1/client/bin/sqlplus.

3. Set SQLPATH to the directory containing glogin.sql. For example:

4. Set Oracle globalization variables required for your locale. A default locale will be assumed if no variables are set. See the Oracle Database Globalization Support Guide for more information.

   For example:

Configuring SQL*Plus Instant Client on Linux (from Client Media or Zip File) and UNIX

1. Add the name of the directory containing the Instant Client files to the appropriate shared library path LD_LIBRARY_PATH, LIBPATH or SHLIB_PATH. Remove any other Oracle directories.

   For example on Solaris in the Bourne or Korn shells:

2. Add the directory containing the Instant Client files to the PATH environment variable. If it is not set, then an absolute or relative path must be used to start SQL*Plus. Remove any other Oracle directories from PATH. For example:

3. Set SQLPATH to the directory containing the Instant Client files so glogin.sql can be found. For example:

4. Set Oracle globalization variables required for your locale. A default locale will be assumed if no variables are set. See the Oracle Database Globalization Support Guide for more information.

   For example:

Configuring SQL*Plus Instant Client on Windows

The environment may be configured using SET commands in a Windows command prompt or made permanent by setting Environment Variables in System Properties.

Oracle Others Driver Download For Windows 10 Pro

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

1. Add the directory containing the Instant Client files to the PATH system environment variable. Remove any other Oracle directories from PATH.

   For example, add c:instantclient10_2 to the beginning of PATH.

2. Set the user environment variable SQLPATH to the directory containing the Instant Client files so glogin.sql is found.

   For example, create a user variable SQLPATH set to c:instantclient.

3. Set Oracle globalization variables required for your locale. A default locale will be assumed if no variables are set. See the Oracle Database Globalization Support Guide for more information. For example, to set NLS_LANG for a Japanese environment, create a user environment variable NLS_LANG set to JAPANESE_JAPAN.JA16EUC.

   If you have installed the lightweight Instant Client, see Lightweight Instant Client for information about supported NLS_LANG settings.

Connecting to a Database with SQL*Plus Instant Client

SQL*Plus Instant Client is always 'remote' from any database server. To connect to a database you must specify the database using an Oracle Net connection identifier.

An example using an Easy Connection identifier to connect to the HR schema in the MYDB database running on mymachine is:

Alternatively you can use a Net Service Name:

Net Service Names can be stored in a number of places, including LDAP. The use of LDAP is recommended to take advantage of the new features of Oracle Database 10g. See the Oracle Database Net Services Reference for more information.

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. For example, on UNIX, if your tnsnames.ora file is in /home/user1 and it defines the Net Service Name MYDB2:

If TNS_ADMIN is not set, then an operating system dependent set of directories is examined to find tnsnames.ora. This search path includes looking in the directory specified by the ORACLE_HOME environment variable for network/admin/tnsnames.ora. This is the only reason to set the ORACLE_HOME environment variable for SQL*Plus Instant Client. If ORACLE_HOME is set when running Instant Client applications, it must be set to a directory that exists.

This example assumes the ORACLE_HOME environment variable is set, and the $ORACLE_HOME/network/admin/tnsnames.ora or %ORACLE_HOME%networkadmintnsnames.ora file defines the Net Service Name MYDB3:

The TWO_TASK (on UNIX) or LOCAL (on Windows) environment variable can be set to a connection identifier. This removes the need to explicitly enter the connection identifier whenever a connection is made in SQL*Plus or SQL*Plus Instant Client. This UNIX example connects to the database known as MYDB4:

On Windows, TNS_ADMIN and LOCAL may be set in the System Properties. See Configuring SQL*Plus Instant Client on Windows.

AS SYSDBA or AS SYSOPER Connections with SQL*Plus Instant Client

To connect AS SYSDBA or AS SYSOPER to perform DBA tasks, you need to set up an Oracle password file on the database server using the database's orapwd utility. Once this is configured, your SQL*Plus Instant Client connection string might look something like:

See the Oracle Database Administrator's Guide for information on Oracle password files.

Uninstalling Instant Client

The SQL*Plus Instant Client package can be removed separately from the OCI Instant Client. After uninstalling the SQL*Plus Instant Client package, the remaining OCI Instant Client libraries enable custom written OCI programs or third party database utilities to connect to a database.

Uninstalling SQL*Plus Instant Client

1. For installations on Linux from RPM packages, use rpm -e only on the SQL*Plus Instant Client package

   or

   For installations on UNIX and Windows, and installations on Linux from the Client Release media, manually remove the following SQL*Plus specific files:

   Table E-4 Instant Client Files in the SQL*Plus Package

   UNIX	Windows	Description
   sqlplus	sqlplus.exe	SQL*Plus executable
   glogin.sql	glogin.sql	SQL*Plus site profile
   libsqlplus.so	not applicable	SQL*Plus library
   libsqlplusic.so	orasqlplusic10.dll	SQL*Plus data shared library

   
   

2. Reset environment variables and remove tnsnames.ora if necessary.

Uninstalling the Complete Instant Client

1. For installations on Linux from RPM packages, use rpm -qa to find the SQL*Plus Instant Client and Basic OCI package names and run rpm -e to remove them

   or

   For installations on UNIX and Windows, and installations on Linux from the Client Release media, manually delete the directory containing the SQL*Plus executable, Oracle libraries and glogin.sql.

   See Installing SQL*Plus Instant Client from the 10g Client Release Media for a list of the files you copied to the directory.

2. Reset environment variables such as PATH, SQLPATH, LD_LIBRARY_PATH and TNS_ADMIN.

3. Remove tnsnames.ora if necessary.

Symptoms

Your CD or DVD drive is not seen in File Explorer (called Windows Explorer in Windows 7 and earlier versions of Windows), and the device is marked with a yellow exclamation point in Device Manager. Additionally, after you open the device's Properties dialog box, one of the following errors is listed in the Device status area:

• Windows cannot start this hardware device because its configuration information (in the registry) is incomplete or damaged. (Code 19)

• The device is not working properly because Windows cannot load the drivers required for this device. (Code 31)

• A driver (service) for this device has been disabled. An alternate driver may be providing this functionality. (Code 32)

• Windows cannot load the device driver for this hardware. The driver may be corrupted or missing. (Code 39)

• Windows successfully loaded the device driver for this hardware but cannot find the hardware device. (Code 41)

This issue may have occurred after one of the following situations:

Oracle Others Driver Download For Windows 10 64-bit

• You upgrade the Windows operating system.

• You install or uninstall CD or DVD recording programs.

• You uninstall Microsoft Digital Image.

There are various reasons why a CD or DVD drive is not detected. The resolutions that are listed in this article may help solve some instances but not all instances of this problem. You may also need to contact your hardware manufacturer for assistance with your hardware.

Resolution

For each of the following methods, click on the header, and it will open to show you more info:

Oracle Others Driver Download For Windows 10 32-bit

Method 1: Windows 7 and 8.1 - Use the Hardware and Devices troubleshooter

For Windows 10, skip to Method 2.

In Windows 7 and 8.1, to open the Hardware and Devices troubleshooter, follow these steps:

1. Press the Windows logo key + R to open the Run dialog box.

2. Type control in the Run dialog box, then press Enter.

3. In the Search box in Control Panel, type troubleshooter, and then click Troubleshooting.

4. Under the Hardware and Sound item, click Configure a device. If you are prompted to enter an administrator password or provide confirmation, type the password or provide confirmation.

If your problem is not solved, try the next method.

Method 2: Check BIOS settings and chipset drivers

1. Verify the drive is activated in the BIOS. BIOS systems vary by device. If you are not sure how to verify the drive settings in your device’s BIOS, contact the manufacturer of your device.

2. Also, verify with the manufacturer of the computer if the drive came with it, or the manufacturer of the drive if it was purchased separately that the chipset drivers for the device are current.

If your problem is not solved, try the next method.

Method 3: Update or reinstall the driver

To update the driver, search for the driver on the device manufacturer's website, and then follow the installation instructions on the website.
To reinstall the driver, follow these steps:

1. Press the Windows logo key + R to open the Run dialog box.

2. Type devmgmt.msc in the Run dialog box, then press Enter. If you are prompted for an administrator password or for a confirmation, type the password, or select Allow

3. In Device Manager, expand DVD/CD-ROM drives, right-click the CD and DVD devices, and then select Uninstall.

4. When you are prompted to confirm that you want to remove the device, select OK.

5. Restart the computer.

After the computer restarts, the drivers will be automatically installed.
If your problem is not solved, try the next method.

Method 4: Remove and reinstall IDE/ATAPI drivers

To remove and reinstall IDE/ATAPI driver, follow these steps:

1. From Start, search for Device Manager. Open Device Manager from the search results, and select the View menu. Choose Show Hidden Devices.

2. Expand IDE/ATAPI Controllers, and then:

   • Select and right-click ATA Channel 0, and then click Uninstall

   • Select and right-click ATA Channel 1, and then click Uninstall

   • Select and right-click Standard Dual Channel PCI IDE Controller, and then click Uninstall

   • If there are additional entries, right-click them and then choose Uninstall

3. Reboot the device.

After the computer restarts, the drivers will be automatically installed.
If your problem is not solved, try the next method.

Method 5: Fix corrupted registry entries

This problem may be caused by two Windows registry entries that have become corrupted. To use Registry Editor to delete the corrupted Registry entries, follow these steps:

1. Press the Windows logo key + R to open the Run dialog box.

2. Type regedit in the Run dialog box, then press Enter. If you are prompted for an administrator password or for a confirmation, type the password, or select Allow

3. In the navigation pane, locate and then select the following registry subkey:

   HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlClass{4D36E965-E325-11CE-BFC1-08002BE10318}

4. In the right pane, select UpperFilters.
   Note You may also see an UpperFilters.bak registry entry. You do not have to remove that entry. Click UpperFilters only. If you do not see the UpperFilters registry entry, you still might have to remove the LowerFilters registry entry. To do this, go to step 7.

5. On the Edit menu, select Delete.

6. When you are prompted to confirm the deletion, select Yes.

7. In the right pane, select LowerFilters.
   Note If you do not see the LowerFilters registry entry, go to the next method.

8. On the Edit menu, select Delete.

9. When you are prompted to confirm the deletion, select Yes.

10. Exit Registry Editor.

11. Restart the computer.

Note: To use this method, you must be logged on to Windows as an administrator. To verify that you are signed in as an administrator, bring up the Control Panel, select User Accounts, and then choose Manage User Accounts.
Important:

• Follow the steps in this section carefully. Serious problems might occur if you modify the registry incorrectly. Before you modify it, back up the registry for restoration in case problems occur.

• After trying this method, some apps, such as CD or DVD recording software, might not work correctly. If so, try uninstalling and reinstalling the affected app. Check with the creator of the app to see if there is an updated version.

If your problem is not solved, try the next method.

Method 6: Create a registry subkey

To create the registry subkey, follow these steps:

1. Press the Windows logo key + R to open the Run box.

2. Type regedit in the Run box, then press Enter. If you are prompted for an administrator password or for a confirmation, type the password, or select Allow.

3. In the navigation pane, locate the following registry subkey:

   HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServicesatapi

4. Right-click atapi, point to New, then select Key.

5. Type Controller0, and then press Enter.

6. Right-click Controller0, point to New, and then select DWORD(32-bit) Value .

7. Type EnumDevice1, and then press Enter.

8. Right-click EnumDevice1, select Modify....

9. Type 1 in the Value data box, and then select OK.

10. Exit Registry Editor.

11. Restart the computer.

Notes

• To use this method, you must be logged on to Windows as an administrator. To verify that you are signed in as an administrator, bring up the Control Panel, select User Accounts, and then choose Manage User Accounts.

• This method should be used on Windows 7, Windows 8 or 8.1, or Windows 10 version 1507. The issues fixed by this method shouldn’t occur in Windows 10 1511 or later.

Important: Follow the steps in this method carefully. Serious problems might occur if you modify the registry incorrectly. Before you modify it, back up the registry for restoration in case problems occur.