Hi everyone.
After successfully upgrading to vCenter 7 and applying the license, the time has come to upgrade the host. Host successfully upgrade itself (I can log in directly to it, iDrac is flawless), but I face exactly this issue: https://kb.vmware.com/s/article/79623
But when I type: select * from vpx_datastore_info;
I get the following error:
VCDB=# select * from vpx_datastore_info;
ERROR: relation "vpx_datastore_info" does not exist
LINE 1: select * from vpx_datastore_info;
I'm totally new to VMWare, I follow the official recommendations, but nothing helped so far. Any idea how to get past this issue?
Ciao
Also to me in the vCenters of version 6.7u3 and 7.0u2 it gives me the same error the vpx_datastore_info table is not present.
A support call should be opened.
Hi, did you solve?
I've got the same problem: https://communities.vmware.com/t5/VMware-vSphere-Discussions/Datastore-conflicts-with-an-existing-da...
rgds
Paolo
I guess the table named vpx_datastore_info does not exist in vCenter 7.0. I have checked on my newly installed vCenter Server 7.0, same...
VCDB=# select * from vpx_datastore_info;
ERROR: relation "vpx_datastore_info" does not exist
LINE 1: select * from vpx_datastore_info;
I got myself a brand new vCenter and it was gone.
It can be solved via CLI on th vCenter, but it was easier for me to reinstall it.
Yes, the problem resides in vCenter.
I've revert my host to vpshere 7.01 and problem was solved
yes 7.0.2 doesn't have vpx_datastore_info .Looking for related tables you can find below
vpx_datastore | table | vc | 64 kB |
vc | vpx_dbm_counter_metadata | table | vc | 16 kB | Database Health Monitor - Performance counters metadata
vc | vpx_dbm_counter_value | table | vc | 0 bytes | Database Health Monitor - Performance counter values
vc | vpx_device | table | vc | 8192 bytes |
vc | vpx_device_seq | sequence | vc | 8192 bytes |
vc | vpx_disabled_methods | table | vc | 8192 bytes |
vc | vpx_drsrules_seq | sequence | vc | 8192 bytes |
vc | vpx_ds_assignment | table | vc | 16 kB |
vc | vpx_ds_info | table | vc | 16 kB |
vc | vpx_ds_vmfs_extent | table | vc | 16 kB |
vc | vpx_ds_vmfs_extent_surr_key_seq | sequence | vc | 8192 bytes |
vc | vpx_dual | table | vc | 40 kB |
vc | vpx_dvhost | table | vc | 8192 bytes |
vc | vpx_dvhost_hc_mtu_result | table | vc | 0 bytes |
vc | vpx_dvhost_hc_mtu_result_surr_key_seq | sequence | vc | 8192 bytes |
vc | vpx_dvhost_hc_result | table | vc | 8192 bytes |
vc | vpx_dvhost_hc_result_surr_key_seq | sequence | vc | 8192 bytes |
vc | vpx_dvhost_hc_vlan_result | table | vc | 0 bytes |
vc | vpx_dvhost_hc_vlan_result_surr_key_seq | sequence | vc | 8192 bytes |
vc | vpx_dvhost_out_of_sync | table | vc | 0 bytes |
vc | vpx_dvport | table | vc | 8192 bytes |
vc | vpx_dvport_membership | table | vc | 0 bytes |
vc | vpx_dvport_setting | table | vc | 8192 bytes |
vc | vpx_dvport_setting_surr_key_seq | sequence | vc | 8192 bytes |
vc | vpx_dvport_vlan | table | vc | 0 bytes |
vc | vpx_dvport_vlan_surr_key_seq | sequence | vc | 8192 bytes |
vc | vpx_dvportgroup | table | vc | 8192 bytes |
vc | vpx_dvs | table | vc | 8192 bytes |
vc | vpx_dvs_blob | table | vc | 8192 bytes |
vc | vpx_dvs_blob_surr_key_seq | sequence | vc | 8192 bytes |
vc | vpx_dvs_compatible | table | vc | 8192 bytes |
vc | vpx_dvs_compatible_surr_key_seq | sequence | vc | 8192 bytes |
vc | vpx_dvs_hc_config | table | vc | 0 bytes |
vc | vpx_dvs_hc_config_surr_key_seq | sequence | vc | 8192 bytes |
vc | vpx_dvs_infra_res_pool | table | vc | 8192 bytes |
vc | vpx_dvs_infra_res_pool_surr_key_seq | sequence | vc | 8192 bytes |
vc | vpx_dvs_ipfix | table | vc | 0 bytes |
vc | vpx_dvs_ipfix_surr_key_seq | sequence | vc | 8192 bytes |
vc | vpx_dvs_lag | table | vc | 8192 bytes |
vc | vpx_dvs_lag_surr_key_seq | sequence | vc | 8192 bytes |
vc | vpx_dvs_lag_vlan
between you can find list of tables through this command
\d+
Hope you find this helpful
KB needs update. vpx_datastore _info was there till 6.5 and no more used in later versions.
To find ID use : select ID from VPX_ENTITY where name ='datastore_name';