Knowledge Base

The VMware Knowledge Base provides support solutions, error messages and troubleshooting guides
 
Search the VMware Knowledge Base (KB)   View by Article ID
 

Performance data is not showing properly after deploying vCenter Server Appliance 5.0 U1b with vPostgres embedded database (2039649)

Details

  • Performance stats data does not get saved into the database correctly and the user will not have access to the historical performance data.
  • The historical task/events do not get removed per the configured specification.
Note: This is due to UTC timestamp should be used when performing calculation in all the functions within the database. The data type used in the timestamp of the performance data tables in the database needs to be modified. This issue occurs when VCVA is deployed with vPostgres embedded database starting from VCVA 5.0 U1a release.
  • Historical performance data graphs of ESXi host under both the Performance > Advanced view and the Performance > Overview tab in the vSphere client are not showing properly.

Solution

To resolve this issue:
  1. Log in to the vCenter Server Appliance (vCVA) virtual machine.
  2. Download the revised SQL files in the package (revisedvPostgresScripts.zip) to /tmp on the vCVA.

    Note: You can download SQL files from the revisedvPostgresScripts.zip file attached to this article.

    The set of SQL files (revisedvPostgresScripts.zip) include:

    vpxv_hist_stat.sql
    stats_rollup1_proc_PostgreSQL.sql  
    stats_rollup2_proc_PostgreSQL.sql    
    stats_rollup3_proc_PostgreSQL.sql  
    purge_stat1_proc_PostgreSQL.sql  
    purge_stat2_proc_PostgreSQL.sql 
    purge_stat3_proc_PostgreSQL.sql 
    purge_usage_stats_proc_PostgreSQL.sql

  3. Change directory to /opt/vmware/vpostgres/1.0/bin.
  4. Check the vc user password:     

    cat /etc/vmware-vpx/embedded_db.cfg | grep PASSWORD    

    You should see an output similar to:

    EMB_DB_PASSWORD='4XQnS5mSRlsQmzyQ'

  5. Log in to the psql VCDB:

    ./psql -d VCDB -U vc    

    When prompted, enter the vc password.

  6. Run these SQL commands:

    drop view VPXV_HIST_STAT_DAILY;   
    drop view VPXV_HIST_STAT_WEEKLY;   
    drop view VPXV_HIST_STAT_MONTHLY;
    drop view VPXV_HIST_STAT_YEARLY;
    alter table vpx_sample_time1
    alter column sample_time type timestamp;
    alter table vpx_sample_time2 
    alter column sample_time type timestamp;
    alter table vpx_sample_time3
    alter column sample_time type timestamp;
    alter table vpx_sample_time4
    alter column sample_time type timestamp;


    Note: The drop view command does not destroy or delete any vCenter Server data. A view is read-only stored query.

  7. Run these SQL commands:

    ./psql -d VCDB -U vc -f /tmp/vpxv_hist_stat.sql
    ./psql -d VCDB -U vc -f /tmp/purge_stat1_proc_PostgreSQL.sql
    ./psql -d VCDB -U vc -f /tmp/purge_stat2_proc_PostgreSQL.sql
    ./psql -d VCDB -U vc -f /tmp/purge_stat3_proc_PostgreSQL.sql
    ./psql -d VCDB -U vc -f /tmp/purge_usage_stats_proc_PostgreSQL.sql
    ./psql -d VCDB -U vc -f /tmp/stats_rollup1_proc_PostgreSQL.sql
    ./psql -d VCDB -U vc -f /tmp/stats_rollup2_proc_PostgreSQL.sql
    ./psql -d VCDB -U vc -f /tmp/stats_rollup3_proc_PostgreSQL.sql  
      

    When prompted, enter the vc password.

  8. Restart vpxd using this command:

    #  /etc/init.d/vmware-vpxd restart

  9. Log in to the vCenter Server Appliance server using the vSphere Client.  

Attachments

Request a Product Feature

To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature page.

Feedback

  • 0 Ratings

Did this article help you?
This article resolved my issue.
This article did not resolve my issue.
This article helped but additional information was required to resolve my issue.
What can we do to improve this information? (4000 or fewer characters)
  • 0 Ratings
Actions
KB: