# JDBC upgraded - how to confirm which version running? **URL:** \ **Category:** Ignition\ **Created:** [January 21, 2025, 6:34pm UTC](https://forum.inductiveautomation.com/t/jdbc-upgraded-how-to-confirm-which-version-running/101191 "2025-01-21T18:34:53Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![justin.brzozoski](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/justin.brzozoski/32/13452_2.png) [@justin.brzozoski](https://forum.inductiveautomation.com/u/justin.brzozoski)\ **Post date:** [January 21, 2025, 6:34pm UTC](https://forum.inductiveautomation.com/t/jdbc-upgraded-how-to-confirm-which-version-running/101191/1 "2025-01-21T18:34:53Z")
I had a server still using MariaDB JDBC 2.7.3 from an old install. I saw that version 3.3.3 was sitting in jdbc-bundled and decided to upgrade to that. I grabbed the file out of that directory and upgraded as per [these instructions](https://docs.inductiveautomation.com/docs/8.1/platform/database-connections/connecting-to-databases/jdbc-drivers-and-translators#upgrade-a-jdbc-driver). The DB connection bounced momentarily and came back up and everything seems to be working. But ... both versions of the MariaDB JDBC files are in the same places as before under `./user-lib/` and I can't find any place in the log that spits out which JDBC version is in use. How can I confirm that the upgrade actually did anything? This is what the files looked like both before and after the upgrade: ```python justin@ignition:/usr/local/bin/ignition$ find . -iname "*maria*" -exec sha256sum {} \; 7c823b2f8fdda522a7f76e69cb287482b46247c135c4c44b27b98fb2ae092747 ./temp/jdbc/mariadb-java-client-2.7.36958885001544908716.jar 89d71a6ffd800c032b23e588108688d391631f0aba962ba2381cc82cb111b796 ./user-lib/jdbc-bundled/mariadb-java-client-3.3.3.jar 7c823b2f8fdda522a7f76e69cb287482b46247c135c4c44b27b98fb2ae092747 ./user-lib/jdbc/mariadb-java-client-2.7.3.jar ``` I expected the upgrade process to move the new one into `./user-lib/jdbc/` directly. ---
**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\ **Post date:** [January 21, 2025, 6:37pm UTC](https://forum.inductiveautomation.com/t/jdbc-upgraded-how-to-confirm-which-version-running/101191/2 "2025-01-21T18:37:49Z")
I think you need to remove the old one to be sure about anything. edit: I think you want to add the 3.3.3 JAR file in `./user-lib/jdbc/` and delete the 2.7.3 file. The `jdbc-bundled` folder is used by the installer during upgrades to stash possibly-newer version of JDBC drivers but not replace your existing ones. ---
**Author:** ![justin.brzozoski](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/justin.brzozoski/32/13452_2.png) [@justin.brzozoski](https://forum.inductiveautomation.com/u/justin.brzozoski)\ **Post date:** [January 21, 2025, 6:46pm UTC](https://forum.inductiveautomation.com/t/jdbc-upgraded-how-to-confirm-which-version-running/101191/3 "2025-01-21T18:46:44Z")
Okay... I tried the JDBC upgrade a second time, and this time it definitely did something: ```python justin@ignition:/usr/local/bin/ignition$ find . -iname "*maria*" -exec sha256sum {} \; 89d71a6ffd800c032b23e588108688d391631f0aba962ba2381cc82cb111b796 ./temp/jdbc/mariadb-java-client-3.3.31472352354373245713.jar 7c823b2f8fdda522a7f76e69cb287482b46247c135c4c44b27b98fb2ae092747 ./temp/jdbc/mariadb-java-client-2.7.36958885001544908716.jar 89d71a6ffd800c032b23e588108688d391631f0aba962ba2381cc82cb111b796 ./user-lib/jdbc-bundled/mariadb-java-client-3.3.3.jar 89d71a6ffd800c032b23e588108688d391631f0aba962ba2381cc82cb111b796 ./user-lib/jdbc/mariadb-java-client-3.3.3.jar ``` I feel like the first time somehow failed and I didn't get any obvious feedback. ---
**Author:** ![dkhayes117](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/dkhayes117/32/68344_2.png) [@dkhayes117](https://forum.inductiveautomation.com/u/dkhayes117)\ **Post date:** [January 21, 2025, 6:49pm UTC](https://forum.inductiveautomation.com/t/jdbc-upgraded-how-to-confirm-which-version-running/101191/4 "2025-01-21T18:49:33Z")
I upgraded to the newest version of MariaDB before Christmas, and all of my connections went bad. Turns out I needed to upgrade the JDBC driver too. I upgraded the same way that you described, except I pulled the latest driver from [MySQL :: Download Connector/J](https://dev.mysql.com/downloads/connector/j/) After updgrading the driver, the connections started working again, and my `/jdbc` directory looks like this ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/d/c/dcb2fccd8fe97612366b2b63ee2edb9af93844eb.png) It obviously switched to the newest one since my connections went back to good, but they both still exist in the folder, but it does not tell you specifically which one is in use. ---
**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\ **Post date:** [January 21, 2025, 6:51pm UTC](https://forum.inductiveautomation.com/t/jdbc-upgraded-how-to-confirm-which-version-running/101191/5 "2025-01-21T18:51:41Z")
Okay, I _think_ for JDBC drivers it's not just loading everything in there, but rather, only the JAR file(s) specified by the JDBC record in the internal DB... but I'm not certain without digging into it further.