Java 引起：org.flywaydb.core.api.FlywayException：验证失败。迁移 2 的迁移校验和不匹配

Question

提问by

I tried to find the solution for the below problem, but none of them worked for me. I am developing Angular + Spring Bootapplication using MySQL + flyway. Please guide whats going wrong here.

我试图找到以下问题的解决方案，但没有一个对我有用。我正在使用MySQL + flyway开发Angular + Spring Boot应用程序。请指导这里出了什么问题。

org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'flywayInitializer' defined in class path resource [org/springframework/boot/autoconfigure/flyway/FlywayAutoConfiguration$FlywayConfiguration.class]: Invocation of init method failed; nested exception is org.flywaydb.core.api.FlywayException: Validate failed. Migration Checksum mismatch for migration 2
-> Applied to database : 1499248173
-> Resolved locally    : -1729781252
    at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1578) ~[spring-beans-4.2.4.RELEASE.jar:4.2.4.RELEASE]
    at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:545) ~[spring-beans-4.2.4.RELEASE.jar:4.2.4.RELEASE]
    at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:482) ~[spring-beans-4.2.4.RELEASE.jar:4.2.4.RELEASE]
    at org.springframework.beans.factory.support.AbstractBeanFactory.getObject(AbstractBeanFactory.java:306) ~[spring-beans-4.2.4.RELEASE.jar:4.2.4.RELEASE]
    at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:230) ~[spring-beans-4.2.4.RELEASE.jar:4.2.4.RELEASE]
    at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:302) ~[spring-beans-4.2.4.RELEASE.jar:4.2.4.RELEASE]
    at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:197) ~[spring-beans-4.2.4.RELEASE.jar:4.2.4.RELEASE]
    at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:296) ~[spring-beans-4.2.4.RELEASE.jar:4.2.4.RELEASE]
    at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:197) ~[spring-beans-4.2.4.RELEASE.jar:4.2.4.RELEASE]
    at org.springframework.context.support.AbstractApplicationContext.getBean(AbstractApplicationContext.java:1054) ~[spring-context-4.2.4.RELEASE.jar:4.2.4.RELEASE]
    at org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:829) ~[spring-context-4.2.4.RELEASE.jar:4.2.4.RELEASE]
    at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:538) ~[spring-context-4.2.4.RELEASE.jar:4.2.4.RELEASE]
    at org.springframework.boot.context.embedded.EmbeddedWebApplicationContext.refresh(EmbeddedWebApplicationContext.java:118) ~[spring-boot-1.3.1.RELEASE.jar:1.3.1.RELEASE]
    at org.springframework.boot.SpringApplication.refresh(SpringApplication.java:764) [spring-boot-1.3.1.RELEASE.jar:1.3.1.RELEASE]
    at org.springframework.boot.SpringApplication.doRun(SpringApplication.java:357) [spring-boot-1.3.1.RELEASE.jar:1.3.1.RELEASE]
    at org.springframework.boot.SpringApplication.run(SpringApplication.java:305) [spring-boot-1.3.1.RELEASE.jar:1.3.1.RELEASE]
    at org.springframework.boot.SpringApplication.run(SpringApplication.java:1124) [spring-boot-1.3.1.RELEASE.jar:1.3.1.RELEASE]
    at org.springframework.boot.SpringApplication.run(SpringApplication.java:1113) [spring-boot-1.3.1.RELEASE.jar:1.3.1.RELEASE]
    at com.boot.App.main(App.java:9) [classes/:na]
Caused by: org.flywaydb.core.api.FlywayException: Validate failed. Migration Checksum mismatch for migration 2
-> Applied to database : 1499248173
-> Resolved locally    : -1729781252
    at org.flywaydb.core.Flyway.doValidate(Flyway.java:1108) ~[flyway-core-3.2.1.jar:na]
    at org.flywaydb.core.Flyway.access0(Flyway.java:62) ~[flyway-core-3.2.1.jar:na]
    at org.flywaydb.core.Flyway.execute(Flyway.java:1012) ~[flyway-core-3.2.1.jar:na]
    at org.flywaydb.core.Flyway.execute(Flyway.java:1006) ~[flyway-core-3.2.1.jar:na]
    at org.flywaydb.core.Flyway.execute(Flyway.java:1418) ~[flyway-core-3.2.1.jar:na]
    at org.flywaydb.core.Flyway.migrate(Flyway.java:1006) ~[flyway-core-3.2.1.jar:na]
    at org.springframework.boot.autoconfigure.flyway.FlywayMigrationInitializer.afterPropertiesSet(FlywayMigrationInitializer.java:66) ~[spring-boot-autoconfigure-1.3.1.RELEASE.jar:1.3.1.RELEASE]
    at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeInitMethods(AbstractAutowireCapableBeanFactory.java:1637) ~[spring-beans-4.2.4.RELEASE.jar:4.2.4.RELEASE]
    at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1574) ~[spring-beans-4.2.4.RELEASE.jar:4.2.4.RELEASE]
    ... 18 common frames omitted

application.properties

应用程序属性

logging.level.org.springframework.web=DEBUG

server.port=8080

spring.h2.console.enabled=true
spring.h2.console.path=/h2

## For H2 DB
#spring.datasource.url=jdbc:h2:file:~/dasboot
#spring.datasource.username=sa
#spring.datasource.password=
#spring.datasource.driver-class-name=org.h2.Driver

## For MYSQL DB
spring.datasource.url=jdbc:mysql://localhost:3306/dasboot
spring.datasource.username=root
spring.datasource.password=root
spring.datasource.driver-class-name=com.mysql.jdbc.Driver

spring.datasource.max-active=10
spring.datasource.max-idle=8
spring.datasource.max-wait=10000
spring.datasource.min-evictable-idle-time-millis=1000
spring.datasource.min-idle=8
spring.datasource.time-between-eviction-runs-millis=1

flyway.baseline-on-migrate=true
spring.jpa.hibernate.ddl-auto=false;

#datasource.flyway.url=jdbc:h2:file:~/dasboot
#datasource.flyway.username=sa
#datasource.flyway.password=
#datasource.flyway.driver-class-name=org.h2.Driver


datasource.flyway.url=jdbc:mysql://localhost:3306/dasboot
datasource.flyway.username=root
datasource.flyway.password=root
datasource.flyway.driver-class-name=com.mysql.jdbc.Driver

pom.xml

<parent>
        <groupId>org.springframework.boot</groupId>
        <artifactId>spring-boot-starter-parent</artifactId>
        <version>1.3.1.RELEASE</version>
    </parent>

    <name>das-boot</name>
    <url>http://maven.apache.org</url>

    <properties>
        <project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
    </properties>

    <dependencies>
        <dependency>
            <groupId>org.springframework.boot</groupId>
            <artifactId>spring-boot-starter-web</artifactId>
        </dependency>
        <dependency>
            <groupId>org.springframework.boot</groupId>
            <artifactId>spring-boot-starter-data-jpa</artifactId>
        </dependency>
        <dependency>
            <groupId>com.h2database</groupId>
            <artifactId>h2</artifactId>
        </dependency>
        <dependency>
            <groupId>org.flywaydb</groupId>
            <artifactId>flyway-core</artifactId>
        </dependency>

        <dependency>
            <groupId>org.springframework.boot</groupId>
            <artifactId>spring-boot-starter-test</artifactId>
            <scope>test</scope>
        </dependency>
        <dependency>
            <groupId>mysql</groupId>
            <artifactId>mysql-connector-java</artifactId>
        </dependency>
    </dependencies>

V2__create_shipwreck.sql

-- For H2 DB
--CREATE TABLE SHIPWRECK(
--  ID INT AUTO_INCREMENT,
--  NAME VARCHAR(255),
--  DESCRIPTION VARCHAR(2000),
--  CONDITION VARCHAR(255),
--  DEPTH INT,
--  LATITUDE DOUBLE,
--  LONGITUDE DOUBLE,
--  YEAR_DISCOVERED INT
--);

CREATE TABLE `dasboot`.`shipwreck` (
  `ID` INT NOT NULL AUTO_INCREMENT,
  `NAME` VARCHAR(255) NULL,
  `DESCRIPTION` VARCHAR(2000) NULL,
  `CONDITION` VARCHAR(255) NULL,
  `DEPTH` INT NULL,
  `LATITUDE` DOUBLE NULL,
  `LONGITUDE` DOUBLE NULL,
  `YEAR_DISCOVERED` INT NULL,
  PRIMARY KEY (`ID`));

Answer 1

回答by Kyle Anderson

Flyway is comparing the checksum of the SQL script with that of the previously run checksum. This exception typically occurs if you change a SQL script that has already been applied by Flyway, thus causing a checksum mismatch.

Flyway 正在将 SQL 脚本的校验和与之前运行的校验和进行比较。如果您更改已被 Flyway 应用的 SQL 脚本，通常会发生此异常，从而导致校验和不匹配。

If this is development, you can drop your database and start the migrations from scratch.

如果这是开发，您可以删除数据库并从头开始迁移。

If you're in production, never edit SQL scripts that have already been applied. Only create new SQL scripts going forward.

如果您在生产环境中，切勿编辑已应用的 SQL 脚本。以后只创建新的 SQL 脚本。

Answer 2

回答by Moebius

IF YOU ARE NOT IN PRODUCTION, you can look in your flywayTablein the data base and remove the line which contain the name of the script which has been applied.

如果您不在生产中，您可以在数据库中查看flywayTable并删除包含已应用脚本名称的行。

flywayTableis a project option which define the name of the table in the db used by flyway which contain information about the version of this db, already applied scripts...

flywayTable是一个项目选项，它定义了 flyway 使用的数据库中表的名称，其中包含有关此数据库版本的信息，已应用的脚本...

Answer 3

回答by YouAreAwesome

The best solution would be to do these steps :

最好的解决方案是执行以下步骤：

Delete the file called - V2__create_shipwreck.sql, clean and build the project again.
Run the project again, login into h2 and delete the table called "schema_version".
drop table schema_version;
Now make V2__create_shipwreck.sql file with ddl and rerun the project again.

Do remember this, add version 4.1.2 for flyway-core in pom.xml like

<dependency>
    <groupId>org.flywaydb</groupId>
    <artifactId>flyway-core</artifactId>
    <version>4.1.2</version>
</dependency>

删除名为 - V2__create_shipwreck.sql 的文件，清理并再次构建项目。
再次运行项目，登录 h2 并删除名为“schema_version”的表。
删除表 schema_version；
现在使用 ddl 创建 V2__create_shipwreck.sql 文件并再次重新运行该项目。

请记住这一点，在 pom.xml 中为 flyway-core 添加 4.1.2 版本，例如

<dependency>
    <groupId>org.flywaydb</groupId>
    <artifactId>flyway-core</artifactId>
    <version>4.1.2</version>
</dependency>

It should work now. Hope this will help.

它现在应该可以工作了。希望这会有所帮助。

Answer 4

回答by Djalas

I would simply delete from schema_version the migration/s that deviates from migrations to be applied. This way you don't throw away any test data that you might have.

我会简单地从 schema_version 中删除偏离要应用的迁移的迁移。这样您就不会丢弃您可能拥有的任何测试数据。

For example:

例如：

SELECT * from schema_version order by installed_on desc

V_005_five.sql
V_004_four.sql
V_003_three.sql
V_002_two.sql
V_001_one.sql

Migrations to be applied

要应用的迁移

V_005_five.sql
* V_004_addUserTable.sql *
V_003_three.sql
V_002_two.sql
V_001_one.sql

Solution here is to delete from schema_version

这里的解决方案是从 schema_version 中删除

V_005_five.sql
V_004_four.sql

AND revert any database changes caused. for example if schema created new table then you must drop that table before you run you migrations.

并恢复导致的任何数据库更改。例如，如果架构创建了新表，那么您必须在运行迁移之前删除该表。

when you run flyway it will only re apply

当您运行 flyway 时，它只会重新适用

V_005_five.sql
* V_004_addUserTable.sql *

new schema_version will be

新的 schema_version 将是

V_005_five.sql
* V_004_addUserTable.sql *
V_003_three.sql
V_002_two.sql
V_001_one.sql

Hope it helps

希望能帮助到你

Answer 5

回答by barnold

Update your schema_version record to mach the "Resolved locally" value which in your case is -1729781252

更新您的 schema_version 记录以匹配“本地解析”值，在您的情况下为 -1729781252

Answer 6

回答by Márton Szabó

Actually there is another solution, but it's a workaround, that should not be done in a properly managed project. However I met a situation, where it was not possible to go down the better road :)

实际上还有另一种解决方案，但它是一种变通方法，不应在妥善管理的项目中完成。但是我遇到了一种情况，不可能走更好的路:)

You can update the schame_version table, and actually change the checksum to the new one. This will cause the migration to go through, but can have other side effects.

您可以更新 schame_version 表，并将校验和实际更改为新的。这将导致迁移通过，但可能会产生其他副作用。

When deploying to different environments (test, uat, prod, etc) then it might happen, that you have to update the same checksum on more environments. And when it comes to gitflow, and release branches, you can easily mix up the whole.

当部署到不同的环境（test、uat、prod 等）时，可能会发生，您必须在更多环境中更新相同的校验和。当涉及到 gitflow 和 release 分支时，你可以很容易地混淆整体。

Answer 7

回答by dave

I had the same issue and deleted the complete schema from the database, yet the issue remained.

我遇到了同样的问题并从数据库中删除了完整的架构，但问题仍然存在。

I solved this by running the repair()command of flyway:

我通过运行repair()flyway 命令解决了这个问题：

flyway.repair();

Alternatively with Flyway Maven plugin:

或者使用 Flyway Maven 插件：

mvn flyway:repair

Maven plugin addition into pom.xml:

Maven 插件添加到 pom.xml 中：

<plugin>
    <groupId>org.flywaydb</groupId>
    <artifactId>flyway-maven-plugin</artifactId>
    <version>5.2.4</version>
</plugin>

BTW: I did not find what exactly went wrong.

BTW：我没有发现到底出了什么问题。

With Gradle (as per comment from Raf):

使用 Gradle（根据Raf 的评论）：

./gradlew flywayRepair

Answer 8

回答by Chloe

Flyway changed the way it calculates the checksums from version 3 to version 5. You can re-calculate the checksums. Since the Flyway plugin doesn't properly read the Spring datasource properties, you have to manually specify them on the command line (or one of the other various ways Flyway accepts).

Flyway 将其计算校验和的方式从版本 3 更改为版本 5。您可以重新计算校验和。由于 Flyway 插件没有正确读取 Spring 数据源属性，您必须在命令行（或 Flyway 接受的其他各种方式之一）上手动指定它们。

mvn flyway:repair -Dflyway.user=root -Dflyway.password= -Dflyway.url=jdbc:mysql://localhost:3306/mydatabase -Dflyway.table=schema_version

Flyway also changed the table it stores the checksums, so you also have to specify flyway-table=schema_versionto use your old table, or else it will give you a warning (and probably an error in version 6).

Flyway 还更改了它存储校验和的表，因此您还必须指定flyway-table=schema_version使用旧表，否则它会给您一个警告（并且可能是版本 6 中的错误）。

[INFO] Repairing Schema History table for version 2 (Description: create sources, Type: SQL, Checksum: 2125962141)  ...
[INFO] Repairing Schema History table for version 3 (Description: create stats, Type: SQL, Checksum: 389912194)  ...
[INFO] Repairing Schema History table for version 4 (Description: add user encrypted, Type: SQL, Checksum: 182607572)  ...

Answer 9

回答by Stephane

If you are sure that the modification in the SQL file has no impact on your existing schema, you can also update the checksum of the existing schema.

如果您确定 SQL 文件中的修改对您现有的架构没有影响，您还可以更新现有架构的校验和。

I did this following a slight change in the sql file.

我在 sql 文件中稍作更改后执行了此操作。

Here is how I updated the checksum:

这是我更新校验和的方法：

update flyway_schema_history set checksum = '-1934991199' where installed_rank = '1';

Answer 10

回答by Eliran_Mesika

simple solution will be change spring.datasource.url=jdbc:h2:file:~/dasboot in application.properties to new file name like : spring.datasource.url=jdbc:h2:file:~/dasboots

简单的解决方案是将 application.properties 中的 spring.datasource.url=jdbc:h2:file:~/dasboot 更改为新文件名，例如： spring.datasource.url=jdbc:h2:file:~/ dasboots

Java 引起：org.flywaydb.core.api.FlywayException：验证失败。迁移 2 的迁移校验和不匹配

提问by

回答by Kyle Anderson

回答by Moebius

回答by YouAreAwesome

回答by Djalas

回答by barnold

回答by Márton Szabó

回答by dave

回答by Chloe

回答by Stephane

回答by Eliran_Mesika

相关推荐

最近更新

标签

Java 引起：org.flywaydb.core.api.FlywayException：验证失败。迁移 2 的迁移校验和不匹配

提问by

回答by Kyle Anderson

回答by Moebius

回答by YouAreAwesome

回答by Djalas

回答by barnold

回答by Márton Szabó

回答by dave

回答by Chloe

回答by Stephane

回答by Eliran_Mesika

相关推荐

Java Android - 错误：任务 ':app:mergeDebugResources' 执行失败

Java 中的函数指针

在 Java 代码中访问 AWS Lambda 环境变量

Java 使用 JNDI 添加 LDAP 条目

相关推荐

最近更新

标签