Knowledge Base

Note: This is a two-part solution. Read and understand all of the steps before proceeding. After the jobs are created and enabled properly, they may take a significant amount of time to run. This article does not apply to installations using Microsoft SQL Server 2005 Express. SQL Server Agent is not available in Microsoft SQL Server 2005 Express. Historic data is managed by the VirtualCenter Server service in this case. In addition, the DSN account has to have permissions to run the rollup jobs. If the account does not have permissions, the performance data is not collected. This can be seen in the logs for the rollup jobs.

Verifying the existence of jobs and removing them

For the scripts to install correctly, you must remove any existing Past _____ stats rollup jobs. This section verifies the existence of jobs and removes them if present.

To verify the existence of jobs and remove them:

1. Open SQL Management Studio using a Sysadmin account (typically SA or Administrator).
2. Expand the Server and SQL Server Agent.
   
   Note: Ensure the SQL Server Agent is running. If it is not running, right-click the SQL Server Agent and select Start. Determine if the issue is still occurring.
   
   
3. Click the Jobs folder. You see a list of all jobs available on your server.
   
   These jobs are related to VirtualCenter 2.5 and vCenter Server 4.x:
   
   
   • Past Day Stats Rollup
   • Past Week Stats Rollup
   • Past Month Stats Rollup
     
     
4. Right-click any of those jobs, if they exist, and select Delete.
5. Click OK to confirm the deletion.
6. Close SQL Management Studio when those jobs are removed.

Adding the SQL Server Agent Jobs

To add a SQL Server Agent Job:

1. Open SQL Management Studio using the database login used by VirtualCenter to connect to the database (typically not SA or Administrator). See Administrative credentials are required for Oracle and SQL Server databases when installing or upgrading vCenter Server (1003052) to ensure that you have the correct permissions.
   
   
2. Click File > Open > File.
3. Navigate to the location of the jobs:
   
   Notes:
   
   
   • The drive letters may change depending on where you install VirtualCenter:
     
     
     • VirtualCenter 2.5: C:\Program Files\VMware\Infrastructure\VirtualCenter Server\dbupgrade\Upgrade-v3-to-v4\T-SQL\
     • VirtualCenter 2.5, Update 4: C:\Program Files\VMware\Infrastructure\VirtualCenter Server\dbupgrade\Upgrade-v4-to-v5\T-SQL\
     • vCenter Server 4.x: C:\Program Files\VMware\Infrastructure\VirtualCenter Server\


   • You may need to copy the job creation sql files from the vCenter Server to the server on which the Management Studio/SQL Plus is being run.
     
     
4. Open job_schedule1_mssql.sql.
5. Ensure that the VirtualCenter Database (for example, VCDB) is selected and that Master is not selected.
6. Right-click the VirtualCenter Database and select New Query.
7. Copy the query outlined in job_schedule1_mssql.sql to the New Query pane in SQL Management studio, then click Execute Query.
8. Repeat steps 1 to 7 for job_schedule2_mssql.sql and job_schedule3_mssql.sql.
9. After all three jobs are created, navigate to SQL Server Agent > Jobs in the Object Explorer.
10. Right-click Past Day stats rollup, then click Properties. Ensure that the owner of the job is the same user as the owner of the database.
11. Right-click Past Month stats rollup, then click Properties. Ensure that the owner of the job is the same user as the owner of the database.
12. Right-click Past Week stats rollup, then click Properties. Ensure that the owner of the job is the same user as the owner of the database.

Oracle

To ensure that the scripts are upgraded properly:

1. Open SQL Plus.
2. Click File > Open > File.
3. Navigate to the location of the jobs, then copy the contents of job_schedule1_oracle.sql:
   
   
   • VirtualCenter 2.5: C:\Program Files\VMware\Infrastructure\VirtualCenter Server\dbupgrade\Upgrade-v3-to-v4\PL-SQL\
   • vCenter Server 4.x: C:\Program Files\VMware\Infrastructure\VirtualCenter Server\


4. Open an sqlplus session with a user account that has access to the Oracle tables, jobs, and schedules related to the vCenter Server.
5. Execute the job_schedule1_oracle.sql script.
   
   Note: Contact your Oracle database administrator or see Oracle support documentation for information on how to execute Oracle scripts.
   
   
6. Repeat steps 1-5 for job_schedule2_oracle.sql and job_schedule3_oracle.sql.
7. After all three jobs are created, ensure that the global Oracle setting JOB_QUEUE_PROCESSES is not set to 0 as this disables all job processing.

Additional Information

If you encounter issues after upgrading to vCenter Server 4.0, see Past Week stats rollupvc40 SQL Server job fails to complete after upgrading to vCenter (1014209).

See Also:

• Verifying vCenter Server 2.5 jobs and stored procedures (1033588)
• Verifying vCenter Server 4.0 jobs and stored procedures (1033587)
• Verifying vCenter Server 4.1 jobs and stored procedures (1029824)
• Reducing the size of the vCenter Server database when the rollup scripts take a long time to run (1007453)
• 『Performance data is currently not available for this entity』のエラーが表示された、ロールアップ ジョブをアップデートする (2001955)