When upgrading from TDM Portal 4.10.0.39 to 4.10.72.0, the CA Test Data Manager Service tries to start but shuts down. We see the following error in the TDM Portal startup.log:
SEVERE: Schema migration failed with exit code '4'.
Release : 4.10
Component : TDM Web Portal
In the TDMSchemaManagmentStartup.log we see:
2022-08-08 20:26:56.326 UTC [ERROR] --- c.ca.tdm.schema.Main: Migration failed: 'FlywayException: Validate failed: Detected failed migration to version 4.10.0.08 (widen tsc id columns)'
org.flywaydb.core.api.FlywayException: Validate failed: Detected failed migration to version 4.10.0.08 (widen tsc id columns)
at org.flywaydb.core.Flyway.doValidate(Flyway.java:1065)
at org.flywaydb.core.Flyway.access$100(Flyway.java:72)
at org.flywaydb.core.Flyway$1.execute(Flyway.java:975)
at org.flywaydb.core.Flyway$1.execute(Flyway.java:971)
at org.flywaydb.core.Flyway.execute(Flyway.java:1464)
at org.flywaydb.core.Flyway.migrate(Flyway.java:971)
at com.ca.tdm.schema.SchemaMigrator.migrate(SchemaMigrator.java:90)
... 2 common frames omitted
Wrapped by: com.ca.tdm.schema.ProcessingException: Migration failed: 'FlywayException: Validate failed: Detected failed migration to version 4.10.0.08 (widen tsc id columns)'
at com.ca.tdm.schema.SchemaMigrator.migrate(SchemaMigrator.java:92)
at com.ca.tdm.schema.Main.run(Main.java:104)
at com.ca.tdm.schema.Main.main(Main.java:67)
The error only tells us the migration failed, but does not show why. The original TDMSchemaManagmentStartup.log, which was created when the migration first failed, might contain more information if it is still available.
Without the original TDMSchemaManagmentStartup.log to refer to, we cannot determine the root cause.
To correct the migration issue, have your DBA, or someone who has access to the Repository database, to run the following:
UPDATE schema_version SET success = 1 WHERE success <> 1
The error "Schema migration failed with exit code '4'" can also occur if a firewall blocks access to the SQL Server database port 1433