vCenter server upgrade from 7.x to 8.x fails with "Source vCenter Server schema validation found an issue"
search cancel

vCenter server upgrade from 7.x to 8.x fails with "Source vCenter Server schema validation found an issue"

book

Article ID: 396790

calendar_today

Updated On:

Products

VMware vCenter Server

Issue/Introduction

  • vCenter server upgrade from 7.x to 8.x fails during VCDB validation stage.

  • Log file /var/log/vmware/upgrade/prechecks.json will show similar entries to:

        "error": [
            {
                "text": {
                    "id": "vcdb.error.validate.linux.vcdb",
                    "translatable": "Source vCenter Server schema validation found an issue.",
                    "localized": "Source vCenter Server schema validation found an issue."
                },

  • Log file /var/log/vmware/upgrade/CollectRequirements_com.vmware.vcdb_yyyy_mm_dd_hh_mm.log will show similar entries to:

    YYYY-MM-DDThh:mm:ss INFO vcdb.const Validating source embedded schema...
    YYYY-MM-DDThh:mm:ss ERROR vcdb.const Error while validating source vCenter Server database: Error while executing ./Upgrade-v2017-to-v2018/postgresql/validate_PostgreSQL.sql, reason: Statement failure(rc=-1).
    YYYY-MM-DDThh:mm:ss ERROR vcdb.const Error while validating source vCenter Server database: RAISE EXCEPTION 'ERROR !%',err_message_full;
    YYYY-MM-DDThh:mm:ss ERROR vcdb.const Error while validating source vCenter Server database: 1 [P0001](1) ERROR: ERROR ! Missing indexes: VPX_EVENT_18.VPXI_CHANGE_TAG_18;VPX_EVENT_18.VPXI_EVENT_CATEGORY_18;VPX_ALARM.VPX_ALARM_F1;VPX_ALARM_RUNTIME.IX_VPX_ALRT_CRTIME_STATUSVALUE;VPX_CHANGE_TAG.VPX_CHANGE_TAG_M1;VPX_COMPLIANCE_STATUS.VPX_COMPL_STATUS_ENTITY_ID_F1;VPX_COMPLIANCE_STATUS.VPX_COMPL_STATUS_PROFID_F1;VPX_COMPUTE_RES_FAILOVER_HOST.VPX_COMP_RES_FAILOVER_HOST_F1;VPX_COMPUTE_RES_USER_HB_DS.VPX_COMPUTE_RES_USER_HB_DS_F1;VPX_COMPUTE_RESOURCE.VPX_COMPUTE_RESOURCE_F1;VPX_COMPUTE_RESOURCE_DAS_VM.VPX_COMPUTE_RESOURCE_DAS_VM_F1;VPX_COMPUTE_RESOURCE_DRS_VM.VPX_COMPUTE_RESOURCE_DRS_VM_F1;VPX_COMPUTE_RESOURCE_ORC_VM.VPX_COMPUTE_RESOURCE_ORC_VM_F1;VPX_EVENT_18.VPXI_EVENT_CHAIN_ID_18;VPX_COMPUTE_RESOURCE_ORC_VM.VPX_COMPUTE_RESOURCE_ORC_VM_F2;VPX_DAS_HB_DATASTORE_SYS.VPX_DAS_HB_DATASTORE_SYS_F1;VPX_DAS_HB_DATASTORE_SYS.VPX_DAS_HB_DATASTORE_SYS_F2;VPX_DATASTORE.VPXI_DATASTORE_DATACENTER;VPX_DEVICE.VPX_DEVICE_U1;VPX_DS_ASSIGNMENT.VPX_DS_ASSIGNMENT_M1;VPX_DS_ASSIGNMENT.VPXI_DS_ASSIGNMENT_ENTITY;VPX_DVHOST.VPX_DVHOST_F1;VPX_
    YYYY-MM-DDThh:mm:ss ERROR vcdb.const Error while validating source vCenter Server database: Error while executing the query
    .
    .
    .
    YYYY-MM-DDThh:mm:ss INFO extensions The component script returned '{'coreRequirement': {'requiredSrcDiskSpace': 0.1, 'requiredDstDiskSpace': {'/storage/db': 0.8}, 'exportEstimationTime': 1, 'importEstimationTime': 2}, 'dstPortSpecs': [], 'srcPorts': [], 'userOptionSpecs': [{'optionId': 'vcdb.migrateSet', 'answerSpecs': [{'answerId': 'all', 'optionRequirement': {'requiredSrcDiskSpace': 0.2, 'requiredDstDiskSpace': {'/storage/seat': 1.6}, 'exportEstimationTime': 7, 'importEstimationTime': 12}, 'requirementMismatchSpecs': []}, {'answerId': 'core_events_tasks', 'optionRequirement': {'requiredSrcDiskSpace': 0.2, 'requiredDstDiskSpace': {'/storage/seat': 1.0}, 'exportEstimationTime': 5, 'importEstimationTime': 9}, 'requirementMismatchSpecs': []}, {'answerId': 'core', 'optionRequirement': {'requiredSrcDiskSpace': 0.0, 'requiredDstDiskSpace': {}, 'exportEstimationTime': 0, 'importEstimationTime': 0}, 'requirementMismatchSpecs': []}]}], 'installArguments': {'db.type': 'embedded'}, 'extraArguments': {'src.db.type': 'embedded'}, 'requirementMismatchSpecs': [{'text': Source vCenter Server schema validation found an issue., 'description': None, 'resolution': Read Knowledge Base Article 2149901 and address the issues found., 'problemId': None, 'severity': 'ERROR'}]}'

  • Log file /var/log/vmware/upgrade/vcdb_req.err will show similar entries to:

    1 [P0001](1) ERROR: ERROR ! Missing indexes: VPX_EVENT_18.VPXI_CHANGE_TAG_18;VPX_EVENT_18.VPXI_EVENT_CATEGORY_18;VPX_ALARM.VPX_ALARM_F1;VPX_ALARM_RUNTIME.IX_VPX_ALRT_CRTIME_STATUSVALUE;VPX_CHANGE_TAG.VPX_CHANGE_TAG_M1;VPX_COMPLIANCE_STATUS.VPX_COMPL_STATUS_ENTITY_ID_F1;VPX_COMPLIANCE_STATUS.VPX_COMPL_STATUS_PROFID_F1;VPX_COMPUTE_RES_FAILOVER_HOST.VPX_COMP_RES_FAILOVER_HOST_F1;VPX_COMPUTE_RES_USER_HB_DS.VPX_COMPUTE_RES_USER_HB_DS_F1;VPX_COMPUTE_RESOURCE.VPX_COMPUTE_RESOURCE_F1;VPX_COMPUTE_RESOURCE_DAS_VM.VPX_COMPUTE_RESOURCE_DAS_VM_F1;VPX_COMPUTE_RESOURCE_DRS_VM.VPX_COMPUTE_RESOURCE_DRS_VM_F1;VPX_COMPUTE_RESOURCE_ORC_VM.VPX_COMPUTE_RESOURCE_ORC_VM_F1;VPX_EVENT_18.VPXI_EVENT_CHAIN_ID_18;VPX_COMPUTE_RESOURCE_ORC_VM.VPX_COMPUTE_RESOURCE_ORC_VM_F2;VPX_DAS_HB_DATASTORE_SYS.VPX_DAS_HB_DATASTORE_SYS_F1;VPX_DAS_HB_DATASTORE_SYS.VPX_DAS_HB_DATASTORE_SYS_F2;VPX_DATASTORE.VPXI_DATASTORE_DATACENTER;VPX_DEVICE.VPX_DEVICE_U1;VPX_DS_ASSIGNMENT.VPX_DS_ASSIGNMENT_M1;VPX_DS_ASSIGNMENT.VPXI_DS_ASSIGNMENT_ENTITY;VPX_DVHOST.VPX_DVHOST_F1;VPX_
    2 [P0001](1) DVHOST_HC_MTU_RESULT.VPX_DVHOST_HC_MTU_RESULT_M1;VPX_DVHOST_HC_RESULT.VPX_DVHOST_HC_RESULT_M1;VPX_DVHOST_HC_VLAN_RESULT.VPX_DVHOST_HC_VLAN_RESULT_M1;VPX_DVPORT.VPX_DVPORT_M1;VPX_DVPORT.VPX_DVPORT_M2;VPX_DVPORT.VPX_DVPORT_M3;VPX_DVPORT_MEMBERSHIP.VPX_DVPORT_MEMBERSHIP_F1;VPX_DVPORT_MEMBERSHIP.VPX_DVPORT_MEMBERSHIP_F2;VPX_DVPORT_SETTING.VPX_DVPORT_SETTING_M1;VPX_DVPORT_SETTING.VPX_DVPORT_SETTING_M2;VPX_DVPORT_SETTING.VPX_DVPORT_SETTING_U1;VPX_DVPORT_VLAN.VPX_DVPORT_VLAN_M1;VPX_DVPORTGROUP.VPX_DVPORTGROUP_F1;VPX_DVS.VPX_DVS_F1;VPX_DVS.VPX_DVS_F2;VPX_DVS.VPX_DVS_F3;VPX_DVS_BLOB.VPX_DVS_BLOB_F1;VPX_DVS_BLOB.VPX_DVS_BLOB_M1;VPX_DVS_LAG.VPX_DVS_LAG_U1;VPX_DVS_PVLAN.VPX_DVS_PVLAN_F1;VPX_DVS_RULE.IDX_VPX_DVS_RULE;VPX_DVS_RULE_QUALIFIER.IDX_VPX_DVS_RULE_QUALIFIER;VPX_DVS_SCOPE.VPX_DVS_SCOPE_M1;VPX_DVS_VSPAN_SESSION.VPX_DVS_VSPAN_SESSION_U1;VPX_ENTITY.VPX_ENTITY_F1;VPX_ENTITY.VPXI_ENTITY_TYPE_ID;VPX_ENTITY_LAST_EVENT.VPX_ENTITY_LAST_EVENT_F1;VPX_EVENT_1.VPX_EVENT_F1_1;VPX_EVENT_1.VPXI_CHANGE_TAG_1;VPX_EVENT_1.VPXI_EVEN
    3 [P0001](1) T_CATEGORY_1;VPX_EVENT_1.VPXI_EVENT_CHAIN_ID_1;VPX_EVENT_1.VPXI_EVENT_COMPUTERES_ID_1;VPX_EVENT_1.VPXI_EVENT_CREATE_TIME_1;VPX_EVENT_1.VPXI_EVENT_DATACENTER_ID_1;VPX_EVENT_1.VPXI_EVENT_DATASTORE_ID_1;VPX_EVENT_1.VPXI_EVENT_DVS_ID_1;VPX_EVENT_1.VPXI_EVENT_EVENT_TYPE_1;VPX_EVENT_1.VPXI_EVENT_EXTENDED_CLASS_1;VPX_EVENT_1.VPXI_EVENT_HOST_ID_1;VPX_EVENT_1.VPXI_EVENT_NETWORK_ID_1;VPX_EVENT_1.VPXI_EVENT_VM_ID_1;VPX_EVENT_10.VPX_EVENT_F1_10;VPX_EVENT_10.VPXI_CHANGE_TAG_10;VPX_EVENT_10.VPXI_EVENT_CATEGORY_10;VPX_EVENT_10.VPXI_EVENT_CHAIN_ID_10;VPX_EVENT_10.VPXI_EVENT_COMPUTERES_ID_10;VPX_EVENT_10.VPXI_EVENT_CREATE_TIME_10;VPX_EVENT_10.VPXI_EVENT_DATACENTER_ID_10;VPX_EVENT_10.VPXI_EVENT_DATASTORE_ID_10;VPX_EVENT_10.VPXI_EVENT_DVS_ID_10;VPX_EVENT_10.VPXI_EVENT_EVENT_TYPE_10;VPX_EVENT_10.VPXI_EVENT_EXTENDED_CLASS_10;VPX_EVENT_10.VPXI_EVENT_HOST_ID_10;VPX_EVENT_10.VPXI_EVENT_NETWORK_ID_10;VPX_EVENT_10.VPXI_EVENT_USERNAME_10;VPX_EVENT_10.VPXI_EVENT_VM_ID_10;VPX_EVENT_11.VPX_EVENT_F1_11;VPX_EVENT_11.VPXI_CHANGE_TAG_11;VPX_
    4 [P0001](1) EVENT_11.VPXI_EVENT_CATEGORY_11;VPX_EVENT_11.VPXI_EVENT_CHAIN_ID_11;VPX_EVENT_11.VPXI_EVENT_COMPUTERES_ID_11;VPX_EVENT_11.VPXI_EVENT_CREATE_TIME_11;VPX_EVENT_11.VPXI_EVENT_DATACENTER_ID_11;VPX_EVENT_11.VPXI_EVENT_DATASTORE_ID_11;VPX_EVENT_11.VPXI_EVENT_DVS_ID_11;VPX_EVENT_11.VPXI_EVENT_EVENT_TYPE_11;VPX_EVENT_11.VPXI_EVENT_EXTENDED_CLASS_11;VPX_EVENT_11.VPXI_EVENT_HOST_ID_11;VPX_EVENT_11.VPXI_EVENT_NETWORK_ID_11;VPX_EVENT_11.VPXI_EVENT_USERNAME_11;VPX_EVENT_11.VPXI_EVENT_VM_ID_11;VPX_EVENT_12.VPX_EVENT_F1_12;VPX_EVENT_12.VPXI_CHANGE_TAG_12;VPX_EVENT_12.VPXI_EVENT_CATEGORY_12;VPX_EVENT_12.VPXI_EVENT_CHAIN_ID_12;VPX_EVENT_12.VPXI_EVENT_COMPUTERES_ID_12;VPX_EVENT_12.VPXI_EVENT_CREATE_TIME_12;VPX_EVENT_18.VPX_EVENT_F1_18;;
    Error while executing the query

Environment

vCenter Server 7.X

vCenter Server 8.X

Cause

This issue occurs due to missing indexes in the vCenter Server database.

Resolution

If you encounter the symptoms outlined above, please contact Broadcom Technical Support for further assistance, as the resolution involves re-creating missing indexes on the vCenter Server database, which should be performed with caution.

Additional Information

The old legacy KB ID of 2149901 is showing as a coded error when the customers update from version 7 to version 8 fails and the "newer" ID is archived as it references MS SQL DB edits. This KB should be used for the VCenter Appliances and Postgres.

Use the following article if the entries also include a "Missing constraints" error in the above mentioned logs :
Upgrade Pre-Checks on the vCenter Server fails with error "Source vCenter Server schema validation found an issue"

Powered by Wolken Software