Starting in v0.20.0, Metabase provides a driver for connecting to Oracle databases. Under the hood, Metabase uses Oracle’s JDBC driver; due to licensing restrictions, we can’t include it as part of Metabase. Luckily, downloading it yourself and making it available to Metabase is straightforward and only takes a few minutes.
You can download the JDBC driver from Oracle’s JDBC driver downloads page.
Head to this page, accept the license agreement, and download
Before downloading this JAR you may need to sign up for a free account with Oracle. We recommend downloading version 22.214.171.124 or greater of the Oracle JDBC driver.
Metabase will automatically make the Oracle driver available if it finds the Oracle JDBC driver JAR in the Metabase plugins directory when it starts up. All you need to do is create the directory, move the JAR you just downloaded into it, and restart Metabase.
By default, the plugins directory is called
plugins, and lives in the same directory as the Metabase JAR.
For example, if you’re running Metabase from a directory called
/app/, you should move the Oracle JDBC driver JAR to
# example directory structure for running Metabase with Oracle support /app/metabase.jar /app/plugins/ojdbc8.jar
If you’re running Metabase from the Mac App, the plugins directory defaults to
# example directory structure for running Metabase Mac App with Oracle support /Users/camsaul/Library/Application Support/Metabase/Plugins/ojdbc8.jar
Finally, you can choose a custom plugins directory if the default doesn’t suit your needs by setting the environment variable
Java version 9 has introduced a new module system that places some additional restrictions on class loading. To use Metabase drivers that require extra external dependencies, you’ll need to include them as part of the classpath at launch time. Run Metabase as follows:
# Unix java -cp metabase.jar:plugins/* metabase.core
On Windows, use a semicolon instead:
# Windows java -cp metabase.jar;plugins/* metabase.core
The default Docker images use Java 8 so this step is only needed when running the JAR directly.