Creating default alarms when upgrading to vCenter Server 4.0

Kunnskapsbase

This article describes how to create default database alarms for vCenter Server 4.0, following an upgrade.

Note: This is an issue with upgrading to vCenter Server 4.0 only. Fresh installations of vCenter Server 4.0 are not affected.

Warning: Running the scripts attached to this article on a fresh vCenter Server 4.0 installation can cause vCenter Server to fail.

This issue is resolved in vCenter 4.0 Server Update 1. For more information, see VMware vCenter Server 4.0 Update 1 Release Notes .

Note: Before performing any of the troubleshooting steps below, create backups of the vCenter Server database.

To create missing default alarms:

Download the files 1010399_create_alarms_mssql.txt and 1010399_create_alarms_oracle.txt attached to this article.
Save 1010399_create_alarms_mssql.txt as create_alarms_mssql.sql.
Save 1010399_create_alarms_oracle.txt as create_alarms_oracle.sql.
Copy the appropriate SQL query file to the C:\Program Files\VMware\Infrastructure\VirtualCenter Serverdirectory on your vCenter server:

Note: The vCenter Server 4.0 installation directory may have been relocated to another drive.
- For Microsoft SQL Server, copy create_alarms_mssql.sql.
- For Oracle Database, copy create_alarms_oracle.sql.
Create backups of the vCenter Server database.
Stop the VMware VirtualCenter Server service. For more information, see Stopping, starting, or restarting vCenter services (1003895).
Execute the downloaded SQL queries:
- For Microsoft SQL Server:
  1. Log in to the vCenter database using the same user credentials that vCenter Server uses to connect to the database.
  2. In Microsoft SQL Server Management Studio, navigate to the folder Databases > VC_database_DSN.
  3. Click New Query.
  4. In the query editor, copy and paste the contents of create_alarms_mssql.sql.
  5. Press F5 to run the script.
  6. Start the VMware VirtualCenter Server service. For more information, see Stopping, starting, or restarting vCenter services (1003895).
- For Oracle Database:
- Based on VMware KB 1010399

Kunnskapsbase