This worked with vCloud Director 5.6.3 with SQL 2008 database backend. You should probably check with support if this would be a fix.
Shutdown vCloud Director on the cells (VMware KB: Using the Cell Management Tool to shut down a vCloud Director cell). The vCD services must be stopped on all Cells.
Make sure you have a backup of the database!
Run the following SQL queries on the database to delete the QRTZ tables.
delete from dbo.compute_resource_inv;
delete from dbo.custom_field_manager_inv;
delete from dbo.cluster_compute_resource_inv;
delete from dbo.datacenter_inv;
delete from dbo.datacenter_network_inv;
delete from dbo.datastore_inv;
delete from dbo.datastore_profile_inv;
delete from dbo.dv_portgroup_inv;
delete from dbo.dv_switch_inv;
delete from dbo.folder_inv;
delete from dbo.managed_server_inv;
delete from dbo.managed_server_datastore_inv;
delete from dbo.managed_server_network_inv;
delete from dbo.network_inv;
delete from dbo.resource_pool_inv;
delete from dbo.storage_pod_inv;
delete from dbo.storage_profile_inv;
delete from dbo.task_inv;
delete from dbo.vm_inv;
delete from dbo.property_map;
delete from QRTZ_SCHEDULER_STATE;
delete from QRTZ_FIRED_TRIGGERS;
delete from QRTZ_PAUSED_TRIGGER_GRPS;
delete from QRTZ_CALENDARS;
delete from QRTZ_TRIGGER_LISTENERS;
delete from QRTZ_BLOB_TRIGGERS;
delete from QRTZ_CRON_TRIGGERS;
delete from QRTZ_SIMPLE_TRIGGERS;
delete from QRTZ_TRIGGERS;
delete from QRTZ_JOB_LISTENERS;
delete from QRTZ_JOB_DETAILS;
Afterwards start vCloud Director on one of the Cells (service vmware-vcd start). Do not start any other Cells.
After about 5 minutes you should be able to log back into the vCloud Director UI and if you go to System > Manage & Monitor > vSphere Resources > vCenters, you should see vCenter reconnecting and resyncing the inventory. Then once everything is back up you can start the other Cells.
