vSphere DRS functionality was impacted due to unhealthy state vSphere Cluster Services caused by the unavailability of vSphere Cluster Service VMs. vSphere Cluster Service VMs are required to maintain the health of vSphere DRS./var/log/vmware/eam/eam.log you see the following entries:YYYY-MM-DDTHH:MM:SS | ERROR | vlsi | DispatcherImpl.java | 468 | Internal server error during dispatch com.vmware.vim.binding.eam.fault.EamServiceNotInitialized: EAM is still loading from database. Please try again later.
YYYY-MM-DDTHH:MM:SS | INFO | vim-monitor | VcListener.java | 125 | Full stack trace: com.vmware.eam.db.PersistenceException: Found inconsistency in the DB! There is no VM factory referred by agency HostVMAgency(ID:'Agency:##########:null')
VMware vCenter Server 7.x
VMware vCenter Server 8.x
Stale ESX Agent Manager (EAM) agent entries are present in the vCenter Server database (VCDB). When the EAM service attempts to fetch these old entries during initialization, it encounters a database inconsistency that prevents the deployment of new vCLS agents
Follow these steps to remove stale EAM agent entries from the vCenter Server database.
Note: Take a snapshot of the vCenter (If this is an enhanced linked mode environment, take powered-off snapshots for consistency).
service-control --stop content-libraryservice-control --stop eamservice-control --stop vpxd/opt/vmware/vpostgres/current/bin/psql -U postgres -d VCDB
select * from VPX_EXT_DATA where EXT_ID = 'com.vmware.vim.eam' and data_key = 'Agency:##########';delete from VPX_EXT_DATA where EXT_ID = 'com.vmware.vim.eam' and data_key = 'Agency:##########';\qservice-control --start vpxdservice-control --start eamservice-control --start content-library