This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

IG refuses to start with "Unexpected database level" after upgrading from 3.7.0 to 3.7.3

Dear community,

I just checked out the new release and upgraded our demo environment on SLES/PostgreSQL (IG on dedicated host, OSP and PostgreSQL on a separate host).

The component upgrades seem to have worked without any issues with the new helper scripts.

Also, the summary of IG core installer is showing no severe errors:

Installation: Successful with errors.

523 Successes
0 Warnings
3 NonFatalErrors
0 FatalErrors

The ones listed as NonFatalErrors seem to be caused by some views that could not be created successfully by liquibase, e.g.:

"Unexpected error running Liquibase: Unterminated string literal started at position 760 in SQL CREATE VIEW ... ..."

But, when I start-up tomcat now, I almost immediately get the following error in catalina.out:

[INFO] 2022-12-08 16:39:24.146 [com.netiq.iac.persistence.dbcheck.DatabaseSchemaCheck] [IG-SERVER] Connecting to PostgreSQL version 9.6.12
[INFO] 2022-12-08 16:39:26.744 [null] liquibase: Reading from public.databasechangelog
[SEVERE] 2022-12-08 16:39:29.790 [com.netiq.iac.persistence.dbcheck.DatabaseSchemaCheck] [IG-SERVER]
=================== FATAL ERROR ===========================
Unexpected database level. Expected: 3.7.3, discovered: 3.7.0 Development
[SEVERE] 2022-12-08 16:39:29.795 [org.apache.catalina.core.StandardContext] One or more listeners failed to start. Full details will be found in the appropriate container log file

In the OPS DB I can see the following in the table:


I would suspect, that these two are related. It seems, the installer did not properly/fully upgrade the DB schema.

Has anyone seen this or knows how to fix this (I could probably put in the "expected" value directly here, but I am not sure if something else is a little off here...)?

Many thanks and best regards,