Liquibase migration error 2.0.5 to 3.5.4

General Discussion
1

When I bump liquibase version up from 2.0.5 to 3.5.4. below error has occurred.

Value too long for column "LOCKED CHAR(1) NOT NULL": "'TRUE' (4)"

It seems DATABASECHANGELOGLOCK’s LOCKED field datatype is changed char(1) to char(5).
Is there any way to avoid this issue? Should I manually update the LOCKED field datatype before running liquibase?

Thanks in advance.

2

Hi @donggyu04,

I believe you can just delete the DATABASECHANGELOGLOCK (please take back up before you do this), Liquibase should recreate the appropriate table the next time you do a Liquibase update.

-Ronak