Collection Contents Previous Next PDF

ASA Database Administration Guide

Connecting to a Database

Troubleshooting connections

Locating the interface library


The client application makes a call to one of the Adaptive Server Anywhere interface libraries. In general, the location of this DLL or shared library is transparent to the user. Here we describe how to locate the library in case of problems.

ODBC driver location 

For ODBC, the interface library is also called an ODBC driver. An ODBC client application calls the ODBC driver manager, and the driver manager locates the Adaptive Server Anywhere driver.

The ODBC driver manager looks in the supplied data source in the .odbc.ini file or registry to locate the driver. When you create a data source using the ODBC Administrator, Adaptive Server Anywhere fills in the current location for your ODBC driver.

Embedded SQL interface library location 

Embedded SQL applications call the interface library by name. The name of the Adaptive Server Anywhere embedded SQL interface library is as follows:

OLE DB driver location 

The provider name (ASAProv) is used to locate the ASAOLEDB DLL based on entries in the registry. The entries are created when the ASAProv provider is installed or if it is reregistered.

iAnywhere JDBC driver location 

The Java package jodbc.jar must be in the classpath when you run your application. The native DLLs or shared objects must be in the system path.

When the library is located 

Once the client application locates the interface library, it passes a connection string to it. The interface library uses the connection string to assemble a list of connection parameters, which it uses to establish a connection to a server.


Collection Contents Previous Next PDF