Mick Benham

Thank you for the response. I just realized the database_version in the db was showing 7.3. It looks like a previous upgrade failed but left a lock on the database. When I attempted to roll back to version 7.4 I saw the error message in the logs. I was able to successfully upgrade to 7.19. From: discussion@art.p.re.sourceforge.net discussion@art.p.re.sourceforge.net on behalf of Gerd S schnutz@users.sourceforge.net Date: Thursday, February 1, 2024 at 4:33 AM To: [art:discussion] 352129@discussion.art.p.re.sourceforge.net...

Thank you very much. Yes it looks like the automatic upgrade failed due to a lock on the database from a previous failed upgrade. The db was still showing version 7.3. After removing the lock the upgrade to 7.19 completed successfully and I can now save the settings. Sorry for not realizing this myself.

This is still an issue after upgrade to 7.19. Can anyone provide guidance?

I'm running into a similar issue. Upgraded to 7.17 but have been seeing the issue since 7.13 when experimental OAUTH was added. Tomcat 9 .0.84 Oracle 19c database JDK 11 An error occurred: java.sql.SQLException: ORA-00904: "OAUTH_CLIENT_SECRET": invalid identifier Query: INSERT INTO ART_SETTINGS (SMTP_SERVER, SMTP_PORT, SMTP_USE_STARTTLS, USE_SMTP_AUTHENTICATION, SMTP_USERNAME, SMTP_PASSWORD, SMTP_FROM, ART_AUTHENTICATION_METHOD, WINDOWS_DOMAIN_CONTROLLER, ALLOWED_WINDOWS_DOMAINS, DB_AUTHENTICATION_DRIVER,...

Any plans to upgrade the version of Jackson-databind? Current version is showing 56 vulnerabilities. com.fasterxml.jackson.core_jackson-databind version 2.9.6 has 56 vulnerabilities Fixed in 2.10.0, 2.9.10