OCI always obtains its data from the Data Shared Library. However, if it is set, it does not affect OCI. The ORACLE_HOME environment variable no longer determines the location of NLS, CORE, and error message files.Īn OCI-only application should not require ORACLE_HOME to be set. The JDBC OCI driver, in addition to the three OCI shared libraries, you must alsoĭownload OCI JDBC Library (for example libocijdbc19.so on Linux or Oraocci19.dll on Windows) in the Instant Client directory. To enable OCCI, you must install the OCCI Library To enable other capabilities such as OCCI and JDBC OCI, you must copy a fewĪdditional files. 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. 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, if you have multiple directories containing Instant Client libraries, then only one such directory should be on the operating system Library Path. There should be only one set of Oracle libraries on the operating system Library Path variable. Co-location of symlinks to Instant Client libraries is not a substitute for physical co-location of the libraries. For example, you can delete files such as jdbc.jar.Īll the libraries must be copied from the same Oracle home and must be placed in the same directory. Other libraries and utilities get installed, but are not needed for OCI runtime use. Otherwise, a full installation based on Oracle home is assumed.įor 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. Library is found, then the application operates in the Instant Client Light mode. Load the Instant Client Light Data Shared Library (see Table 2-3 and Table 2-4), libociicus.so (or If this library is not found, then OCI tries to Linux, or PATH on Windows) to determine if the application should The runtime library search path (for example LD_LIBRARY_PATH on Libociei.so (or Oraociei19.dll on Windows) in OCI applications, by default, look for the OCI Data Shared Library, It describes the version, date and time, and the operating system the Instant Client was generated on. It is simple for independent software vendors to package applications.Ī README file is included with the Instant Client installation. There is no loss of functionality or performance for applications deployed using Instant Client. The number of required files and the total disk storage are significantly Installation involves unzipping a few files, or installing RPM packages. Finally, the Instant Client is easy to install. A minimal install of Instant Client shared libraries can occupy less than 10% of the space of a full client-side installation. 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.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |