Now we have separate the liquibase changelogs into a separate repository. The changelogs were generated from ab existing jmix database.
It is very likely to be caused by the MySQL being case-sensitive. We met others issues related to MySQL being case-sensitive and after we recreated the databases, all the issues have gone. As now we are using an approach of separating the liquibase into a repository. I am not sure if the database were case-insensitive, we may not have met the error when starting the Jmix application.