I have same problem.
I have an metabase installation based on docker image 0.24.2.
I follow the installation statement for oracle driver but when I try to create a database link I don’t see oracle menu choice.
I had the same problem with the Docker installation. What I needed to do to fix it is:
Make sure the metabase account in the Docker container can actually access those files, for example chmod -R 777 ./plugins on the host. You can verify this with docker exec -it metabase ls -l /app/plugins.
I read instructions and do not realize how the new jar(in plugins folder) will be associated to text in the combo box. Normally in a combo is displayed human-readable description ( like PostgreSQL, MySQL) and NOT the driver name. So even Metabase to load dynamically new jars( db drivers), there should be simple configuration and mapping between these jars and text displayed in combo. My question is: where should I add this mapping in order to use provided in plugin DB driver?
If you just want to use an already supported database like Oracle there is no need to give any mapping as it’s already hard-coded into the Metabase driver layer (a support layer on top of e.g a JDBC driver) - like here for Oracle. So there is really no magic to it.
Thanks for fast reply! Unfortunatelly this is not the case. I’d like to add snowflake connection. Is there someting I can do without waiting the official (hardcoded?) release. I do not know clojure but I’m prety good with java.