Filr 3.2 upgrade fails with Liquibase Error Incorrect syntax

  • 7022391
  • 28-Nov-2017
  • 12-Dec-2017

Environment

Micro Focus Filr 3.2
MS SQL Server

Situation

Filr 3.0, 3.1 and 3.1.1 deployments with MS-SQL Server as database may run into a liquibase error during the schema update which takes place during the Filr 3.2 Update. As a result, the update will remain incomplete and will have to be restarted manually after correcting the schema error condition. When this happens, the following error is logged in the /var/log/zypp/history file:

INFO 11/10/17 3:27 AM:liquibase: Successfully acquired change log lock
INFO 11/10/17 3:27 AM:liquibase: Reading from [dbo].[DATABASECHANGELOG]
INFO 11/10/17 3:27 AM:liquibase: Reading from [dbo].[DATABASECHANGELOG]
SEVERE 11/10/17 3:27 AM:liquibase: Change Set scripts/changelog/sqlserver-changelog-filrproton.xml::6::dhivya failed. 
     Error: Migration failed for change set scripts/changelog/sqlserver-changelog-filrproton.xml::6::dhivya:
     Reason:
          scripts/changelog/sqlserver-changelog-master.xml : Incorrect syntax near '<'.:
          Caused By: Precondition Error
          liquibase.exception.MigrationFailedException: Migration failed for change set
          scripts/changelog/sqlserver-changelog-filrproton.xml::6::dhivya:
     Reason:
          scripts/changelog/sqlserver-changelog-master.xml : Incorrect syntax near '<'.:
          Caused By: Precondition Error
    at liquibase.changelog.ChangeSet.execute(ChangeSet.java:285)
    at liquibase.changelog.visitor.UpdateVisitor.visit(UpdateVisitor.java:27)
    at liquibase.changelog.ChangeLogIterator.run(ChangeLogIterator.java:58)
    at liquibase.Liquibase.update(Liquibase.java:114)
    at liquibase.integration.commandline.Main.doMigration(Main.java:825)
    at liquibase.integration.commandline.Main.main(Main.java:134)


Resolution

A fix for this issue is available in Filr 3.3 Update. With the fix in place, if the upgrade is attempted from Filr 3.0, 3.1 or 3.1.1 directly to Filr 3.3 the error will be prevented and the schema update will succeed.

Feedback service temporarily unavailable. For content questions or problems, please contact Support.