Flyway can't calculate the checksum of a large SQL script

Which version and edition of Flyway are you using?

6.0.2

If this is not the latest version, can you reproduce the issue with the latest one as well?

Yes

Which client are you using? (Command-line, Java API, Maven plugin, Gradle plugin)

Command-line

Which database are you using (type & version)?

Oracle 12.1

Which operating system are you using?

Windows

What did you do?

I exported my database using SQL Developer, creating a SQL file ~32MB in size which I used as an effective baseline. When I tried to run flyway info, I got the following error:

Unable to calculate checksum for V001.001__BaselineScript.sql: Input length = 1
: Running flyway info failed: "C:\Program Files\flyway\flyway.cmd" exited with code 1
Flyway Enterprise Edition (unlimited schemas) 6.0.2 by Redgate
Database: jdbc:oracle:thin:@//localhost:1521/db (Oracle 12.1)

ERROR: Unable to calculate checksum for V001.001__BaselineScript.sql: Input length = 1

What did you expect to see?

I expected to see a standard flyway info response. The SQL script is valid and can be run in SQL Developer. When I tried to do something similar but on a much smaller database it all worked which suggests the size of the file is causing the problem.

What did you see instead?

See error as described above

[rscero]

Wanted to add a bit to this discussion. Had this exact problem yesterday, ERROR: Unable to calculate checksum of <script file> Input Length=1. Looked through many discussions, went down the rabbit hole testing them, none of them worked. Script was not large at all, ran the repair command, even tried converting the encoding between UTF-8 and ANSI. Nothing worked. To make it more confusing, the procedure being changed hadn’t been updated in probably 4-5 years (prior to us using flyway), the change was minor, and the change script code, when run in SQL, ran fine. After a LOT of testing, found the issue. Our procedures have a comment header that maintains information on history of changes and other info. Part of that header is a copyright statement. Example: –COPYRIGHT 2011 … Well, in this particular procedure, that had been set at: © 2011… Yep, it was the © character that was causing the issue. Removed that, added COPYRIGHT statement, problem solved.

[hdiass]

@rscero saved hours of my life, Cheers to you!