Hello
Yes, the databasechangeloglock looks this way

So, regarding your problem, is that you copied the production tables, and they contain something that is not in sync with your Jmix liquibase changelogs locally.
Nope. The production system is running the same program without any problem. When I switch off the liquibase generation, the system is running as expected 
The problem occurs, meanwhile generating not executing the liquibase files …
So if I click on

I get another errorbox

The generation process should not change anything on the database, isn’t it ?
But, I found a problem
In the entity, conAddfloat1 is defined as double ( generation from database ).
In the MSSQL DB the column exists as a float, no problem.
In the MariaDb the column exists as a float → problem generating the liquibase log.
I think, this is a new feature ? For me I can solve now the problem, changing all the entities, but for somebody else, this might be a problem.
Regards
Felix