how to override flywaydb V4.2.0 oracle system schema clean changes
Among the changes in flywaydb V4.2.0 is enforcement of disabling of the clean function for oracle system schemas. This is a sensible move, but is causing issues for us because we have numerous schemas that have been created, perhaps naively, in the root container in oracle 12c. This means that we have many schemas that are considered by flyway to be oracle system schemas, though they are in fact user created, which it refuses to clean. The most technically correct solution would be to create these schemas in a PDB rather than the root container, but due to the work required to migrate to a PDB with the large number of schemas that we have it may well not be an option that the business is willing to consider, certainly not in a big-bang way that affects all schemas at once. Ideally we would like to be able to override or modify the behaviour of flyway when working with these schemas to allow clean during development and testing. Is there an existing solution that would permit this, either by setting a flyway execution option or by changing metadata in the target database? This will allow us to migrate at an appropriate pace to properly configured PDB containers and still upgrade to V4.2.0 or later flyway versions. Without a solution to this we are stuck with flyway V4.1.2 until we have migrated all schemas that we work with.
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
Flyway: how to find out maximum version available to migrate()?
Using flyway to efficiently manage repeatable scripts
getting started with flyway for one with no java experience