what to do when flyway update to 4.0 fails midway
I tried to update my (Oracle) database to Flyway 4.0 from Flyway 3.x today. I can see the update script tries to remove a couple of indexes (_vr_idx and _ir_idx). The problem I'm facing is the update has failed mid-way and now every time I rerun it, it complaints about the indexes not existing... How do I proceed?
This is a known issue fixed in the upcoming Flyway 4.0.1. In your case you have 3 options: Drop the schema_version table and baseline the schema with Flyway 4.0 Manually perform the remaining actions on the schema_version table, followed by repair with Flyway 4.0 Recreate the dropped indexes and try again with Flyway 4.0.1
Base directory and schema_version
flyway: db init without maven?
Flyway-1.7: workaround for dealing with branching? (Flyway issue 138)
Retry a flyway failed migration
Can I use numbers in descriptions to force a loading order for SQL files?
Flyway 1.7 migrations transaction
how does flyway lock a postgres schema?
Flyway migrate Oracle PL/SQL dump
Why version counter and not timestamps
executing more than one statement at once
How to get flyway to re-run migration?
How to build Flyway without all JDBC Drivers
How do placeholders work in Flyway?
Flyway SQL directory not found while migrating from within a war
Can Flyway find out and generate migration files from datamodel?
Flyway: Unable to find path for sql migrations