Fix DBeaver Driver Not Found – Missing JDBC Driver

In this tutorial, you'll learn about Fix DBeaver Driver Not Found. We cover key concepts, practical examples, and best practices.

You try to connect to a database in DBeaver — say, MariaDB, ClickHouse, or SQLite. DBeaver opens a download dialog, then fails with "Driver not found" or "Can't create driver instance". The connection button stays greyed out.

Wrong ❌

You click Download when DBeaver prompts for the driver. The download bar appears, completes, but nothing changes — the driver still shows "Missing" in the connection wizard.

You try to manually point DBeaver to a JAR you downloaded months ago, but the class path is wrong and DBeaver complains about a missing class.

Right ✅

Automatic download (recommended):

1. Window → Preferences → Connections → Drivers
2. Find your database (e.g. MariaDB)
3. Select it → click Edit
4. In the Libraries tab, click Download/Update
5. Pick the latest stable version → Download
6. After download, verify Class Name is populated (e.g. org.<a href="/databases/mariadb/">mariadb</a>.jdbc.Driver)

Manual JAR install:

1. Download the driver JAR (e.g. <a href="/databases/mariadb/">mariadb</a>-java-client-3.1.4.jar)
2. In DBeaver: Window → Preferences → Drivers → MariaDB → Edit → Libraries
3. Click Add File → select the JAR
4. Click Find Class — DBeaver autodetects the driver class

Now create the connection — the Test Connection button is green and active:

Connected
Driver: MariaDB Connector/J 3.1.4
Database: mydb@host:3306
Ping: 3 ms

Root Cause

DBeaver does not bundle every JDBC driver — it fetches them on demand from Maven Central. Network restrictions, corporate proxies, or version mismatches cause the download to fail silently. The driver entry remains in a half‑configured state.

Prevention

• Configure DBeaver's proxy: Window → Preferences → Connections → Drivers → Proxy if behind a corporate firewall.
• Keep a local folder of common JDBC JARs for offline installs.
• After a major DBeaver upgrade, re‑download third‑party drivers — the internal API can change.
• Use the Connectivity → Drivers view to see all installed drivers at a glance.

Common Mistakes with driver not found

1. Overlapping type class instances that cause GHC to reject the program with ambiguous dispatch errors
2. Non-exhaustive pattern matches that compile with warnings then crash at runtime
3. Misunderstanding that String is [Char] with poor performance for large text operations

These mistakes appear frequently in real-world DBEAVER code. DodaTech's contributors have identified these patterns through analysis of open-source projects and production systems.

Practice Exercise

Write a pure function that safely divides two integers using Maybe, then test it with edge cases like division by zero and negative numbers.

This exercise reinforces the concepts covered in this guide. Try implementing it before checking online solutions.

FAQ

See the full guide to DBeaver setup on the DodaTech DBeaver Fundamentals course.