Copy it to the Server folder. C: Oracle product 11.2.0 Server. Create the connection in IDT. In IDT login to a Respository session. Create New relational connection. Select oracle Client. Or test existing connection, Then check the The Network Layer is the Oracle OCI - This is the type of Oracle Connection expected. Why does Oracle not find oci.dll? Ask Question Asked 4 years. If you are using TOAD, you will need to download the 32-bit version of the Oracle Client Tools. When you create the folder structure for the downloads just write them the old way 'c: oraclient'. Adding OCI Service Broker for Kubernetes to Clusters. Download the JKS Wallet for an Autonomous Database Create a Self-Signed Certificate for a Target Database with Client Authentication Enabled Create a Self-Signed Certificate for a Target Database with Client Authentication Disabled. Here are the most recent additions to Oracle Cloud. Is there a way to use the Qt OCI driver without installing Oracle client? Maybe using static libs from Oracle while we build the driver? Or using some Oracle client dlls and with some env variable setup? The thing is I can't ask my clients to install oracle client before using my application.
Is there a way to use the Qt OCI driver without installing Oracle client ? Maybe using static libs from Oracle while we build the driver? Or using some Oracle client dlls and with some env variable setup?
The thing is I can't ask my clients to install oracle client before using my application. They expect my application to up and running without any hassle.
If this cannot be achieved then what do we have as alternatives?
- OS=Windows 7
- Qt=4.8.6
2 Answers
If anyone interested this is how I have done it.
- Read http://docs.oracle.com/cd/B12037_01/appdev.101/b10779/oci01int.htm#423364 Forget about patching part.
- Download oracle instant client http://www.oracle.com/technetwork/database/features/instant-client/index-097480.html. This is a zip file, no installation required, just extract it application contains. (alternatively we can extract somewhere else and include the location into Path env variable)
- As now we don't have client installed, we don't have a tnsnames.ora file also. So set the ip, port and service name directly. (Alternatively we can use TNS_ADMIN env variable if we want tnsnames.ora file badly) Ex:
- That is it. It should work perfectly.
Meantime, it is legal to distribute the Oracle instant client DLLs.
MorpheusMorpheusWhat do you want to achieve? Are your intentions purely technical or do you have problems with licensing? (Oracle does not allow redistribution of OCI libs). What OS are you using?
On Linux/AIX you can theoretically create you own 'static' version of OCI lib. The dynamic one is called libclntsh (sh - stands for shared). The static one libclntst can be at least build manually by using Oracle's makefiles.Then you can technically embed this static library in your application. You might have some missing symbols (for example __fast_memcpy_A). It's because Oracle was compiled using Intel's ICC compiler and you have also add static version of some ICC's runtime libs.
You can also look at project Tora. There users have to download OCI libs manually and have all ale Oracle specific code is put into separate plugin.
Update: AFAIK Oracle does not allow re-distribution of OCI.DLL unless you are Oracle Business Partner (or however is it called these days).
In case of Windows platform you can use:
Microsoft's ODBC driver for Oracle. It should be present in every Windows installation. But this one is very old and does not support newer>11 gold badge14 silver badges23 bronze badges
Not the answer you're looking for? Browse other questions tagged qtoracle11gqt4oci or ask your own question.
The script content on this page is for navigation purposes only and does not alter the content in any way.
Describes OCI Instant Client and Instant Client Light
This chapter contains the following topics:
2.1 About OCI Instant Client
The Instant Client feature simplifies the deployment of customer applications based on OCI, OCCI, ODBC, and JDBC OCI 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. The Instant Client shared libraries occupy only about one-fourth the disk space of a full client-side installation. Finally, the Instant Client is easy to install.
Why use Instant Client?
Installation involves copying a small number of files or installing a package, for example the Linux 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.
The following tables shows the Oracle Database client-side files required to deploy an OCI application:
Table 2-1 OCI 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 |
| Security Library |
| ONS library |
Footnote 1
The libraries libclntsh.so.12.1, libclntshcore.so.12.1, and libociei.so must reside in the same directory in order to use Instant Client.
Table 2-2 OCI Instant Client Shared Libraries for Microsoft Windows
| Microsoft Windows | Description for Microsoft Windows |
|---|---|
| Forwarding functions that applications link with |
| Data and code |
| Security Library |
| ONS library used by OCI internally |
| Symbol tables |
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.
See Also:
OCI Instant Client Light Shared Libraries Linux and UNIX Table 2-3
OCI Instant Client Light Shared Libraries for Microsoft Windows Table 2-4
Oracle Database 12c Release 2 (12.2) library names are used in the table.
2.1.1 Installing the OCI Instant Client or Installing the Linux RPM Packages
Oracle Instant Client can be installed in two ways.
The Instant Client libraries can be installed by either choosing the Instant Client option from Oracle Universal Installer or by downloading and installing the Instant Client libraries from the OCI page on the Oracle Technology Network website:
To Download and Install the Instant Client Libraries from the Oracle Technology Network Website or to Install the Instant Client from the Oracle Universal Installer
The following steps are for the Linux, Unix, and Windows environments.
From the Oracle Technology Network, download and install the Instant Client shared libraries to an empty directory, such as
instantclient_12_2, for Oracle Database 12c Release 2 (12.2). Choose the Basic package.Or, 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_12_2, for Oracle Database 12c Release 2 (12.2).Set the operating system shared library path environment variable to the directory from Step 1. For example, on Linux or UNIX, set
LD_LIBRARY_PATHtoinstantclient_12_2. On Windows, setPATHto theinstantclient_12_2directory.If necessary, set the
NLS_LANGenvironment 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_LANGis 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 theNLS_LANGenvironment variable.(Optional). Set the
TNS_ADMINenvironment variable if thesqlnet.ora,tnsnames.ora, ororaaccess.xmlfiles are desired.
After completing the preceding steps you are ready to run the OCI application.
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 (except for the tnsnames.ora file described later).
If you did a complete client installation (by choosing the Admin option in Oracle Universal Installer), the Instant Client shared libraries are also installed. 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.12.1, libclntshcore.so.12.1, and libnnz12.so are in $ORACLE_HOME/lib
On Windows:
oraociei12.dll library is in ORACLE_HOMEinstantclient
oci.dll, ociw32.dll, and orannzsbb12.dll are in ORACLE_HOMEbin
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.
Note:
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.12.1 on Linux or UNIX and oraocci12.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 libocijdbc12.so on Linux or UNIX and ocijdbc12.dll on Windows). Place all libraries in the Instant Client directory.
Note:
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.
Note:
In addition, on Linux and UNIX systems, instead of copying individual files, you can generate Instant Client zip and RPM files for OCI and OCCI, JDBC, and SQL*Plus as described in 'Regeneration of Data Shared Library and Zip and RPM Files'. Then, you can copy the zip and RPM files to the target system and unzip them as previously described. The regenerated Instant Client binaries contain only the Instant Client files installed in the Oracle Client Administrator Home from which the regeneration is done. To install the rpm files, follow these instructions:Become root by running
suand entering the super-user password.Change to the directory in which you want to install.
Uninstall any earlier installations.
Install each package.
Or, to upgrade each package.
Delete the
.rpmfiles if you want to save disk space.Exit the root shell. No need to reboot.
2.1.2 When to Use Instant Client
Instant Client is a deployment choice and can be used for running production applications.
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.
See Also:
2.1.3 About Patching Instant Client Shared Libraries on Linux or UNIX
Because Instant Client is a deployment feature, the number and size of files (client footprint) required to run an OCI application has been reduced.
Hence, all files needed to patch Instant Client shared libraries are not available in an Instant Client deployment. A complete client installation based on Oracle home is needed for patching. Use the opatch utility for patching.
After you apply the patch in an Oracle home environment, copy the files listed in About OCI Instant Client to the instant client directory, as described in Installing the OCI Instant Client or Installing the Linux RPM Packages.
Instead of copying individual files, you can generate Instant Client zip and RPM files for OCI and OCCI, JDBC, and SQL*Plus as described in Regeneration of Data Shared Library and Zip and RPM Files. Then, you can copy the zip and RPM files to the target system and unzip them as described in Installing the OCI Instant Client or Installing the Linux RPM Packages.
The opatch utility stores the patching information of the ORACLE_HOME installation in libclntsh.so. This information can be retrieved by the following command:
If the Instant Client deployment system does not have the genezi utility, you can copy it from the ORACLE_HOME/bin directory.
Note:
The opatch utility is not available on Windows.
2.1.4 Regeneration of Data Shared Library and Zip and RPM Files
The process to regenerate the data shared library and the zip and RPM files changed.
The process to regenerate the data shared library and the zip and RPM files changed in Oracle Database 12c Release 1 (12.1). Separate make file targets are used to create the data shared libraries, zip, and RPM files either individually or all at once. In previous releases, one target, ilibociei, was provided to build the data shared libraries, zip, and RPM files. Now ilibociei builds only the zip and RPM files. Regeneration of data shared libraries requires both a compiler and linker, which may not be available on all installations. The sections that follow show the make file target used to regenerate data shared libraries, zip, and RPM files.
Note:
The regenerated Instant Client binaries contain only the Instant Client files installed in the Oracle Client Administrator Home from which the regeneration is done. Therefore, error messages, character set encodings, and time zone files that are present in the regeneration environment are the only ones that are packaged in the data shared libraries. Error messages, character set encodings, and time zone files depend on which national languages were selected for the installation of the Oracle Client Administrator Home.
Regeneration of the data shared library and the zip and RPM files is not available on Windows platforms.
2.1.4.1 Regenerating Data Shared Library libociei.so
The OCI Instant Client Data Shared Library (libociei.so) can be regenerated by using the following commands in an Administrator Install of ORACLE_HOME:
The new regenerated libociei.so is placed in the ORACLE_HOME/instantclient directory. The original existing libociei.so located in this same directory is renamed to libociei.so0.
2.1.4.2 Regenerating Data Shared Library libociicus.so
To regenerate Instant Client Light data shared library (libociicus.so), use the following commands:
The newly regenerated libociicus.so is placed in the ORACLE_HOME/instantclient/light directory. The original existing libociicus.so located in this same directory is renamed to libociicus.so0.
2.1.4.3 Regenerating Data Shared Libraries libociei.so and libociicus.so in One Step
To regenerate the data shared libraries libociei.so and libociicus.so, use the following commands:
The newly regenerated libociei.so is placed in the ORACLE_HOME/instantclient directory. The original existing libociei.so located in this same directory is renamed to libociei.so0.
The newly regenerated libociicus.so is placed in the ORACLE_HOME/instantclient/light directory. The original existing libociicus.so located in this same directory is renamed to libociicus.so0.
2.1.4.4 Regenerating Zip and RPM Files for the Basic Package
To regenerate the zip and RPM files for the basic package, use the following commands:
2.1.4.5 Regenerating Zip and RPM Files for the Basic Light Package
To regenerate the zip and RPM files for the basic light package, use the following commands:
2.1.4.6 Regenerating Zip and RPM Files for the JDBC Package
To regenerate the zip and RPM files for the JDBC package, use the following commands:
2.1.4.7 Regenerating Zip and RPM Files for the ODBC Package
To regenerate the zip and RPM files for the ODBC package, use the following commands:
2.1.4.8 Regenerating Zip and RPM Files for the SQL*Plus Package
To regenerate the zip and RPM files for the SQL*Plus package, use the following commands:
2.1.4.9 Regenerating Zip and RPM Files for the Tools Package
To regenerate the zip and RPM files for the tools package, use the following commands:
2.1.4.10 Regenerating Zip and RPM Files for All Packages
To regenerate the zip and RPM files for all packages, use the following commands:
The new zip and RPM files are generated under the following directory:
$ORACLE_HOME/rdbms/install/instantclient
Regeneration of the data shared library and the zip and RPM files is not available on Windows platforms.
2.1.5 Database Connection Strings for OCI Instant Client
OCI Instant Client can make remote database connections in all the ways that ordinary SQL clients can.
However, because Instant Client does not have the Oracle home environment and directory structure, some database naming methods require additional configuration steps.
All Oracle Net naming methods that do not require use of ORACLE_BASE_HOME, or ORACLE_HOME, or TNS_ADMIN (to locate configuration files such as tnsnames.ora, sqlnet.ora, or oraaccess.xml) work in the Instant Client mode. In particular, the connect_identifier in the OCIServerAttach() call can be specified in the following formats:
A SQL Connect URL string of the form:
As a local naming parameters
tnsnames.oraconfiguration file entry of the form:As an Oracle Net connect descriptor of the form:
A Connection Name that is resolved through Directory Naming where the site is configured for LDAP server discovery.
For naming methods such as tnsnames.ora and directory naming to work, the TNS_ADMIN environment variable must be set.
See Also:
Oracle Database Net Services Administrator's Guide chapter on 'Configuring Naming Methods' for more about connect descriptors
If the TNS_ADMIN environment variable is not set, and tnsnames.ora entries such as inst1, and so on, are used, then the ORACLE_HOME variable must be set, and the configuration files are expected to be in the $ORACLE_HOME/network/admin directory.
Note that the ORACLE_HOME variable in this case is only used for locating Oracle Net configuration files, and no other component of Client Code Library (OCI, NLS, and so on) uses the value of ORACLE_HOME. So it is preferred and easier to set the TNS_ADMIN environment variable to establish the location of the tnsnames.ora file.
If a NULL string, ', is used as the connection string in the OCIServerAttach() call, then the TWO_TASK environment variable can be set to the connect_identifier. On a Windows operating system, the LOCAL environment variable is used instead of TWO_TASK.
Similarly, for OCI command-line applications such as SQL*Plus, the TWO_TASK (or LOCAL on Windows) environment variable can be set to the connect_identifier. Its value can be anything that would have gone to the right of the '@' on a typical connect string.
This section includes the following topic: Examples of Instant Client Connect Identifiers.
2.1.5.1 Examples of Instant Client Connect Identifiers
If you are using SQL*Plus in Instant Client mode, then you can specify the connect identifier in the following ways:
Oracle Oci Client Download
If the listener.ora file on the Oracle database contains the following:
The SQL*Plus connect identifier is:
The connect identifier can also be specified as:
Alternatively, you can set the TWO_TASK environment variable to any of the previous connect identifiers and connect without specifying the connect identifier. For example:
You can also specify the TWO_TASK environment variable as:
Then you can invoke SQL*Plus with an empty connect identifier (you are prompted for the password):
The connect descriptor can also be stored in the tnsnames.ora file. For example, if the tnsnames.ora file contains the following connect descriptor:
The tnsnames.ora file is located in the /home/webuser/instantclient directory, so you can set the variable TNS_ADMIN (or LOCAL on Windows) as:
Then you can use the connect identifier conn_str for invoking SQL*Plus, or for your OCI connection.
Note:
TNS_ADMIN specifies the directory where the tnsnames.ora file is located and TNS_ADMIN is not the full path of the tnsnames.ora file.
If the preceding tnsnames.ora file is located in an installation based Oracle home, in the /network/server6/home/dba/oracle/network/admin directory, then the ORACLE_HOME environment variable can be set as follows and SQL*Plus can be invoked as previously, with the identifier conn_str:
Finally, if tnsnames.ora can be located by TNS_ADMIN or ORACLE_HOME, then the TWO_TASK environment variable can be set as follows enabling you to invoke SQL*Plus without a connect identifier:
2.1.6 Environment Variables for OCI 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_HOMEbin 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 12c 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 oracorezoneinfo 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:
On Windows:
In these examples, n is the time zone data file version number.
Be sure to create subdirectory oracore/zoneinfo for (UNIX/LINUX) or subdirectory oracorezoneinfo 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 entries 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.
2.1.7 SDK for 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.batis provided to build the demos.On UNIX or Linux, the makefile
demo.mkis provided to build the demos. Theinstantclient_12_2directory must be on theLD_LIBRARY_PATHbefore linking the application. The OCI and OCCI programs require the presence oflibclntsh.soandlibocci.sosymbolic links in theinstantclient_12_2directory. Thedemo.mkmake file creates these before the link step. These symbolic links can also be created in a shell:The SDK also contains the Object Type Translator (OTT) utility and its classes to generate the application header files.
2.2 About Instant Client Light (English)
What about Instant Client Light (English) version.
The Instant Client Light (English) 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.
2.2.1 Globalization Settings
What character sets are supported by Instant Client Light.
Instant Client Light supports the following client character sets:
Single-byte
US7ASCII
WE8DEC
WE8MSWIN1252
WE8ISO8859P1
Unicode
UTF8
AL16UTF16
AL32UTF8
Instant Client Light can connect to databases having one of these database character sets:
US7ASCII
WE8DEC
WE8MSWIN1252
WE8ISO8859P1
WE8EBCDIC37C
WE8EBCDIC1047
UTF8
AL32UTF8
Free Gg Client Download
Instant Client Light returns an error if a character set other than those in the preceding lists is used as the client or database character set.
Instant Client Light can also operate with the OCI Environment handles created in the OCI_UTF16 mode.
See Also:
Oracle Database Globalization Support Guide for more information about National Language Support (NLS) settings
2.2.2 Operation of Instant Client Light
When do OCI applications operate in the Instant Client Light mode.
OCI applications, by default, look for the OCI Data Shared Library, libociei.so (or Oraociei12.dll on Windows) on the LD_LIBRARY_PATH (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-3and Table 2-4), libociicus.so (or Oraociicus12.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-3 OCI Instant Client Light Shared Libraries Linux and UNIX
| Linux and UNIX | Description for Linux and UNIX |
|---|---|
| Client Code Library |
| OCI Instant Client Light Data Shared Library |
| Security Library |
Table 2-4 OCI Instant Client Light Shared Libraries for Microsoft Windows
| Microsoft Windows | Description for Microsoft Windows |
|---|---|
| Forwarding functions that applications link with |
| Data and code |
| Security Library |
| Symbol tables |
See Also:
OCI Instant Client Shared Libraries for Linux and UNIX Table 2-1
OCI Instant Client Shared Libraries for Microsoft Windows Table 2-2
2.2.3 Installing Instant Client Light
Instant Client Light can be installed in one of these ways:
Installed from Oracle Technology Network (OTN)
The following URL is the Instant Client page on the Oracle Technology Network website:
For Instant Client Light, download and unzip the
basiclite.zippackage in to an emptyinstantclient_12_2directory.Installed from an Instant Client Administrator installation
From the
ORACLE_HOME/instantclient/lightsubdirectory, copylibociicus.so(ororaociicus12.dllon Windows). The Instant Client directory on theLD_LIBRARY_PATH(PATHon Windows) should contain the Instant Client Light Data Shared Library,libociicus.so(oraociicus12.dllon Windows), instead of the larger OCI Instant Client Data Shared Library,libociei.so(oraociei12.dllon Windows).Installed from an Oracle Universal Installer installation
When you select the Instant Client option from the Oracle Universal Installer,
libociei.so(ororaociei12.dllon Windows) is installed in the base directory of the installation, which means these files are placed on theLD_LIBRARY_PATH(PATHon Windows).The Instant Light Client Data Shared Library,
libociicus.so(ororaociicus12.dllon Windows), is installed in thelightsubdirectory of the base directory and not enabled by default. Therefore, to operate in the Instant Client Light mode, the OCI Data Shared Library,libociei.so(orOraociei12.dllon Windows) must be deleted or renamed and the Instant Client Light library must be copied from thelightsubdirectory to the base directory of the installation.For example, if Oracle Universal Installer has installed the Instant Client in
my_oraic_12_2directory on theLD_LIBRARY_PATH(PATHon Windows), then use the following command sequence to operate in the Instant Client Light mode:Note:
To ensure that no incompatible binaries exist in the installation, always copy and install the Instant Client files in to an empty directory.