Troubleshooting: SSLHandshakeException / "Data Lake is not available" (Java JDBC - Infor Compass)

ODBC PowerPack Troubleshooting
, , , ,
1

Overview

When connecting to Infor Data Lake (Compass JDBC) using Java-based drivers (for example, via ZappySys ODBC - JDBC Bridge Driver), you may run into errors like:

  • java.sql.SQLException: Data Lake is not available
  • SSLHandshakeException
  • Authentication was rejected
  • Could not retrieve authentication tokens from the authentication server

Even though the message may look like an SSL issue, the root cause is not always related to certificates. This article walks through the most common causes and how to troubleshoot them.

Common Causes

This issue is usually related to one of the following:

  • SSL / Java truststore issues
  • OAuth authentication failure (ION API)
  • Network or endpoint access problems
  • Invalid or outdated ION API credential files

Step-by-Step Troubleshooting

1. Check if this is an Authentication Issue

If you see errors like:

  • Authentication was rejected
  • Could not retrieve authentication tokens

Then the issue is happening during token generation (ION API).

What to do:

  • Try generating a token using Postman or another API tool
  • Verify your:
    • Client ID / Client Secret
    • Token endpoint
    • Username/password (only if using password flow)

2. Verify Infor Environment

Before going deeper, confirm whether the issue is specific to your setup.

Check:

  • Can you access Data Lake using Infor Compass?
  • Does it work from another tool (e.g., DBeaver, FiveTran)?

Result:

  • If it works elsewhere → the issue is local (JDBC / Java / config)
  • If it fails everywhere → check with your Infor admin

3. Validate Java & SSL Configuration

Since the driver runs on Java, SSL configuration is important.

Things to check:

  • Java is correctly installed and configured
  • JAVA_HOME is pointing to the correct version
  • Required certificates exist in the Java keystore

Command to list certificates:

keytool -list -v -keystore "%JAVA_HOME%\lib\security\cacerts" -storepass changeit

Common issues:

  • Missing intermediate certificates
  • Expired certificates
  • Java update resetting the truststore

Note: If everything looks fine here but the issue persists, continue to the next section — the problem may not be SSL-related.

4. Check Network / Endpoint Access

Sometimes the driver cannot reach the authentication endpoint.

Things to verify:

  • Firewall is not blocking outbound requests
  • Token endpoint is reachable

Quick test:

  • Try calling the token endpoint via Postman or browser

5. Restart and Refresh Configuration

This sounds simple, but it helps in many cases.

  • Restart the machine or service
  • Re-save your DSN configuration
  • Re-test the connection

Additional Root Cause: ION API Credential Files

This is a commonly overlooked issue.

Scenario

You may still see the error even when:

  • SSL setup is correct
  • Java configuration is fine
  • Infor Compass works
  • Other tools can connect successfully

Root Cause

The problem may be with the ION API credential files (for example, .ionapi file or related config).

These files can become:

  • Outdated
  • Corrupted
  • Misconfigured
  • Pointing to the wrong location

Solution

Try the following:

  1. Re-download credentials
  • Go to Infor ION API → Authorized Apps
  • Download fresh credentials
  1. Use a new folder
  • Create a new folder
  • Place:
    • New .ionapi file
    • Required JDBC .jar files
  1. Update your configuration
  • Point your JDBC / ODBC–JDBC bridge to the new folder
  1. Test again
  • First test using a tool like DBeaver (optional but helpful)
  • Then test using your application or ZappySys driver

Tip

If it works in another tool but not in your setup, it usually means:
:backhand_index_pointing_right: The configuration path or credential reference is incorrect

Summary

Here’s a quick way to think about it:

Symptom Likely Cause
SSLHandshakeException Certificate / Java issue
Authentication rejected OAuth / token issue
Works in other tools Local configuration issue
Sudden failure Credential file issue

Final Thoughts

If the connection was working before and suddenly stopped without any visible changes, don’t focus only on SSL. While SSL handshake failures are often caused by untrusted or missing certificates in the Java truststore, in many real-world cases the issue turns out to be related to ION API credentials or configuration.

A good approach is to:

  • Verify connectivity and endpoint access
  • Check Java and SSL configuration
  • Validate or re-download ION API credentials

Following these steps usually helps resolve the issue quickly.

If you’re still stuck, feel free to reach out to ZappySys Support with your setup details (mask sensitive information), and we’ll be happy to help you troubleshoot further.