Error "SQLError was thrown: "ODBC error: (42P01) - ERROR: relation "vpxv_event_all" does not exist" observed when vpxd service failure.
search cancel

Error "SQLError was thrown: "ODBC error: (42P01) - ERROR: relation "vpxv_event_all" does not exist" observed when vpxd service failure.

book

Article ID: 437137

calendar_today

Updated On:

Products

VMware vCenter Server VMware Cloud Foundation VMware Telco Cloud Platform

Issue/Introduction

  • The vCenter Server Appliance (VCSA) is inaccessible via the vSphere Client.
  • The vmware-vpxd service fails to start and shuts down immediately upon initialization.
  • The /var/log/vmware/vpxd/vpxd.log records the following critical database exceptions:

2026-04-15T15:22:42.661+10:00 error vpxd[303205] [Originator@6876 sub=Default] [VdbStatement] SQL execution failed:  SELECT EVENT_ID, CHAIN_ID, EVENT_TYPE, EXTENDED_CLASS, CREATE_TIME, USERNAME, CATEGORY, VM_ID,        VM_NAME, HOST_ID, HOST_NAME, COMPUTERESOURCE_ID, COMPUTERESOURCE_TYPE,        COMPUTERESOURCE_NAME, DATACENTER_ID, DATACENTER_NAME, DATASTORE_ID, DATASTORE_NAME, NETWORK_ID,        NETWORK_NAME, NETWORK_TYPE, DVS_ID, DVS_NAME, STORAGEPOD_ID, STORAGEPOD_NAME, CHANGE_TAG_ID FROM VPXV_EVENT_ALL  WHERE (EVENT_ID IN (?)) LIMIT 1;
2026-04-15T15:22:42.661+10:00 error vpxd[303205] [Originator@6876 sub=Default] [VdbStatement] Execution elapsed time: 2 ms
2026-04-15T15:22:42.661+10:00 error vpxd[303205] [Originator@6876 sub=Default] [VdbStatement] Statement diagnostic data from driver is 42P01:0:1:ERROR: relation "vpxv_event_all" does not exist;
--> Error while executing the query

2026-04-15T15:22:42.661+10:00 error vpxd[303205] [Originator@6876 sub=Default] [Vdb::IsRecoverableErrorCode] Unable to recover from 42P01:1
2026-04-15T15:22:42.661+10:00 error vpxd[303205] [Originator@6876 sub=Default] [VdbStatement] SQLError was thrown: "ODBC error: (42P01) - ERROR: relation "vpxv_event_all" does not exist;
--> Error while executing the query" is returned when executing SQL statement " SELECT EVENT_ID, CHAIN_ID, EVENT_TYPE, EXTENDED_CLASS, CREATE_TIME, USERNAME, CATEGORY, VM_ID,        VM_NAME, HOST_ID, HOST_NAME, COMPUTERESOURCE_ID, COMPUTERESOURCE_TYPE,        COMPUTERESOURCE_NAME, DATACENTER_ID, DATACENTER_NAME, DATASTORE_ID, DATASTORE_NAME, NETWORK_ID,        NETWORK_NAME, NETWORK_TYPE, DVS_ID, DVS_NAME, STORAGEPOD_ID, STORAGEPOD_NAME, CHANGE_TAG_ID FROM VPXV_EVENT_ALL  WHERE (EVENT_ID IN (?)) LIMIT 1; "
2026-04-15T15:22:42.662+10:00 error vpxd[303205] [Originator@6876 sub=MoEvent] [EventManagerMo] Failed to load events: "ODBC error: (42P01) - ERROR: relation "vpxv_event_all" does not exist;
--> Error while executing the query" is returned when executing SQL statement " SELECT EVENT_ID, CHAIN_ID, EVENT_TYPE, EXTENDED_CLASS, CREATE_TIME, USERNAME, CATEGORY, VM_ID,        VM_NAME, HOST_ID, HOST_NAME, COMPUTERESOURCE_ID, COMPUTERESOURCE_TYPE,        COMPUTERESOURCE_NAME, DATACENTER_ID, DATACENTER_NAME, DATASTORE_ID, DATASTORE_NAME, NETWORK_ID,        NETWORK_NAME, NETWORK_TYPE, DVS_ID, DVS_NAME, STORAGEPOD_ID, STORAGEPOD_NAME, CHANGE_TAG_ID FROM VPXV_EVENT_ALL  WHERE (EVENT_ID IN (?)) LIMIT 1; "
2026-04-15T15:22:42.662+10:00 error vpxd[303205] [Originator@6876 sub=ConfigIssue] Processing of persisted config issues failed: N3Vim5Fault13DatabaseError9ExceptionE(Fault cause: vim.fault.DatabaseError
--> )

2026-04-15T15:22:42.664+10:00 warning vpxd[303205] [Originator@6876 sub=VpxProfiler] ServerApp::Init [TotalTime] took 2533 ms
2026-04-15T15:22:42.664+10:00 error vpxd[303205] [Originator@6876 sub=Default] Failed to intialize VMware VirtualCenter. Shutting down
2026-04-15T15:22:42.664+10:00 info vpxd[303205] [Originator@6876 sub=SupportMgr] Wrote uptime information
2026-04-15T15:22:42.664+10:00 info vpxd[303205] [Originator@6876 sub=Default] Forcing shutdown of VMware VirtualCenter now

Environment

VCF 9.x
vCenter Server 8.x
TCP 5.x

Cause

The VPXV_EVENT_ALL view in the vCenter Database (VCDB) is lost and this could be due to 

  1. Failed or Interrupted Upgrade during vCenter Server Database schema migration state. 
  2. Manual schema modifications or a restore from an inconsistent backup will lead to database corruption. 
  3. Abrupt power off of vCenter Server or any maintenance operation carried out when the /storage/seat partition 100% full. 

Resolution

Option 1

Recreate the missing "vpxv_event_all" table from the SQL definitions available in the vCenter Server installation directory. 

  1. Power off the vCenter Server and take an offline snapshot.

  2. Power on the vCenter Server and SSH to the vCenter Server.

  3. Connect to the database and confirm that the "vpxv_event_all" is absent. 

    /opt/vmware/vpostgres/current/bin/psql -d VCDB -U postgres -c "\dv VPXV_EVENT_ALL"

  4. Recreate the Schema Views as per the vCenter Server version from the install directory:

    • For vCenter Server 8.x :

      /opt/vmware/vpostgres/current/bin/psql -d VCDB -U postgres -f /usr/lib/vmware-vpx/py/vpxd_db_views.sql 
    • For vCenter 7.x :

      /opt/vmware/vpostgres/current/bin/psql -d VCDB -U postgres -f /usr/lib/vmware-vpx/sql/VCDB_views_PostgresSQL.sql

  5. If the script executes successfully, restart the vCenter services:

    service-control --stop --all && service-control --start --all

Option 2: 

Database Restoration via File-Based Backup (Last Resort):  Restore vCenter Server from a File-Based Backup

  1. Power off the corrupted vCenter Server Appliance to isolate it from the network.

  2.  

    Download the full VCSA ISO installer (e.g., VMware-VCSA-all-8.0.x.iso) corresponding to your exact build from the Broadcom Support Portal.

  3.  

    Mount the ISO to an administrative workstation and execute the vcsa-ui-installer.

  4.  

    Select the Restore operation from the installer interface.

  5.  

    Input the backup repository details in Stage 1 to deploy a new virtual appliance.