# Emerse 6.1.x upgrade question related to DB

**URL:** <https://discourse.project-emerse.org/t/emerse-6-1-x-upgrade-question-related-to-db/66>\
**Category:** Uncategorized\
**Created:** [July 23, 2021, 11:06pm UTC](https://discourse.project-emerse.org/t/emerse-6-1-x-upgrade-question-related-to-db/66 "2021-07-23T23:06:23Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![EricMeeks](https://avatars.discourse-cdn.com/v4/letter/e/5f8ce5/32.png) [@EricMeeks](https://discourse.project-emerse.org/u/EricMeeks)\
**Post date:** [July 23, 2021, 11:06pm UTC](https://discourse.project-emerse.org/t/emerse-6-1-x-upgrade-question-related-to-db/66/1 "2021-07-23T23:06:23Z")

</div>

We’re getting ready to upgrade our system and I noticed that the latest emerse.war file doesn’t have an oracle ODBC driver jar file. Is that ok?  
I’m new to gradle and I can see that for build/dev it’s helpful to use the lightweight MariaDB, but in production we will still be on Oracle. Do I need to manually add a jar to tomcat somewhere or is this going to be OK because of Hibernate/etc.?

Thanks,  
Eric

---

<div class="post-metadata">

**Author:** ![mcclaink](https://yyz2.discourse-cdn.com/flex030/user_avatar/discourse.project-emerse.org/mcclaink/32/8_2.png) [@mcclaink](https://discourse.project-emerse.org/u/mcclaink)\
**Post date:** [July 26, 2021, 2:12pm UTC](https://discourse.project-emerse.org/t/emerse-6-1-x-upgrade-question-related-to-db/66/2 "2021-07-26T14:12:46Z")

</div>

You will need to get the JDBC jar, and put that into tomcat’s `lib` directory. It looks like I don’t have that in the installation guide, or setup guide, so I’ll have to add that. But, it is in the Upgrade guide [here](https://project-emerse.org/documentation/upgrading_guide.html#trueupgrading-from-emerse-version-6-0-to-version-6-1). You’ll also have to select the `ds.dialect` property too. For oracle, you should use a value of `org.hibernate.dialect.Oracle12cDialect`. (There isn’t a more specific dialect for Oracle 19.) I know it’s perhaps a little funky, so if you have any suggestions, let us know!

---

<div class="post-metadata">

**Author:** ![EricMeeks](https://avatars.discourse-cdn.com/v4/letter/e/5f8ce5/32.png) [@EricMeeks](https://discourse.project-emerse.org/u/EricMeeks)\
**Post date:** [August 3, 2021, 10:02pm UTC](https://discourse.project-emerse.org/t/emerse-6-1-x-upgrade-question-related-to-db/66/3 "2021-08-03T22:02:05Z")

</div>

Thanks for this. Now found another issue. The upgrade.sql script for 6.0 from [https://github.com/project-emerse/emerse/releases](https://github.com/project-emerse/emerse/releases) has an error.

Near the bottom there is a rogue line breaking the script:  
version, namely, those users who can access EMERSE.’, ‘EXECUTED’, ‘seed\_data’, NULL, ‘4.2.2’, ‘2540816332’);

Is something missing?

---

<div class="post-metadata">

**Author:** ![mcclaink](https://yyz2.discourse-cdn.com/flex030/user_avatar/discourse.project-emerse.org/mcclaink/32/8_2.png) [@mcclaink](https://discourse.project-emerse.org/u/mcclaink)\
**Post date:** [August 4, 2021, 4:11pm UTC](https://discourse.project-emerse.org/t/emerse-6-1-x-upgrade-question-related-to-db/66/4 "2021-08-04T16:11:45Z")

</div>

I think that line should not be there at all. I replaced the upgrade.sql without that line.

(We use liquibase, but we normally distribute the sql scripts with the statements related to liquibase specifically removed, and that line was a lingering part of such a liquibase-related statement.)