# Message regarding an empty result set for databasechangeloglock

**URL:** <https://forum.liquibase.org/t/message-regarding-an-empty-result-set-for-databasechangeloglock/1487>\
**Category:** Liquibase Development\
**Created:** [February 22, 2011, 5:52pm UTC](https://forum.liquibase.org/t/message-regarding-an-empty-result-set-for-databasechangeloglock/1487 "2011-02-22T17:52:00Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![greg\_henry](https://avatars.discourse-cdn.com/v4/letter/g/d78d45/32.png) [@greg\_henry](https://forum.liquibase.org/u/greg_henry)\
**Post date:** [February 22, 2011, 5:52pm UTC](https://forum.liquibase.org/t/message-regarding-an-empty-result-set-for-databasechangeloglock/1487/1 "2011-02-22T17:52:00Z")

</div>

Hello&nbsp;

Since i’ve changed from 1.9.5 to 2.0.x I get the following error when i try to sync a new database

Greg

---

<div class="post-metadata">

**Author:** ![greg\_henry](https://avatars.discourse-cdn.com/v4/letter/g/d78d45/32.png) [@greg\_henry](https://forum.liquibase.org/u/greg_henry)\
**Post date:** [February 22, 2011, 5:52pm UTC](https://forum.liquibase.org/t/message-regarding-an-empty-result-set-for-databasechangeloglock/1487/2 "2011-02-22T17:52:00Z")

</div>

Hello Nathan

yes , databasechangeloglock is empty,&nbsp;

if i add a dummy record, the error is &nbsp;not raised.

the table is created by our standard tables setup … and is still in 1.9 format (does it change between 1.9 and 2.0 ?)

Greg

---

<div class="post-metadata">

**Author:** ![nvoxland](https://avatars.discourse-cdn.com/v4/letter/n/87869e/32.png) [@nvoxland](https://forum.liquibase.org/u/nvoxland)\
**Post date:** [February 22, 2011, 5:52pm UTC](https://forum.liquibase.org/t/message-regarding-an-empty-result-set-for-databasechangeloglock/1487/3 "2011-02-22T17:52:00Z")

</div>

It means that there is a databasechangeloglock table, but no data in it. &nbsp;If you drop the table it should be recreated with the expected row in it. &nbsp;I’m not sure why it wasn’t populated correctly. &nbsp;if you select \* from databasechangeloglock there are now rows, correct?

Nathan