Hi Alvin, Deleting from liquibasechangeloglock is safe.
The idea is that when you start OpenMRS liquibase writes to that table to indicate it's "in progress", but if things crash for any reason, it remains in the "locked" state. So as long as you know that no code is actively running updates against the database, it's safe to delete from liquibasechangeloglock. -Darius On Mon, May 14, 2012 at 5:37 PM, alvin.marcelo <[email protected]>wrote: > Dear all, > > Our Openmrs installs have been encountering errors which have been > attributed to the liquibaselock process not having been completed. I'll ask > the field team to post the errordetails. > > My concern is the workaround they developed: > > They run a delete from liquibaselock which solves the problem. Is this > safe? > > _________________________________________ > > To unsubscribe from OpenMRS Implementers' mailing list, send an e-mail to > [email protected] with "SIGNOFF openmrs-implement-l" in the > body (not the subject) of your e-mail. > > [mailto:[email protected]?body=SIGNOFF%20openmrs-implement-l] > _________________________________________ To unsubscribe from OpenMRS Implementers' mailing list, send an e-mail to [email protected] with "SIGNOFF openmrs-implement-l" in the body (not the subject) of your e-mail. [mailto:[email protected]?body=SIGNOFF%20openmrs-implement-l]
