I'm not completely clear what you mean by "Database generated databasechangelog and databasechangeloglock, but databasechangelog did not create records"
If you mean that the DATABASECHANGELOG table does not have any rows in it, then that is expected behavior.
The generateChangeLog command should not make any changes to your database, it should just capture the state of the schema as a changelog file. If you wanted to immediately then mark that database as "in sync" with the changelog, you would execute the command liquibase changeLogSync on the same database. You could, as well, use that changelog to bring a separate empty database up-to-date with the changelog by running liquibase update against the new empty database.
If that is not the problem you are having, I could interpret your question as "The databasechangelog.xml file that was created by the generateChangeLog command was empty." If that is what is happening, the most likely issue is that liquibase is either not connecting to the database you expect, or the database is indeed empty, or there are some sort of permissions problems and the credentials you are using to connect to the database are insufficient to be able to query the system tables required.
Steve Donie
Principal Software Engineer
Datical, Inc. http://www.datical.com/
Steve Donie
Principal Software Engineer
Datical, Inc. http://www.datical.com/