JDBC Driver

This section describes the JDBC driver provided by Exasol to connect third party applications to Exasol.

System Requirements

JRE Requirement

The JDBC driver requires a Java runtime environment (version 5.0 or later). You can use the driver on any platform with a supported JRE version.

If you are using Exasol JDBC version 6.2.3 or later, the driver needs JRE 7 or later version.

Tested Systems

The driver has been tested on the following systems using the specified Java version with the latest available updates:

Download JDBC Driver

  1. Go to the Exasol Downloads page.
  2. In the Download JDBC Driver section, select the required file based on your OS, for examples:
    • Windows:EXASOL_JDBC-<version>.msi
    • Unix:EXASOL_JDBC-<version>.tar.Z
    • Linux:EXASOL_JDBC-<version>.tar.gz
  3. Run the executable file downloaded, and follow the setup wizard to complete the installation.

Installing JDBC Driver

On Windows

The driver is installed as a .jar archive in the installation directory.

On Linux/Unix

The driver is included in the delivered .tgz file. Depending on the application this archive must be added to the search path for the Java classes (CLASSPATH).

All classes of the JDBC driver belong to the Java com.exasol.jdbc package. The main class of the driver is com.exasol.jdbc.EXADriver

Integrating JDBC Driver using Maven

The JDBC driver is also available in the Exasol Maven repository (https://maven.exasol.com). Add the following repository and dependency to the build configuration of your project (for example, pom.xml for Maven)


Exasol URL

The JDBC Driver uses the following URL structure for Exasol:


The following table explains the elements of the URL structure.

Element Details
jdbc:exa This prefix is necessary for the driver manager.

Defines the servers and the port of the Exasol cluster (for example, You can also have a hostname mapped to multiple IP addresses.

When opening a connection, the driver will randomly choose an address from the specified address range. If the connection fails, the driver will continue to try all other possible addresses. You can also specify an IP range with a comma-separated list. For example:

  • myhost:8563: Single server with name myhost and port 8563. Or single host myhost with multiple IP addresses mapped to it and port 8563.
  • myhost1,myhost2:8563: Two servers with port 8563.
  • myhost1..4:8563: Four servers (myhost1, myhost2, myhost3, myhost4) and port 8563.
  • Four servers from to and port 8563.

Instead of a list you can also specify a file that contains a list (for example, //c:\mycluster.txt). The two slashes ("/") indicate that a filename is specified. An optional list of properties separated by a ";" follows the port, the values of which should be set when logging-in.

These properties correspond with the supported Driver Properties and are described in the following section.

The values of properties within the URL can only consist of alphanumeric characters.

Example from a Java program

import java.sql.*;
import com.exasol.jdbc.*;

public class jdbcsample
    public static void main(String[] args)
        try { Class.forName("com.exasol.jdbc.EXADriver");
    } catch (ClassNotFoundException e) { 
    Connection con=null
    Statement stmt=null
    try {
        con = DriverManager.getConnection( 
        stmt = con.createStatement();
        ResultSet rs = stmt.executeQuery("SELECT * FROM CAT")
        System.out.println("Schema SYS contains:")
            String str1 = rs.getString("TABLE_NAME")
            String str2 = rs.getString("TABLE_TYPE")
            System.out.println(str1 + ", " + str2);
    } catch (SQLException e) { 
    } finally {
        try {stmt.close();} catch (Exception e) {e.printStackTrace();} 
        try {con.close();} catch (Exception e) {e.printStackTrace();}

The above code sample builds a JDBC connection to Exasol, that runs on servers up to on port 8563. User sys with the password exasol is logged-in and the schema sys is opened. After that, all tables in this schema are shown.

Schema SYS contains

Supported Driver Standards

The driver supports JDBC 3.0 Core API until Exasol JDBC 6.2.2 release. However, from Exasol JDBC 6.2.3 release, the driver supports JDBC 4.1 API. Detailed information about the supported interfaces are provided in the API Reference which you can find in the html folder of the driver installation directory. If you want to learn more about JDBC, see JDBC Basics.

The standard includes the following:

  • Access to the driver through the DriverManager API and configuration of the driver using the DriverPropertyInfo interface.
  • Direct execution of SQL statements as a prepared statement and in batch mode.
  • Support of more than one open ResultSet.
  • Support of the DatabaseMetaData and ResultSetMetaData metadata APIs.

The following features are not supported:

  • Savepoints
  • User-defined data types and the types Blob, Clob, Array, and Ref.
  • Stored procedures
  • Read-only connections
  • The API ParameterMetaData

If the rowcount of a query exceeds 2147483647 (231-1), the JDBC driver will return the value 2147483647. This is because of the 32-bit limitation for this return value defined by the JDBC standard.

Supported Driver Properties

You can transfer the following properties to the JDBC driver through the URL. Property names are case sensitive.



Name of the schema that should be opened after login. If the schema cannot be opened, the login fails with a java.sql.SQLException.

Default: no schema to open


0=off, 1=on

Switches autocommit on or off.

Default: 1


0=off, 1=on

Switches automatic encryption on or off.

Default: 1



Principal name of the Kerberos service. If nothing is specified, the name "exasol" will be used as default.


Host name of the Kerberos service. If nothing is specified, the host name of the connections string will be used as default

numeric, >0

Amount of data in kB which should be obtained by Exasol during a fetch. The JVM can run out of memory if the value is too high.

Default: 2000

The same can be achieved by using the function setFetchSize().


0=off, 1=on

Switches on the driver's log function. The driver then writes a log file named jdbc_timestamp.log for each established connection.

These files contain information on the called driver methods and the progress of the JDBC connection. It can assist the Exasol Support in the diagnosis of problems.

Due to performance reasons the logging should not be used in a productive system

Default: 0



Defines the directory where the JDBC debug log files should be written to (in debug mode).

Example: jdbc:exa:;debug=1;logdir=/tmp/my folder/;schema=sys

Default is the application's current directory, which is not always transparent. That is why you should always set the log directory in debug mode.



Defines the name of the client sent to the server.

Default: "Generic JDBC client"



Defines the version of the client sent to the server.

Default: empty ("")


numeric, >=0

Maximum time (in seconds) the driver waits for the database for a connect or disconnect request.

Default is 0 (unlimited)


numeric, >=0

Maximum time (in milliseconds) the driver waits to establish a TCP connection to a server. This timeout is used to limit the login time especially in case of a large cluster with multiple reserve nodes.

Default: 2000


numeric, >=0

Defines the time (in seconds) for a statement to run before it is automatically aborted.

Default is 0 (unlimited)


0=off, 1=on

Enables the user to execute queries even if the limit for active sessions (executing a query) has been reached.


  • Only the SYS user can set the parameter.
  • superconnection should only be used in case of significant performance problems where it is impossible to log in and execute queries within a reasonable time. By that parameter you can analyze the system and kill certain processes which cause the problem.

Default: 0


0=off, 1=on

The sub-connections for parallel read and insert have this flag switched on.

Details and examples are available in an Exasol Knowledge Base Article.

Default: 0


numeric, >=0

Is necessary to establish parallel sub-connections.

Default: 0

connectionPoolSizenumeric, >=0

Changes the maximum size of the connection pool. You can change it only once in the driver instance.

Default: 64

Valid values: 0<connectionPoolSize<8192

Best Practices


Memory of JVM

When operating on big tables, you can get problems if the specified memory for the JVM is not big enough.

Reading big data volumes

Through the parameter fetchsize, you can determine the data volume which should be fetched from the database per communication round. If this value is too low, the data transfer may take longer to complete. If this value is too high, the JVM may run out of memory. The recommended fetch size is 1000-2000.

Inserting data into the database

Instead of using single insert statements like "INSERT INTO t VALUES 1, 2, ..." you should use the more efficient interface of prepared statements and their parameters. Prepared statements achieve optimal performance when using parameter sets between 500 kB and 20 MB. Moreover you should insert the data by using the native data types.

Unused resources

Unused resources should be freed immediately. For example, Prepared Statements through "close()".

Connection servers

Don't specify any unnecessary wide IP address range. Since those addresses are randomly tried until a successful connection, the "connect" could take much time.