Verifying jobs and stored procedures installed in vCenter Server 5.1, 5.5 and 6.x
search cancel

Verifying jobs and stored procedures installed in vCenter Server 5.1, 5.5 and 6.x

book

Article ID: 308757

calendar_today

Updated On:

Products

VMware vCenter Server

Issue/Introduction

This article provides a complete list of jobs and stored procedures in vCenter Server 5.1, 5.5 and 6.x.

vCenter Server offloads many data maintenance tasks to the database by installing stored procedures and jobs to invoke the stored procedures. For example, vCenter Server includes procedures to move data between tables or delete old data.

Notes:


Environment

VMware vCenter Server 6.x
VMware vCenter Server 5.0.x
VMware vCenter Server 5.5.x

Resolution

Verifying the jobs installed in vCenter Server 5.1, 5.5 and 6.x

To check the jobs installed in vCenter Server 5.1, 5.5 and 6.x using MS SQL:

  1. Launch SQL Server Management Studio.
  2. Navigate to SQL Server Agent.

    Note: SQL Express does not have a SQL Server Agent so it does not have the jobs listed. Only the full edition of SQL Server has the agent and jobs.
     
  3. Ensure that the jobs listed in this table are installed:

    Note: For managing an Oracle vCenter Server database, you can use Oracle SQL Developer and for managing a DB2 vCenter Server database, you can use DB2 Control Center.
     
    Rollup JobCorresponding File
    Event Task Cleanup myDBjob_cleanup_events_DB.sql
    Past Day stats rollup myDBjob_schedule1_DB.sql
    Past Month stats rollup myDBjob_schedule3_DB.sql
    Past Week stats rollup myDBjob_schedule2_DB.sql
    Process Performance Data myDBjob_dbm_performance_data_DB.sql
    Property Bulletin Daily Update myDB

    Note: This job only applies to vCenter Server 5.x    		job_property_bulletin_DB.sql
    Topn past day myDBjob_topn_past_day_DB.sql
    Topn past month myDBjob_topn_past_month_DB.sql
    Topn past week myDBjob_topn_past_week_DB.sql
    Topn past year myDBjob_topn_past_year_DB.sql

    where DB is db2, mssql, or oracle.

    Note: Ensure that myDB references the vCenter Server database and not the primary or some other database. If these jobs reference any other database, you must delete and recreate the jobs.

Verifying the stored procedures installed in vCenter Server 5.1, 5.5 and 6.x

To check the stored procedures installed in vCenter Server 5.1, 5.5 and 6.x using MS SQL:

  1. Navigate to vCenter DB > Programmability > Stored Procedures.
  2. Ensure that the stored procedures listed in this table are installed:
     
    Stored ProcedureCorresponding File
    calc_topn1_proc
    calc_topn1_proc_DB.sql
    calc_topn2_proc
    calc_topn2_proc_DB.sql
    calc_topn3_proc
    calc_topn3_proc_DB.sql
    calc_topn4_proc
    calc_topn4_proc_DB.sql
    cleanup_events_tasks_proc
    cleanup_events_DB.sql
    clear_topn1_proc
    clear_topn1_proc_DB.sql
    clear_topn2_proc
    clear_topn2_proc_DB.sql
    clear_topn3_proc
    clear_topn3_proc_DB.sql
    clear_topn4_proc
    clear_topn4_proc_DB.sql
    delete_stats_proc
    delete_stats_proc_DB.sql
    insert_stats_proc
    insert_stats_proc_DB.sql
    l_purge_stat2_proc
    l_purge_stat2_proc_DB.sql
    l_purge_stat3_proc
    l_purge_stat3_proc_DB.sql
    l_stats_rollup1_proc
    l_stats_rollup1_proc_DB.sql
    l_stats_rollup2_proc
    l_stats_rollup2_proc_DB.sql
    l_stats_rollup3_proc
    l_stats_rollup3_proc_DB.sql
    load_stats_proc
    load_stats_proc_DB.sql
    load_usage_stats_proc
    load_usage_stats_proc_DB.sql
    process_license_snapshot_proc
    process_license_snapshot_DB.sql
    process_performance_data_proc
    process_performance_data_DB.sql
    purge_stat2_proc
    purge_stat2_proc_DB.sql
    purge_stat3_proc
    purge_stat3_proc_DB.sql
    purge_usage_stat_proc
    purge_usage_stats_proc_DB.sql
    rule_topn1_proc
    rule_topn1_proc_DB.sql
    rule_topn2_proc
    rule_topn2_proc_DB.sql
    rule_topn3_proc
    rule_topn3_proc_DB.sql
    rule_topn4_proc
    rule_topn4_proc_DB.sql
    stats_rollup1_proc
    stats_rollup1_proc_DB.sql
    stats_rollup2_proc
    stats_rollup2_proc_DB.sql
    stats_rollup3_proc
    stats_rollup3_proc_DB.sql
    upsert_last_event_proc
    upsert_last_event_proc_DB.sql
where DB is db2, mssql, or oracle.
If any of these jobs or stored procedures are missing, you must install them by running the corresponding .sql file on the vCenter Server database using a database management tool such as SQL Management Studio. For more information on running these .sql files, see section Adding the SQL Server Agent Jobs in Updating rollup jobs after the error: Performance data is currently not available for this entity (1004382).

Notes:
  • The upsert_last_event_proc procedure is not required for the Oracle database.
  • If there is a custom schema, the following command also needs to be ran:

    alter schema schema_name transfer dbo.stored_procedure_name

All SQL scripts are located in the vCenter Server installation folder:
  • vCenter Server 5.1 and 5.5: C:\Program Files\VMware\Infrastructure\VirtualCenter Server\sql.
  • vCenter Server 6.x: C:\Program Files\VMware\vCenter Server\vpxd\sql
For more information on commonly used vCenter Server installation paths, see Common vCenter Server and vSphere Client Windows paths (1028185).

Ensure that the vCenter Server database is the target before executing the SQL file.


Additional Information

"Performance data is currently not available for this entity" error after updating rollup in vSphere
Verifying jobs and stored procedures in VMware vCenter Server 4.1.x
Verifying vCenter Server 4.0 jobs and stored procedures
Verifying vCenter Server 2.5 jobs and stored procedures
Verifying jobs and stored procedures installed in VMware vCenter Server 5.0
Verifying jobs and stored procedures installed in vCenter Server 5.1, 5.5 and 6.x
vCenter Server 5.1 および 5.5 にインストールされたジョブとストアド プロシージャを確認する
验证 vCenter Server 5.1、5.5 和 6.x 中安装的作业和存储过程

Powered by Wolken Software