@cool_ashfaque @Dalaj Can you please try below steps on source vCenter Server :
- Backup vCenter Server (Take Powered Off snapshot of all vCenter Servers if VC is part of Enhanced Linked Mode)
- SSH to VCSA
- Connect to Postgres Database using command - "/opt/vmware/vpostgres/current/bin/psql -d VCDB -U postgres"
- Execute below query in VCDB prompt
alter table vc.vsan_historical_health drop constraint uk_vsan_historical_health;
- Execute below query to create a unique index
CREATE UNIQUE INDEX IF NOT EXISTS UK_VSAN_HISTORICAL_HEALTH on VC.VSAN_HISTORICAL_HEALTH (
CLUSTER_ID,
GROUP_ID,
TEST_ID,
CREATION_TIME
) TABLESPACE hs4;
- Ideally, you can retry the upgrade after this step. If not, please share result of below Two queries and based on the result I can confirm if you are good to retry the upgrade
Query - 1
select i.relname idxname, t.relname tablename, idx.indisunique
from pg_index idx
join pg_class i on (idx.indexrelid = i.oid)
join pg_class t on (t.oid = idx.indrelid)
where t.relname like 'vsan_historical_health%'
and idx.indisunique = true;
Query - 2
select t.relname rablename, con.conname, con.contype
from pg_constraint con
join pg_class t on (t.oid = con.conrelid)
where t.relname like 'vsan_historical_health%';
- Exit from VCDB using command \q
