DB006 : Could not acquire change log lock

DB006 : Could not acquire change log lock

Symptoms

When saving the database configuration in the 360Suite Administration Console, the following error message appears:
  1. DB006 : Could not acquire change log lock

Cause

When the application is upgraded, the database structure is updated (new tables and/or columns are added or some old ones are removed).
360Suite needs to ensure that the database structure meets the needs of the application for the new version.
For that, 360Suite uses an external library called Liquibase. To avoid running multiple updates simultaneously, this tool creates sort a lock for itself on the database then processes the update.

For some reason (may be a network issue, even a short one), if this lock is not released when the schema update is finished, it will remain, hence the error message.
It can be verified by running the below command on the 360Suite database:
  1. SELECT * FROM databasechangeloglock;
This will return the content of a table with a single line, and

Resolution

To unlock the 360Suite database, use the following SQL query on the database used for 360Suite:
  1. UPDATE DATABASECHANGELOGLOCK SET LOCKED=0
After running this request and making sure the transaction was committed, the database configuration in 360Suite needs to be saved again in the Administration Console.
AlertWarning : only run this query if you are 100% sure that the application database shouldn't be blocked.
The use of this lock is typicaly useful in a clustered configuration, to avoid having all nodes trying to update the database structure at the same time.

References

  1. What is the DATABASECHANGELOGLOCK table?
  2. COMMIT – SQL Tutorial

    • Related Articles

    • Change Tomcat after 2025.1 upgrade

      Context To prepare for BI 2025 moving away from Java 8, we migrated from Java 8 to Java 21. This migration impacts everyone doing update from previous version, as the version used for Tomcat is not compatible anymore, as Java 21 requires a Tomcat 10 ...

    • How to expand Dataprovider SQL Query column in 360Eyes database

      Symptom When running 360Eyes Impact Analysis Reports (such as Report 52), users observe that the SQL query stored in the 360eyes_REPORTS.unx / Eye Document / Dataprovider / Dataprovider Sql Queryfield is incomplete, partial or truncated. This often ...

    • "DB003: No suitable driver found" when configuring 360Suite databases

      Symptoms When configuring 360Suite main database. When configuring 360Eyes database. When trying to create a 360Cast SQL source. When trying to create a 360View SQL Query. In any of these situations, when the database type was selected, the following ...

    • Wrong collation for 360Eyes database on SQL Server

      Error Updating SQL Server Password in 360Eyes – Collation Issue Description After updating the SQL Server account password used in 360Eyes, attempts to update the password in the Eyes Configuration (Admin Page) result in a runtime error: [ERROR] ...

    • Audit Snapshot Fails in 360Eyes — Unsupported DB URL (jdbc:sqlanywhere)

      Symptoms When running the 360Eyes – Audit job, the job fails during DO_SPECIFIC_JOB_ACTIONS and the log displays: Could not generate snapshot : Current DB URL (jdbc:sqlanywhere:DSN=BIA_Audit_PROD) is not supported. Cause The Audit data source is ...