JDBC drivers for predefined data connectors

Obtaining IBM BigInsights 3 JDBC drivers

If you use the IBM BigInsights 3 BigSQL and Hive2 services, you can obtain the JDBC driver files as follows:

1. Log in to the BigInsights Web Console.
2. Click Quick Links > Download client library and development software.
3. Select the following software bundles:
   • Hive JDBC package
   • BigSql and BigSqlv1 client libraries
4. Save the JDBC files to the directory shown in Table 1.

Obtaining IBM BigInsights 4 JDBC drivers

If you use the IBM BigInsights 4 BigSQL and Hive2 services, you can obtain the JDBC driver files as follows:

1. Copy the required JAR files (shown in Table 1) from the Hadoop master node. The files are typically located in the following directories:
   • For Hive:
     • /usr/iop/4.0.0.0/hive/lib/
     • /usr/iop/4.0.0.0/hadoop/
     • /etc/hadoop/conf/
   • For BigSQL:
     • /usr/ibmpacks/bigsql/4.0/db2/java/
2. You can copy all of the JAR files if you want, but you need only the files shown in Table 1.
3. Save the JDBC files to the directory shown in Table 1.

Obtaining Cloudera JDBC drivers

Drivers are available on the Cloudera website or you can download the driver files from a Cloudera installation package.

• If you choose to download drivers from the Cloudera web site:

  Note that there are separate packages for Hive and Impala. The Hive package must be copied to ./libs/cloudera/hive/ and the Impala package to ./libs/cloudera/impala. Each download packages has several JDBC driver zip files. Ensure that you use the JDBC4 (not JDBC41) zip file for the compatible drivers. For both, Impala and Hive, JDBC4 drivers are the only supported version. The other JDBC versions that are included in the package are not compatible with IBM Fluid Query.

  Note: If you download and use the drivers from the Cloudera web site and encounter problems, you can use the drivers from a Cloudera installation kit as a workaround. Note that you must remove the drivers from the web download package first before you replace them with the other drivers.
• If you choose to obtain the JDBC driver files from a Cloudera installation, use the following steps:
  1. Copy the required JAR files (shown in Table 1) from the Hadoop master node. The files are typically in the following directories:
     • /usr/lib/hive/lib/
     • /usr/lib/hadoop/client/
     • /opt/cloudera/parcels/CDH/lib/hadoop/lib
  2. You can copy all of the JAR files if you want, but you need only the files shown in Table 1.
  3. Save the JDBC files to the directory shown in Table 1.
     Important:

     • For connections to the Impala service, the IBM Fluid Query features only support the Hive2 drivers.
     • Cloudera 5.4 uses Java 7 JDBC drivers. You can only use Java 7 drivers with IBM Fluid Query 1.6 and IBM Netezza Analytics 3.2.1. If you are using IBM Netezza Analytics version prior to 3.2.1, download and use the Java 6 drivers from a Cloudera 5.3 installation kit.

Obtaining Hortonworks JDBC drivers

If you use the Hortonworks Hive2 services, you could obtain the JDBC driver files as follows:

1. Copy the required JAR files (shown in Table 1) from the Hadoop master node. The files are typically in the following two directories, where X.X.X.X-XXXX are the software version and build numbers for your service provider:
   • ./usr/hdp/X.X.X.X-XXXX/hive/lib/
   • ./usr/hdp/X.X.X.X-XXXX/hadoop/client/
   For example:
   • ./usr/hdp/2.2.0.0-2041/hive/lib/
   • ./usr/hdp/2.2.0.0-2041/hadoop/client/
2. You can copy all of the JAR files if you want, but you need only the files shown in Table 1.
3. Save the JDBC files to the directory shown in Table 1.

Troubleshooting missing JDBC drivers

If you encounter any problems finding or obtaining the JDBC files listed in Table 1, or if you see ClassNotFoundException error messages when trying to configure connections, you may be missing a JDBC file required for that service connection. Sometimes the files may be in other locations on the system. If you cannot find a JDBC file, you can try to search for the file on your service provider's master node.

1. Log in to the service provider's master node as the root user.
2. Run a command similar to the following, to search for the missing file:

   find / -name "missing-jar-name*.jar"

   For example:

   find / -name "commons-configuration*.jar"

3. The command displays a pathname for the file if it is present on the system. If you cannot find the required JDBC file and the fqConfigure.sh script continues to show errors for missing files, contact your service provider for assistance with obtaining the missing file.