ODBC drivers >

JDBC drivers >

Bridges, gateways >

Other >

All products

Connect JDBC to any ODBC driver

Connect JDBC to Microsoft Access

Cross-platform or cross-architecture access to any ODBC driver

ODBC access to any JDBC driver

Connect dbExpress applications to any ODBC driver

Connect XML applications to any ODBC driver

Access mutiple ODBC data sources from one SQL statement

Create custom ODBC drivers

Bespoke data access requirements

In the pipeline

Support

Resources

Quick start

Licensing

Knowledge Base

User Guides

Company

About Us

Careers & Partners

What to do if you get "cannot open shared object file" errors when using the OCI version Easysoft Oracle ODBC driver?

Are you evaluating

an ODBC driver?

Yes I am!

The Oracle client-based version of our Oracle ODBC driver is compatible with either the full version of the Oracle client or the more lightweight Instant Client.

To be able to load the Oracle client software certain environment variables need to be set.

If you have set your environment so that the Oracle client gets loaded, and the Oracle client libraries are the same architecture as the Easysoft driver, but client software still can't be loaded, check that the system libraries that the Oracle client requires are present.

On Linux, use the ldd command to do this. For example:

ldd /usr/lib/oracle/12.2/client/lib/libclntsh.so.12.1

If any of the dependent libraries are not found, you may need to install them. For example, you need the libaio shared object for the Oracle client to function. Make sure that any missing libraries have the same architecture as the client libraries. (If your application is 64-bit, you need a 64-bit ODBC driver and Driver Manager, and a 64-bit Oracle client and dependent library set. If your application is 32-bit, the components listed in the previous sentence all need to be 32-bit.)

Share:

AltStyle によって変換されたページ (->オリジナル) /