- Linux oracle sql client
- Instant Client Installation for Linux (32-bit)
- Linux oracle sql client
- Version 19.19.0.0.0 (Requires glibc 2.27)
- Name
- Download
- Description
- Name
- Download
- Description
- Name
- Download
- Description
- Linux oracle sql client
- Free, light-weight, and easily installed Oracle Database tools, libraries and SDKs
- Oracle Instant Client
- What’s New
- Oracle Linux has Instant Client RPMs
- Instant Client is available for Docker
- Instant Client Features
- Recommended Oracle Oracle Instant Client
- Instant Client applications are cloud ready
- Recent changes to Oracle Autonomous Database on Shared Exadata Infrastructure (ADB-S) connectivity
- Connecting to Multiple Oracle Autonomous Databases from one Process
Linux oracle sql client
(31,413,713 bytes) (cksum — 384697539)
(4,649,614 bytes) (cksum — 753190421)
(331,854 bytes) (cksum — 722849044)
(294,618 bytes) (cksum — 4282446920)
Instant Client Installation for Linux (32-bit)
For general Instant Client information, see the Home Page.
Client-server version interoperability is detailed in Doc ID 207303.1. For example, Oracle Call Interface 19.3 can connect to Oracle Database 11.2 or later. Some tools may have other restrictions.
Installation of ZIP files:
- Download the desired Instant Client ZIP files. All installations require a Basic or Basic Light package.
- Unzip the packages into a single directory such as /opt/oracle/instantclient_19_3 that is accessible to your application. For example:
cd /opt/oracle unzip instantclient-basic-linux-19.3.0.0.0dbru.zip
cd /opt/oracle/instantclient_12_2 ln -s libclntsh.so.12.1 libclntsh.so ln -s libocci.so.12.1 libocci.so
For example, on Oracle Linux, run:
sudo sh -c "echo /opt/oracle/instantclient_19_3 > \ /etc/ld.so.conf.d/oracle-instantclient.conf" sudo ldconfig
Alternatively, set the LD_LIBRARY_PATH environment variable prior to running applications. For example:
The variable can optionally be added to configuration files such as ~/.bash_profile and to application configuration files such as /etc/sysconfig/httpd .
mkdir -p /opt/oracle/instantclient_12_2/network/admin
This is the default Oracle configuration directory for applications linked with this Instant Client.
Alternatively, Oracle configuration files can be put in another, accessible directory. Then set the environment variable TNS_ADMIN to that directory name.
Installation of RPM files:
- Download the desired Instant Client RPM packages. All installations require a Basic or Basic Light RPM.
- Install the packages with yum . For example:
sudo yum oracle-instantclient19.3-basic-19.3.0.0.0-1.i386.rpm
Note that from 19.3, by default only one version of the Instant Client RPM libraries can be installed at a time.
sudo sh -c "echo /usr/lib/oracle/18.3/client/lib > \ /etc/ld.so.conf.d/oracle-instantclient.conf" sudo ldconfig
For Instant Client 19.3 RPM packages, these commands are automatically run.
Alternatively, set the LD_LIBRARY_PATH environment variable prior to running applications. For example:
The variable can optionally be added to configuration files such as ~/.bash_profile and to application configuration files such as /etc/sysconfig/httpd .
sudo mkdir -p /usr/lib/oracle/12.2/client/lib/network/admin
This is the default Oracle configuration directory for applications linked with this Instant Client.
Alternatively, Oracle configuration files can be put in another, accessible directory. Then set the environment variable TNS_ADMIN to that directory name.
Linux oracle sql client
See the Instant Client Home Page for more information about Instant Client.
Client-server version interoperability is detailed in Doc ID 207303.1. For example, Oracle Call Interface 19.3 can connect to Oracle Database 11.2 or later. Some tools may have other restrictions.
Instant Client RPMs are also available from yum.oracle.com for Oracle Linux 8 and Oracle Linux 7.
Version 19.19.0.0.0 (Requires glibc 2.27)
Base — one of these packages is required
Name
Download
Description
- All files required to run OCI, OCCI, and JDBC-OCI applications
- (72,167,356 bytes) (cksum — 2098436471)
- All files required to run OCI, OCCI, and JDBC-OCI applications
- (50,394,052 bytes) (cksum — 391790275)
- Smaller version of the Basic package, with only English error messages and Unicode, ASCII, and Western European character set support
- (33,843,154 bytes) (cksum — 1807809457)
- Smaller version of the Basic package, with only English error messages and Unicode, ASCII, and Western European character set support
- (25,183,484 bytes) (cksum — 3249090742)
Tools — optional packages
Name
Download
Description
- The SQL*Plus command line tool for SQL and PL/SQL queries
- (895,322 bytes) (cksum — 1084119313)
- The SQL*Plus command line tool for SQL and PL/SQL queries
- (681,536 bytes) (cksum — 2341721767)
- Includes Data Pump, SQL*Loader and Workload Replay Client
- (1,221,507 bytes) (cksum — 1376544842)
- Includes Data Pump, SQL*Loader and Workload Replay Client
- (945,784 bytes) (cksum — 2880749463)
Development and Runtime — optional packages
Name
Download
Description
- Additional header files and an example makefile for developing Oracle applications with Instant Client
- (934,898 bytes) (cksum — 3058144248)
- Additional header files and an example makefile for developing Oracle applications with Instant Client
- (619,488 bytes) (cksum — 1371976780)
- Additional support for Internationalization under JDBC
- (1,578,849 bytes) (cksum — 2028481195)
- Additional support for Internationalization under JDBC
- (1,534,324 bytes) (cksum — 3783463702)
Linux oracle sql client
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
Recommended Oracle Oracle Instant Client
Oracle recommends using the latest 19c Release Update of Oracle Instant Client or Oracle Database Client. This is a Long Term Release.
Alternatively you can use the latest 21c Release Update if you require client features introduced in this Innovation Release.
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.
Recent changes to Oracle Autonomous Database on Shared Exadata Infrastructure (ADB-S) connectivity
DigiCert retired the Organizational Unit (OU) field for all public TLS/SSL certificates to comply with industry standards as of August 2022. This means that public TLS/SSL certificates issued by DigiCert will no longer have an OU field. Refer to MOS note 2911553.1 for details.
To avoid disruption to applications connecting to Oracle Autonomous Database on Shared Exadata Infrastructure (ADB-S) during the server side certificate change, you must use hostname based matching of the server certificate.
The following versions of Oracle Instant Client automatically support hostname based matching:
- Oracle Call Interface (OCI), Oracle C++ Call Interface (OCCI) or ODBC applications must use one of the above client versions.
- Oracle Database drivers based on Oracle Instant Client or Oracle Database Client (e.g ODPI-C, python-oracledb Thick mode, cx_Oracle, node-oracledb, godror, PHP OCI8, PHP PDO_OCI, ruby-oci8, ROracle, and rust-oracle) must use the driver with a compatible client version from the list above.
ADB-S connection strings contain a hostname «. (HOST=xyz). » which depends on the region. For example, in the Chicago region the hostname would be «adb.us-chicago-1.oraclecloud.com». If you have replaced the default hostname with an IP address or a custom hostname, then hostname based DN matching will fail. The solution is to add a new entry to your /etc/hosts file using the original ADB-S domain suffix. Your connection string should then use this new name. For example an entry «localtunnel.adb.us-chicago-1.oraclecloud.com» could be created and used.
Connecting to Multiple Oracle Autonomous Databases from one Process
To connect to multiple Oracle Autonomous Database instances from within one application process, use Oracle Instant Client 19.17, or later, or use Instant Client 21c.
If you are using mTLS connections, put each wallet’s cwallet.sso file in a unique directory. Concatenate the tnsnames.ora file entries from all wallets into a single tnsnames.ora file. Make a copy of one sqlnet.ora file and remove the WALLET_LOCATION line. Alter each connection descriptor in your new tnsnames.ora file and add a WALLET_LOCATION clause set to the directory containing the cwallet.sso file for the relevant database. See the Database Net Services Reference for an example. Configure your application to use the new tnsnames.ora and sqlnet.ora files, for example by placing them both in the «network/admin» sub-directory of your Instant Client installation. Your application can now use the appropriate network alias from the tnsnames.ora file to connect to each database service.