# There are outstanding changes to the database

**URL:** <https://dmap-community.ductus.global/t/there-are-outstanding-changes-to-the-database/3938>\
**Category:** CDB and CDB API\
**Created:** [January 13, 2022, 3:30am UTC](https://dmap-community.ductus.global/t/there-are-outstanding-changes-to-the-database/3938 "2022-01-13T03:30:26Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![gelear](https://avatars.discourse-cdn.com/v4/letter/g/f08c70/32.png) [@gelear](https://dmap-community.ductus.global/u/gelear)\
**Post date:** [January 13, 2022, 3:30am UTC](https://dmap-community.ductus.global/t/there-are-outstanding-changes-to-the-database/3938/1 "2022-01-13T03:30:26Z")

</div>

Hi

Confd reports error as title. Anyone knows how to solve it?

Thanks.

---

<div class="post-metadata">

**Author:** ![mvf](https://yyz2.discourse-cdn.com/flex010/user_avatar/dmap-community.ductus.global/mvf/32/182_2.png) [@mvf](https://dmap-community.ductus.global/u/mvf)\
**Post date:** [January 13, 2022, 3:21pm UTC](https://dmap-community.ductus.global/t/there-are-outstanding-changes-to-the-database/3938/2 "2022-01-13T15:21:15Z")

</div>

This means that you are trying to lock “dirty” candidate datastore. As [RFC 6241](https://datatracker.ietf.org/doc/html/rfc6241#section-7.5) mandates, you cannot lock candidate until you either commit or roll back (discard) changes.

---

<div class="post-metadata">

**Author:** ![gelear](https://avatars.discourse-cdn.com/v4/letter/g/f08c70/32.png) [@gelear](https://dmap-community.ductus.global/u/gelear)\
**Post date:** [January 14, 2022, 2:44am UTC](https://dmap-community.ductus.global/t/there-are-outstanding-changes-to-the-database/3938/3 "2022-01-14T02:44:44Z")

</div>

Thanks. Problem is solved. It’s caused by no `<error-option>rollback-on-error</error-option>`  
xml.