Oracle client ��� linux

Oracle client ��� linux

Your search did not match any results.

We suggest you try the following to help find what you’re looking for:

• Check the spelling of your keyword search.
• Use synonyms for the keyword you typed, for example, try “application” instead of “software.”
• Try one of the popular searches shown below.
• Start a new search.

Free, light-weight, and easily installed Oracle Database tools, libraries and SDKs

Oracle Instant Client enables development and deployment of applications that connect to Oracle Database, either on-premise or in the Cloud. The Instant Client libraries provide the necessary network connectivity and advanced data features to make full use of Oracle Database. The libraries are used by the Oracle APIs of popular languages and environments including Python, Node.js, Go, PHP and Ruby, as well as providing access for Oracle Call Interface (OCI), Oracle C++ Call Interface (OCCI), JDBC OCI, ODBC and Pro*C applications. Tools included in Instant Client, such as SQL*Plus, SQL*Loader and Oracle Data Pump, provide quick and convenient data access.

Oracle Instant Client

What’s New

Oracle Linux has Instant Client RPMs

Instant Client RPM packages for Oracle Linux can now be installed from yum.oracle.com for Oracle Linux 8 and Oracle Linux 7. Older releases are available for Oracle Linux 8, Oracle Linux 7 and Oracle Linux 6.

See Instant Client for Oracle Linux for installation instructions.

Instant Client is available for Docker

Dockerfiles are available on GitHub. Pre-built images are available from the GitHub Container Registry.

Instant Client Features

• Free to download, deploy and distribute
• Small footprint
• ZIPs available for quick, one-step install
• RPM Packages also available for Linux, and DMG Packages for macOS Intel x86
• Same libraries as full Oracle Database or Oracle Client
• Includes tools such as SQL*Plus, SQL*Loader and Data Pump
• Widely used and tested

Instant Client applications are cloud ready

Deploy applications using Instant Client in the cloud, or connect to a cloud database.

Whether your applications are in the cloud or on-premise, you can install Instant Client and connect to cloud databases. Follow the normal installation process for your operating system. Some cloud-specific references are shown below.

Источник

Oracle client ��� linux

Learn how to install Oracle Instant Client by downloading the RPMs and using the yum install command.

Starting with 19c, by default, you can install only one version of the Oracle Instant Client RPM packages at a time. If you need multiple versions, use the Oracle Instant Client zip files.

Removing Earlier Oracle Instant Client Installations

Remove any earlier installations of Oracle Instant Client using yum before you start a fresh installation.

List the currently installed Oracle Instant Client packages. For example:

For Oracle Linux 7:

For Oracle Linux 8:

The output will be like:

Remove the Oracle Instant Client packages. For example:

For Oracle Linux 7:

For Oracle Linux 8:

Remove the legacy Oracle Instant Client yum repository setup package. For example:

For Oracle Linux 7:

For Oracle Linux 8:

A reboot is not required.

Installing Oracle Instant Client From the yum Server

If you are using Oracle Linux and have configured your Oracle Linux yum server, then you can install Oracle Instant Client using the yum install command.

Install the Oracle Linux release package to configure repository definitions for Oracle Instant Client:

For Oracle Linux 7:

For Oracle Linux 8:

Go to the Oracle Instant Client repositories to view the available Oracle Instant Client packages:

For Oracle Linux 7:

For Oracle Linux 8:

All installations require a Basic or Basic Light package. All other packages are optional.

Install Oracle Instant Client packages using yum .

For Oracle Linux 7:

For Oracle Linux 8:

To install other Oracle Instant Client packages like SQL*Plus, run:

For Oracle Linux 7:

For Oracle Linux 8:

Using versionlock to Avoid Upgrades

To ensure that you do not inadvertently upgrade Oracle Instant Client when a new major release is published, use yum versionlock after you have installed Oracle Instant Client 21c.

For Oracle Linux 7:

For Oracle Linux 8:

Configuring yum versionlock still allows automatic Oracle Instant Client release updates to 21.2, 21.3, and so on.

Manually Downloading and Installing Oracle Instant Client RPM Packages

An alternative method for installing Oracle Instant Client is to manually download and install the Oracle Instant Client packages.

Go to the Oracle Instant Client Downloads page:

Download the desired Oracle Instant Client RPM packages. Select the correct platform, architecture, and packages of your choice. For example, if your application is 64-bit, then ensure that you select 64-bit Instant Client and download the Basic Package RPM file.

All installations require a Basic or Basic Light package. All other packages are optional.

Install the packages using yum .

For Oracle Linux 7:

For Oracle Linux 8:

Additionally, you may have to perform the following tasks before you start your application:

If you intend to colocate optional Oracle configuration files such as tnsnames.ora , sqlnet.ora , ldap.ora , or oraaccess.xml with Oracle Instant Client, then move these files to the /usr/lib/oracle/21/client64/lib/network/admin subdirectory.

This is the default Oracle configuration directory for applications linked with this Oracle Instant Client.

Alternatively, you can move the Oracle configuration files to another, accessible directory. Then set the environment variable TNS_ADMIN to that directory name.

To use binaries from the tools package, use yum or dnf to install the package and then update your PATH environment variable. For example:

Источник

Oracle client ��� linux

Oracle Instant Client provides the necessary Oracle Database client-side files to create and run OCI, OCCI, ODBC, and JDBC OCI applications. Useful command-line utilities including SQL*Plus, SQL*Loader and Oracle Data Pump are also available. Oracle Instant Client simplifies the deployment of applications by eliminating the need for an Oracle home on the client machines.

The storage space requirement of an OCI application running in Instant Client mode is significantly reduced compared to the same application running in a full client-side installation. A minimal install of Instant Client shared libraries can occupy less than 10% of the space of a full client-side installation. Finally, the Instant Client is easy to install.

Why use Instant Client?

Installation involves unzipping a few files, or installing RPM packages.

The Oracle Database client-side number of required files and the total disk storage are significantly reduced.

There is no loss of functionality or performance for applications deployed using Instant Client.

It is simple for independent software vendors to package applications.

A README file is included with the Instant Client installation. It describes the version, date and time, and the operating system the Instant Client was generated on.

OCI applications, by default, look for the OCI Data Shared Library, libociei.so (or Oraociei18.1.dll on Windows) in the runtime library search path (for example LD_LIBRARY_PATH on Linux, or PATH on Windows) to determine if the application should operate in the Instant Client mode. If this library is not found, then OCI tries to load the Instant Client Light Data Shared Library (see Table 2-3 and Table 2-4), libociicus.so (or Oraociicus18.1.dll on Windows). If the Instant Client Light library is found, then the application operates in the Instant Client Light mode. Otherwise, a full installation based on Oracle home is assumed.

For Instant Client, the following tables shows the Oracle Database client-side files required to deploy an OCI application for Linux and UNIX and Microsoft Windows. Other libraries and utilities get installed, but are not needed for OCI runtime use. For example, you can delete files such as jdbc.jar .

Table 2-1 Instant Client Shared Libraries for Linux and UNIX

Client Code Library

OCI Instant Client Data Shared Library

Oracle Notification Service (ONS) library

Light Weight IPC Library

Message Queue Light Library

The libraries libclntsh.so.18.1, libclntshcore.so.18.1, and libociei.so must reside in the same directory in order to use Instant Client.

Table 2-2 Instant Client Shared Libraries for Microsoft Windows

Linux and UNIX	Description for Linux and UNIX

Forwarding functions that applications link with

ONS library used by OCI internally

Oracle Database 18 c library names are used in the table and are current for Oracle Database release 18c, version 18.1.

On Microsoft Windows, a .sym file is provided for each dynamic-link library (DLL). When the .sym file is present in the same location as the DLL, a stack trace with function names is generated when a failure occurs in OCI on Microsoft Windows.

In general, all OCI functionality is available to an application being run using the Instant Client, except that the Instant Client is for client-side operation only. Therefore, server-side external procedures cannot use Instant Client libraries.

For development you can also use the Instant Client SDK.

Install from ZIP Files, from RPMs, and from Oracle Universal Installer

Oracle Instant Client can be installed in several ways.

The Instant Client libraries can be installed by either choosing the Instant Client option from Oracle Universal Installer or by downloading and installing either the ZIP files or RPMs from the OCI page on the Oracle Technology Network website: Oracle Instant Client

To Download and Install the Instant Client Libraries from the Oracle Technology Network Website

The following steps are for the Linux, Unix, and Windows environments.

From the Oracle Technology Network , download and unzip the required ZIP packages from OTN to an empty directory, such as instantclient_18_1 , for Oracle Database release 18c, version 18.1. All Instant Client ZIP installs require the Basic or Basic Light package.

Become root by running su and entering the super-user password.

Change to the directory in which you want to install.

Uninstall any earlier installations.

Install each package with yum. Yum will automatically install required dependencies, such as libaio .

Or, install each package with rpm.

Delete the .rpm files if you want to save disk space.

Exit the root shell. No need to reboot.

On Windows, set PATH to the instantclient_18_1 directory. For example, on Windows 7, update PATH in Control Panel -> System -> Advanced System Settings -> Advanced -> Environment Variables -> System Variables -> PATH.

If necessary, set the NLS_LANG environment variable to specify the language and territory used by the client application and database connections opened by the application, and the client’s character set, which is the character set for data entered or displayed by a client program. NLS_LANG is set as an environment variable on UNIX platforms and is set in the registry on Windows platforms. See Oracle Database Globalization Support Guide for more information on setting the NLS_LANG environment variable.

If you intend to co-locate optional Oracle client configuration files such as tnsnames.ora , sqlnet.ora , ldap.ora , or oraaccess.xml with Instant Client, then put them in the network/admin subdirectory of Instant Client. This is the default Oracle client configuration directory for applications linked with Instant Client. Alternatively, Oracle client configuration files can be put in another, accessible directory. Then set the environment variable TNS_ADMIN to that directory name.

After completing the preceding steps you are ready to run OCI applications.

The OCI application uses the Instant Client when the OCI shared libraries are accessible through the operating system Library Path variable. In this way, there is no dependency on the Oracle home and none of the other code and data files provided in the Oracle home are needed by OCI.

Install the Instant Client from the Oracle Universal Installer

For Oracle Universal Installer , invoke the Oracle Universal Installer and select the Instant Client option and install the Instant Client shared libraries to an empty directory, such as instantclient_18_1 , for Oracle Database release 18c, version 18.1.

If you did a complete client installation (by choosing the Admin option in Oracle Universal Installer), the locations of the Instant Client shared libraries in a full client installation are:

On Linux or UNIX:

libociei.so library is in $ORACLE_HOME/instantclient

libclntsh.so.18.1 , libclntshcore.so.18.1 , and libnnz18.so are in $ORACLE_HOME/lib

oraociei18.dll library is in ORACLE_HOME\instantclient

oci.dll , ociw32.dll , and orannzsbb18.dll are in ORACLE_HOME\bin

To enable running the OCI application using Instant Client, copy the preceding libraries to a different directory and set the operating system shared library path to locate this directory.

All the libraries must be copied from the same Oracle home and must be placed in the same directory. Co-location of symlinks to Instant Client libraries is not a substitute for physical co-location of the libraries.

There should be only one set of Oracle libraries on the operating system Library Path variable. That is, if you have multiple directories containing Instant Client libraries, then only one such directory should be on the operating system Library Path.

Similarly, if an Oracle home-based installation is performed on the same system, then you should not have ORACLE_HOME/lib and the Instant Client directory on the operating system Library Path simultaneously regardless of the order in which they appear on the Library Path. That is, either the ORACLE_HOME/lib directory (for non-Instant Client operation) or Instant Client directory (for Instant Client operation) should be on the operating system Library Path variable, but not both.

To enable other capabilities such as OCCI and JDBC OCI, you must copy a few additional files. To enable OCCI, you must install the OCCI Library ( libocci.so.18.1 on Linux or UNIX and oraocci18.dll on Windows) in the Instant Client directory. For the JDBC OCI driver, in addition to the three OCI shared libraries, you must also download OCI JDBC Library (for example libocijdbc18.so on Linux or UNIX and ocijdbc18.dll on Windows). Place all libraries in the Instant Client directory.

On hybrid platforms, such as Sparc64, to operate the JDBC OCI driver in the Instant Client mode, copy the libociei.so library from the ORACLE_HOME/instantclient32 directory to the Instant Client directory. Copy all other Sparc64 libraries needed for the JDBC OCI Instant Client from the ORACLE_HOME/lib32 directory to the Instant Client directory.

Environment Variables for Oracle Instant Client

The ORACLE_HOME environment variable no longer determines the location of NLS, CORE, and error message files.

An OCI-only application should not require ORACLE_HOME to be set. However, if it is set, it does not affect OCI. OCI always obtains its data from the Data Shared Library. If the Data Shared Library is not available, only then is ORACLE_HOME used and a full client installation is assumed. Though ORACLE_HOME is not required to be set, if it is set, then it must be set to a valid operating system path name that identifies a directory.

If Dynamic User callback libraries are to be loaded, then as this guide specifies, the callback package must reside in ORACLE_HOME/lib ( ORACLE_HOME\bin on Windows). Set ORACLE_HOME in this case.

Environment variables ORA_NLS10 and ORA_NLS_PROFILE33 are ignored in the Instant Client mode.

Beginning with Oracle Database 12 c Release 2 (12.2), when using Instant Client libraries, the Instant Client can use the ORA_TZFILE environment variable to read the time zone file from the file system when this environment variable is set. Otherwise, if the ORA_TZFILE variable is not set, then the larger, default, timezlrg_ n .dat file from the Data Shared Library is used. If the smaller timezone_ n .dat file is to be used from the Data Shared Library, then set the ORA_TZFILE environment variable to the name of the file without any absolute or relative path names. The file must be copied to subdirectory oracore/zoneinfo for (UNIX/LINUX) or oracore\zoneinfo for (Microsoft Windows) in the instant client directory. You can use the genezi utility with the -v option to verify that the time zone file and location is valid or run SQL*Plus.

On Linux or UNIX:

In these examples, n is the time zone data file version number.

Be sure to create subdirectory oracore/zoneinfo for (UNIX/LINUX) or subdirectory oracore\zoneinfo for (Microsoft Windows) where oracoei or oraociicus DLL’s are located (typically in the instantclient_12_2 directory) and copy the timezone_ n .dat file to this directory.

To determine the versions of small and large time zone files that are packaged in the Instant Client Data Shared Library, enter the following command to run the genezi utility:

If OCI is not operating in the Instant Client mode (because the Data Shared Library is not available), then ORA_TZFILE variable, if set, names a complete path name as it does in previous Oracle Database releases.

If TNSNAMES local naming parameters are used, then, as mentioned earlier, TNS_ADMIN directory must contain the TNSNAMES configuration files. If TNS_ADMIN is not set, then the ORACLE_HOME/network/admin directory must contain Oracle Net Services configuration files.

Database Connection Strings for Oracle Instant Client

All Oracle Net naming methods that do not require use of ORACLE_BASE_HOME , or ORACLE_HOME (to locate configuration files such as tnsnames.ora , sqlnet.ora , or oraaccess.xml ) work in the Instant Client mode.

If you intend to co-locate optional Oracle configuration files such as tnsnames.ora , sqlnet.ora , ldap.ora , or oraaccess.xml with Instant Client, note that beginning with Oracle Database release 18c, version 18.1 Instant Client Basic and Basic Light Zips and RPMs precreate a network/admin directory, where these files can be placed. In earlier releases, users had to create the network/admin directory themselves.

See Database Connection Strings for complete information about database connection strings.

Oracle Database Net Services Administrator’s Guide chapter on «Configuring Naming Methods» for more about connect descriptors

SDK for Oracle Instant Client

The software development kit (SDK) is a set of development tools that allows the creation of applications can be downloaded from the Instant Client link URL on the Oracle Technology Network website:

The Instant Client SDK package has both C and C++ header files and a makefile for developing OCI and OCCI applications while in an Instant Client environment. Developed applications can be deployed in any client environment.

The SDK contains C and C++ demonstration programs.

On Windows, libraries required to link the OCI or OCCI applications are also included. Make.bat is provided to build the demos.

On UNIX or Linux, the makefile demo.mk is provided to build the demos. The instantclient_18_1 directory must be in the runtime library search path, for example LD_LIBRARY_PATH before linking the application. The OCI and OCCI programs require the presence of libclntsh.so and libocci.so symbolic links in the instantclient_18_1 directory. Beginning with Oracle Database 18c, version 18.1, Instant Client Basic and Basic Light ZIP files on Linux, Unix, and macOS now have the libclntsh and libocci symbolic links precreated.

The SDK also contains the Object Type Translator (OTT) utility and its classes to generate the application header files.

About Oracle Instant Client Light

The Instant Client Light version of Instant Client further reduces the disk space requirements of the client installation.

The size of the library has been reduced by removing error message files for languages other than English and leaving only a few supported character set definitions out of around 250.

This Instant Client Light version is geared toward applications that use either US7ASCII, WE8DEC, WE8ISO8859P1, WE8MSWIN1252, or a Unicode character set. There is no restriction on the LANGUAGE and the TERRITORY fields of the NLS_LANG setting, so the Instant Client Light operates with any language and territory settings. Because only English error messages are provided with the Instant Client Light, error messages generated on the client side, such as Net connection errors, are always reported in English, even if NLS_LANG is set to a language other than AMERICAN . Error messages generated by the database side, such as syntax errors in SQL statements, are in the selected language provided the appropriate translated message files are installed in the Oracle home of the database instance.

Источник

Microsoft Windows	Description for Microsoft Windows