# JDBC failed after Ignition Upgrade

**URL:** <https://forum.inductiveautomation.com/t/jdbc-failed-after-ignition-upgrade/84586>\
**Category:** Ignition\
**Created:** [January 22, 2024, 7:12pm UTC](https://forum.inductiveautomation.com/t/jdbc-failed-after-ignition-upgrade/84586 "2024-01-22T19:12:03Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![anthony\_ho](https://avatars.discourse-cdn.com/v4/letter/a/59ef9b/32.png) [@anthony\_ho](https://forum.inductiveautomation.com/u/anthony_ho)\
**Post date:** [January 22, 2024, 7:12pm UTC](https://forum.inductiveautomation.com/t/jdbc-failed-after-ignition-upgrade/84586/1 "2024-01-22T19:12:03Z")

</div>

We have a Test server that mirrors a Production Server. Both have version 8.1.32. I have the latest snowflake-jdbc-3.14.4 installed on both servers and they were making connections to a Snowflake database fine.

But after the Test Server is upgraded to 8.1.36, the db connection was faulted and the driver threw an error:

> java.sql.SQLException: Cannot create PoolableConnectionFactory (JDBC driver internal error: exception creating result java.lang.NoClassDefFoundError: Could not initialize class net.snowflake.client.jdbc.internal.apache.arrow.memory.util.MemoryUtil at net.snowflake.client.jdbc.internal.apache.arrow.memory.ArrowBuf.getDirectBuffer(ArrowBuf.java:231).)

Does anyone have this experience?

---

<div class="post-metadata">

**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 22, 2024, 7:37pm UTC](https://forum.inductiveautomation.com/t/jdbc-failed-after-ignition-upgrade/84586/2 "2024-01-22T19:37:47Z")

</div>

You'll need to modify ignition.conf and add a line like this:

```auto
wrapper.java.additional.7=--add-opens=java.base/java.nio=ALL-UNNAMED

```

The number after "additional" may be different in your config, it should be the next sequential and unused number in that section.

---

<div class="post-metadata">

**Author:** ![Anthony\_Ho1](https://avatars.discourse-cdn.com/v4/letter/a/7feea3/32.png) [@Anthony\_Ho1](https://forum.inductiveautomation.com/u/Anthony_Ho1)\
**Post date:** [January 22, 2024, 9:15pm UTC](https://forum.inductiveautomation.com/t/jdbc-failed-after-ignition-upgrade/84586/3 "2024-01-22T21:15:23Z")

</div>

Yup, that fixed the issue. Thanks.

---

<div class="post-metadata">

**Author:** ![Prince\_Cyril](https://avatars.discourse-cdn.com/v4/letter/p/8e8cbc/32.png) [@Prince\_Cyril](https://forum.inductiveautomation.com/u/Prince_Cyril)\
**Post date:** [May 10, 2024, 5:03pm UTC](https://forum.inductiveautomation.com/t/jdbc-failed-after-ignition-upgrade/84586/4 "2024-05-10T17:03:41Z")

</div>

I recently worked on setting up a connection to snowflake. While working on it, I spent quite some time to figureout the right compatibility between the driver and the snowflake instance + the ignition.conf wrapper setting mentioned here.  
Suggestion to the IA team to add this in the section.

> **[JDBC Driver and Database Translator Settings | Ignition User Manual](https://docs.inductiveautomation.com/docs/8.1/platform/database-connections/connecting-to-databases/jdbc-drivers-and-translators/jdbc-driver-and-database-translator-settings#snowflake)**
>
> This page details various JDBC driver and translator settings.

---

<div class="post-metadata">

**Author:** ![Ivan\_H](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/ivan_h/32/28186_2.png) [@Ivan\_H](https://forum.inductiveautomation.com/u/Ivan_H)\
**Post date:** [September 19, 2024, 4:31pm UTC](https://forum.inductiveautomation.com/t/jdbc-failed-after-ignition-upgrade/84586/5 "2024-09-19T16:31:17Z")

</div>

Works like a charm. Thank you.
