Portal Home > Knowledgebase > VMware Knowledge Base > Checking the status of vCenter Server performance rollup jobs

Checking the status of vCenter Server performance rollup jobs

Purpose

This article provides steps to check the status of the vCenter Server performance rollup jobs.
 
You may want to check the status of the vCenter Server performance rollup jobs if:
  • After certain tasks, such as maintenance or upgrades, you want to verify that the vCenter Server performance rollup jobs are working.
  • You see a warning/alert for the vCenter Server database in the vCenter Service Status screen indicating that the jobs are not running.

Resolution

In MS SQL Server

In MS SQL server 2005/2008/2008 R2 Full Edition, the jobs reside in the SQL Server Agent.
 
To check the status:

Note: Ensure that the SQL Agent service is running. If the SQL Agent service is not running, the performance rollup jobs are not executed.

  1. Launch SQL Management Studio.
  2. Connect to the SQL instance where the vCenter Server database resides.
  3. Expand SQL Server Agent within which the jobs resides.
  4. Locate the Past Day Stats rollup job.
  5. Right-click the job and click View History. The status of the job and other details regarding the schedule are displayed.
  6. Repeat the steps for past week rollup and past month rollup.

In MS SQL server 2005/2008/2008 R2 Express Edition, there is no SQL Agent to run the jobs. Instead, the VMware VirtualCenter Server service calls the stored procedures for performing the rollup directly. When the vpxd is running, the calls to run the stored procedures are automatically executed.

In Oracle 10g and 11g

If you have a query tool such as SQL, connect to the  Oracle database and execute this SQL statement to check next lastdate and nextdate of job:

SELECT job, to_char(last_date, 'mm/dd/yyyy hh:mi pm') lastdate,to_char(next_date, 'mm/dd/yyyy hh:mi pm') nextdate, failures, broken, what
FROM user_jobs
ORDER BY next_date;

You see an output similar to:

          JOB LASTDATE            NEXTDATE              FAILURES  B    WHAT

        2  11/12/2011     05:49 AM 11/12/2011 07:49 AM    0     N   begin stats_rollup1_proc; Purge_Stat1_proc; end;

        3  11/12/2011     05:49 AM 11/12/2011 07:49 AM    0     N   begin stats_rollup2_proc; Purge_Stat2_proc; end;

        4  11/11/2011     10:04 AM 11/12/2011 10:04 AM    0     N   begin stats_rollup3_proc; Purge_Stat3_proc; end;


The output shows the last time the job ran and if the job is broken. Oracle sets the next run date to a date far in the future after multiple failures. The column B in the output refers to broken jobs. In this example, N (No) broken jobs was returned.

For DB2 v9.5 and v9.7

To verify if the performance rollup jobs exist in the vCenter Server database running on DB2:

  1. Connect to the machine hosting the DB2 database.
  2. Launch the DB2 Control Center.
  3. Connect to the vCenter Server database as a database user.
  4. Launch a DB2 command editor from the Control Center and run this SQL statement:

    SELECT * from SYSTOOLS.ADMIN_TASK_LIST

  5. Verify and ensure that you can see these three STATS rollup jobs:

    * STATS_ROLLUP_JOB1_VCX
    * STATS_ROLLUP_JOB2_VCX
    * STATS_ROLLUP_JOB2_VCX


    Note: These are the performance rollup jobs. You may also see additional jobs.

  6. To check the status of the jobs, run this SQL statement:
 SELECT name, begin_time, end_time, status FROM systools.admin_task_status ORDER BY begin_time DESC;

You see an output similar to:

NAME                   BEGIN_TIME                  END_TIME                   STATUS
STATS_ROLLUP_JOB1_VCX  2011-10-05-01.55.00.843000  2011-10-05-01.57.40.296000 COMPLETE
STATS_ROLLUP_JOB2_VCX  2011-10-05-01.55.00.855000  2011-10-05-01.56.37.407000 COMPLETE
STATS_ROLLUP_JOB3_VCX  2011-10-05-01.55.00.859000  2011-10-05-01.55.37.406000 COMPLETE

In this sample output, the jobs were successfully marked as COMPLETE. If any issues were encountered the status appears as FAILED.  


Based on VMware KB 2012226

Also Read

Language: