Error[VdbError] (-5) The data being fetched is NULL at column position 18 for "VPX_DS_INFO.MAX_PHYSICAL_RDM_FILE_SIZE"
yyyy-mm-ddThh:mm:ss.Z INFO firstbootInfrastructure [Failed] /usr/lib/vmware-vpx/firstboot/vpxd_firstboot.py is complete
yyyy-mm-ddThh:mm:ss.Z WARNING firstbootInfrastructure Bug component info file does not exist
yyyy-mm-ddThh:mm:ss.Z INFO firstbootInfrastructure Firstboot duration: 1396 sec
yyyy-mm-ddThh:mm:ss.Z INFO firstbootInfrastructure First boot is a failure
yyyy-mm-ddThh:mm:ss.z Invoked command: ['/usr/sbin/vpxd', '-L']
yyyy-mm-ddThh:mm:ss.z RC = 2
Stdout
Stderr
yyyy-mm-ddThh:mm:ss.Z VirtualCenter firstboot failed
yyyy-mm-ddThh:mm:ss.z error vpxd[32030] [Originator@6876 sub=Main] Init failed. VdbError: Error[VdbError] (-5) The data being fetched is NULL at column position 18 for "VPX_DS_INFO.MAX_PHYSICAL_RDM_FILE_SIZE"
--> Backtrace:
VMware vCenter Server Appliance 6.5.x
VMware vCenter Server 6.5.x
VMware vCenter Server Appliance 6.7.x
VMware vCenter Server 6.7.x
This issue occurs when there are one or more entries are having null values which causes vpxd firstboot failure in the table vpx_datastore_info the MAX_PHYSICAL_RDM_FILE_SIZE or MAX_VIRTUAL_RDM_FILE_SIZE.
To resolve this issue:
/opt/vmware/vpostgres/current/bin/psql -d VCDB -U postgres
Select * from vpx_datastore_info where MAX_PHYSICAL_RDM_FILE_SIZE is NULL;
Select * from vpx_datastore_info where MAX_VIRTUAL_RDM_FILE_SIZE is NULL;
UPDATE vpx_datastore_info set MAX_PHYSICAL_RDM_FILE_SIZE= <size> where MAX_PHYSICAL_RDM_FILE_SIZE is null;
UPDATE vpx_datastore_info set MAX_PHYSICAL_RDM_FILE_SIZE= <size> where MAX_VIRTUAL_RDM_FILE_SIZE is null;
UPDATE vpx_datastore_info set MAX_PHYSICAL_RDM_FILE_SIZE= 68169720922112 where MAX_PHYSICAL_RDM_FILE_SIZE is null;