Error LCMVIDMIMPORT0019 during Inventory Sync - Aria Suite Lifecycle

Products

• VCF Operations/Automation (formerly VMware Aria Suite)

Issue/Introduction

Triggering an inventory sync or patching results in error code LCMVIDMIMPORT0019.

This may follow a change in the default domain tenant address of vIDM.

Logs in /var/log/vrlcm/vmware_vrlcm.log show:

com.vmware.vrealize.lcm.common.exception.LcmException: Failed to get admin token: 
	at com.vmware.vrealize.lcm.vidm.driver.rest.util.VidmServerRestUtil.loginLocalAdmin(VidmServerRestUtil.java:240)
	at com.vmware.vrealize.lcm.vidm.driver.helpers.VidmImportUtil.getPostInstallDetails(VidmImportUtil.java:271)
	at com.vmware.vrealize.lcm.vidm.core.task.VidmPostImportEnvironmentTask.execute(VidmPostImportEnvironmentTask.java:101)
	at com.vmware.vrealize.lcm.automata.core.TaskThread.run(TaskThread.java:62)
	at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
	at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
	at java.base/java.lang.Thread.run(Unknown Source)

Manual attempts to reset the vIDM admin password via CLI fail with

Exception encountered during context initialization - canceling refresh attempt:  
org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'liquibase' defined in class path resource [com/vmware/vidm/accesscontrol/db/DbDataStoreAutoConfiguration.class]:  
Invocation of init method failed; nested exception is liquibase.exception.LockException: Could not acquire change log lock.

Environment

• Aria Suite Lifecycle 8.1x
• VMware Identity Manager (vIDM) / Workspace ONE Access 3.3.x

Cause

A stale Liquibase lock exists on the vIDM database, specifically within the saas.DATABASECHANGELOGLOCK table. This prevents the Lifecycle Manager from obtaining the necessary admin token to complete synchronization or patching tasks.

Resolution

In order to resolve this follow the below steps :

1. Take a snapshot of the vIDM appliance(s) before proceeding.
2. Verify the entries in runtime-config.properties (located in /usr/local/horizon/conf).
   • Single-node: Ensure gateway.hostname and configurator.hostname match.
   • Cluster: Set gateway.hostname to the Load Balancer FQDN and configurator.hostname to the individual node FQDN.
3. Restart services and verify connectivity.
4. If the error persists, clear the stale database lock:
   • Log in to the vIDM database.
   • Identify and clear the lock in the saas.DATABASECHANGELOGLOCK table as detailed in KB 319309.
5. Retry the Inventory Sync or Patching task in Aria Suite Lifecycle.

Additional Information

• For issues relating to password updates, see KB 302049.
• To speak with a customer representative or a Support Engineer, see Contact Support. Scroll to the bottom of the page and click on your respective region.