|
Hi Ivy Team I am getting following error message during Ivy startup after I migrated to the 7.3.1 image : java.lang.Exception: The system database (jdbc:postgresql://10.172.0.9:5432/ivysystemdb_7) with all tables already exists (Version: 50). But was created with a older version of the ivy Engine. at ch.ivyteam.ivy.server.configuration.command.CreateDbCommand.checkIfCreationNeeded(CreateDbCommand.java:114) at ch.ivyteam.ivy.server.configuration.command.CreateDbCommand.createSystemDatabase(CreateDbCommand.java:63) at ... What has to be done to fix this problem. Thanks & Regards John |
|
Hello @John Moser The system database needs to be converted. Classically, you started the Engine Configuration UI and clicked on the button I think for the container use case, our We provide additionally a Command Line Tool, called EngineConfigCLI (https://developer.axonivy.com/doc/latest/EngineGuideHtml/tools.html#tool-engineconfigcli). This CLI is also able to convert the database. This CLI tool is also available in our docker image. Be aware that a migration can take some time. Attention: Always make a backup of the SystemDb before converting. I tried the autoConvert solution but it did not work. I even installed/started an "empty" Ivy. If you look at the stack trace, it fails always at the same code line ch.ivyteam.ivy.server.configuration.command.CreateDbCommand.checkIfCreationNeeded(CreateDbCommand.java:114) at and looking at the name of the method, it looks like it does not even attempt to convert. It seems to me that you are using the CLI tool and calling the creation command? e.g. No ... I am running the following flag in ivy.yaml : # If set to true the system database is automatically converted to the latest version during startup of the Axon.ivy Engine if needed. Autoconvert: true My expectation is that during the startup of Ivy this flag will cause the db to convert so that Ivy 7.3.1 can be run. So my question is, does this flag work at all ? PS: imho I would be surprised if this works, if you have a real big sys db, how do you make sure that the Ivy startup can be delayed for so long ? I double checked your issue and can now explain why this happens. Our docker image provides an own docker-entrypoint.sh and execute create-db before starting, to bootstrap a db. But in this scenario this commando will fail. We will fix that for 8.0 (XIVY-3343). As workaround you can override the docker-entrypoint.sh with a more intelligent implementation. See https://developer.axonivy.com/doc/latest/engine-guide/getting-started/docker.html We can not ensure that ivy startup is delayed for so long. You need to prepare a maintenance window for your user. Ok ... then we will use the CLI. Btw I just saw that 7.4 is out. Should we (from KLARA) move right to 7.4 or first move to 7.3.1 ? I recommend to go directly to 7.4.we have improved db migration scripts between 7.2 unf 7.3. we'd love to get early feedback on the 7.4 release. And migrators could benefit of the enhanced cockpit and migration scripts. However, a 7.4 migration must be carefully considered since with it the migration to java11 and primeFaces 7.0 is enforced with it. So it might take some manual migration steps...
showing 5 of 7
show 2 more comments
|
Once you sign in you will be able to subscribe for any updates here
By RSS:Markdown Basics
Tags:
Asked: 29.08.2019 at 10:33
Seen: 1,467 times
Last updated: 18.09.2019 at 02:46
