[Solved] Unable to upgrade to 2.6.1

Unimus support forum
Post Reply
g4mbr1nus
Posts: 2
Joined: Wed Jun 19, 2024 8:35 am

Wed Jan 08, 2025 9:45 am

Hi,

I tried to upgrade version to 2.6.1 but database update failed:

Code: Select all

2025-01-08 10:31:00.935  INFO 240353 --- [main] software.netcore.bootstrap.UnimusServer  : Starting UnimusServer v2.6.1 using Java 11.0.25 on mon-frontend with PID 240353 (/opt/unimus/Unimus.jar started by root in /opt/unimus)
2025-01-08 10:31:00.939  INFO 240353 --- [main] software.netcore.bootstrap.UnimusServer  : The following 7 profiles are active: "unix", "unimus-unix", "jar", "unimus", "core", "LOCAL", "PUBLIC"
2025-01-08 10:31:37.793  INFO 240353 --- [main] n.u._.infrastructure.fqdn.FqdnResolver   : FQDN successfully resolved to 'mon-frontend'
2025-01-08 10:31:51.851  INFO 240353 --- [main] software.netcore.bootstrap.UnimusServer  : Started UnimusServer in 53.654 seconds (JVM running for 55.391)
2025-01-08 10:31:51.895  INFO 240353 --- [multicaster-3] s.netcore.starter.AppStartTimeMonitor    : Application started in: 40.748 seconds
2025-01-08 10:31:53.048  INFO 240353 --- [SimpleAsyncTaskExecutor-1] s.b.b.s.LoggingPathAccessibilityBootStep : Checking logging subsystem
2025-01-08 10:31:53.060  INFO 240353 --- [SimpleAsyncTaskExecutor-1] .s.b.b.s.DatabaseConnectionCheckBootStep : Testing database connection
2025-01-08 10:31:53.999  INFO 240353 --- [SimpleAsyncTaskExecutor-1] .s.b.b.s.DatabaseConnectionCheckBootStep : Database connection test passed
2025-01-08 10:31:54.005  INFO 240353 --- [SimpleAsyncTaskExecutor-1] n.u.s.b.b.step.DatabaseUpdateBootStep    : Connecting to database (MYSQL, jdbc:mysql://192.168.169.241:6446/unimus?allowPublicKeyRetrieval=true&useSSL=false&serverTimezone=UTC)
2025-01-08 10:31:54.006  INFO 240353 --- [SimpleAsyncTaskExecutor-1] n.u.s.b.b.step.DatabaseUpdateBootStep    : Updating database schema
2025-01-08 10:32:01.473 ERROR 240353 --- [SimpleAsyncTaskExecutor-1] n.u.s.b.b.step.DatabaseUpdateBootStep    : Failed to update database schema. Reason = 'liquibase.exception.LiquibaseException: org.springframework.jdbc.BadSqlGrammarException: StatementCallback; bad SQL grammar [alter table backup_segment_group add temp_index bigint]; nested exception is java.sql.SQLSyntaxErrorException: Duplicate column name 'temp_index''
Is there a way to fix that?
Thanks for the help.
Laco
Posts: 15
Joined: Thu Sep 12, 2024 10:28 am

Wed Jan 08, 2025 10:40 am

Hi.

Yes there is a way to fix it. This issue occurs when a DB upgrade is interrupted.
The fix procedure depends on your DB and your OS.

Please create Support request on our Portal https://portal.unimus.net/ and we can provide full instructions.

Best regards
Laco
Post Reply