Описанный в предыдущем разделе процесс установки ПО Oracle Client требует выполнения подготовительных действий, необходимых для установки регулярного программного обеспечения Oracle Database Server.
К счастью, инсталляция полного программного обеспечения Oracle Client для подключения к базе данных Oracle может требоваться не всегда. Новое программное обеспечение Oracle Instant Client позволяет запускать приложения без установки стандартного ПО Oracle Client или наличия каталога ORACLE_HOME. Программное обеспечение Oracle Client не обязательно инсталлировать на каждом компьютере, которому необходим доступ к базе данных Oracle. Все существующие приложения OCI, ODBC и JDBC будут работать с Instant Client (Мгновенный клиент). При желании с ним можно даже использовать интерфейс SQL*Plus.
Instant Client предоставляет следующие преимущества по сравнению с полномасштабным ПО Oracle Client.
Установка Instant Client
Чтобы установить новое программное обеспечение Instant Client и быстро подключиться к базе данных Oracle, выполните следующие действия.
Где скачать Oracle Instant Client
Как мы уже говорили, Instant Client является бесплатным и совершенно открыто распространяется корпорацией Oracle. Вы можете его скачать по этой ссылке. Как видите, клиент есть для различных операционных систем с различной битностью.
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
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 Database и Microsoft SQL Server Integration Services я собрал 2 FAQ-а. Первый — по Oracle Client — я публикую здесь, а второй — по коннекторам SSIS к Oracle, следующим постом.
Что такое Oracle Client?
Это промежуточное ПО, предназначенное для доступа к Oracle Database. Некоторые приложения имеют встроенного клиента. Встраиваемый клиент, предназначенный для разработчиков, называется Instant Client.
Откуда скачать Oracle Client?
Если Вы возьмете клиента от более старшей версии это будет плюсом, поскольку не придется его обновлять на работающей системе, когда потребуется соединяться со следующей СУБД Oracle.
Не перепутайте Oracle Client и Oracle Instant Client, предназначенный для разработчиков. Так же, не качайте Data Access Components, поскольку DAC, помимо Oracle Client, содержит много средств, нужных только для разработки приложений.
Установка клиента Oracle 12c 32-bit не проходит после установки Oracle 12c 64-bit клиента (или наоборот)
Если Вы только что установили одного из клиентов Oracle 12c и не перезагружались, перезагрузитесь.
Программа установки Oracle Client, называемая Oracle Universal Installer, создает службу OracleRemExecService, которая согласно неофициальному описанию нужна только для OUI и должна исчезнуть после перезагрузки. В реальности она не исчезает, но и не запускается при старте ПК. Является ли правильным остановить службу, я не знаю, но это тоже помогает.
Как настроить подключение к СУБД Oracle в приложении, использующем Oracle Client?
Со стороны прикладного программного обеспечения, работающего через Oracle Client, для указания БД может быть использовано имя сервиса TNS или строка конфигурации, содержащая часть объявления имени сервиса TNS.
В первом случае в папке Oracle Client в «\network\admin\tnsnames.ora» укажите:
При этом, в приложениях в поле TNS Service Name указывается имя подключения.
Следует иметь ввиду, что в приложении, запускаемом в 32-х битной среде, используется Oracle Client 32-bit, а в 64-х битной среде используется Oracle Client 64-bit, поэтому может потребоваться сделать «tnsnames.ora» в обоих клиентах.
Что такое SERVICE_NAME и SID?
Подключение к базе данных по сети со стороны сервера обслуживает промежуточное ПО, называемое Listener.
SID это уникальный идентификатор базы данных Oracle на машине, а SERVICE_NAME, это идентификатор базы данных, заданный в Listener. Таким образом, одна и та же база данных, может быть доступна под разными SERVICE_NAME, но только под одним SID. Вас, поскольку Вы находитесь снаружи Listener-а, волнует SERVICE_NAME.
Как адресовать таблицы в Oracle?
По-умолчанию пользователь Oracle обращается к таблицам в своей схеме. Для того, что бы запрос обращался к одним и тем же таблицам из под любого пользователя, нужно указывать имя схемы перед точкой. Например, BM9.BM_CUSTOMER_CONTACT адресует таблицу BM_CUSTOMER_CONTACT в схеме BM9.
Что такое схема и база данных в Oracle?
База данных в СУБД Oracle = отдельный набор процессов СУБД с общей памятью.
Схема содержится внутри базы данных и является контейнером для таблиц. Кроме того, схема = пользователь.
Таблицы с одинаковыми именами могут существовать одновременно в разных схемах.
Почему не удается определить OCI environment (например, в Attunity)?
Приложение использующее Oracle Client должно каким-то образом его найти. Путь установки Oracle Client добавляется в %PATH% Oracle Installer-ом при установке. Но следует иметь ввиду, что переменные окружения устанавливаются процессу при запуске и, к примеру, Visual Studio (BIDS, Data Tools) запущенная до установки клиента, требует перезапуска, что бы начать использовать новый %PATH%.
Эта ошибка может быть по разному сформулирована в других приложениях.
Как настроить символьную кодировку Oracle Client?
Неверно настроенная кодировка может влиять как на получаемые данные, так и на выполнение запросов. Это может проявляться в том, что REPLACE(table_column, ‘А’, ‘Б’) в одном инструменте работает, а в другом нет, потому, что литералы ‘А’ и ‘Б’, поступающие в БД, воспринимаются иначе в одном из инструментов.
Для 32-х разрядного клиента в реестре в [HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\ORACLE] установите параметр «NLS_LANG»=»RUSSIAN_CIS.CL8MSWIN1251» (типа REG_SZ).
Для 64-х разрядного клиента в реестре в [HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE], аналогично, установите параметр «NLS_LANG»=»RUSSIAN_CIS.CL8MSWIN1251» (типа REG_SZ).
После настройки кодировки необходимо перезагрузиться, поскольку, уже запущенный Oracle Client её не перечитает.
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 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 Oraociei19.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 Oraociicus19.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.
Table 2-1 Instant Client Shared Libraries for Linux and UNIX
Linux and UNIX
Description 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 must reside in the same directory in order to use Instant Client.
Table 2-2 Instant Client Shared Libraries for Microsoft Windows
Microsoft Windows
Description for Microsoft Windows
Forwarding functions that applications link with
ONS library used by OCI internally
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.
Installing from the ZIP files
This section describes how to install the Instant Client from the ZIP files.
Alternatively, run the following command to set the LD_LIBRARY_PATH environment variable prior to running the applications:
The variable can be added optionally to the configuration files such as
This is the default Oracle configuration directory for applications linked with the Instant Client.
Alternatively, Oracle configuration files can be placed in another accessible directory and then set the environment variable TNS_ADMIN to that directory name.
Installing from the RPM files
This section describes how to install the Instant Client from the RPM files.
Starting from version 19.3, by default only one version of the Instant Client RPM libraries can be installed at a time.
For Instant Client 19.3 RPM packages, these commands are run automatically.
Alternatively, run the following command to set the LD_LIBRARY_PATH environment variable prior to running the applications:
The variable can optionally be added to configuration files such as
This is the default Oracle configuration directory for applications linked with the Instant Client.
Alternatively, Oracle configuration files can be placed in another accessible directory and then set the environment variable TNS_ADMIN to that directory name.
Installing from the Oracle Universal Installer
This section describes how to install Oracle Instant Client from the Oracle Universal Installer.
See Steps 5 and 6 in Installing from the ZIP files about setting the environment variables.
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:
oraociei19.dll library is in ORACLE_HOME\instantclient
To enable running the OCI application using Instant Client, copy the preceding libraries to a different directory and then 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.19.1 on Linux or UNIX and oraocci19.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 libocijdbc19.so on Linux or UNIX and ocijdbc19.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.
In these examples, n is the time zone data file version number.
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
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_19 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_19 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.
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.
Table 2-1 Instant Client Shared Libraries for Linux and UNIX
Linux and UNIX
Description 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
Microsoft Windows
Description for Microsoft Windows
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.
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.
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.
Or, install each package with rpm.
Exit the root shell. No need to reboot.
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.
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
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:
oraociei18.dll library is in ORACLE_HOME\instantclient
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.
In these examples, n is the time zone data file version number.
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
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.
Описанный в предыдущем разделе процесс установки ПО Oracle Client требует выполнения подготовительных действий, необходимых для установки регулярного программного обеспечения Oracle Database Server.