After you choose a database type, make sure you understand the configuration and patch requirements for the database.

vCenter Server databases require a UTF codeset.

Configuration and Patch Requirements lists the configuration and patch requirements for the databases that are supported with vCenter Server.

Contact your DBA for the appropriate database credentials.

For a complete list of database versions supported with vCenter Server, see the vSphere Compatibility Matrixes on the VMware vSphere documentation Web site.

Configuration and Patch Requirements

Database Type

Patch and Configuration Requirements

IBM DB2 9.5

If the database is not local to the vCenter Server system, install the IBM Data Server Runtime Client.

Install the IBM DB2 native client according to the IBM instructions for your DB2 version.

If you are not running DB2 with DB2 9.5 fix pack 5, install Hotfix 22318 for DB2 9.5.0 on the system where you are installing vCenter Server.

Ensure that C:\Program Files\IBM\SQLLIB\BIN is in the system path. DB2 might be installed at a different location.

You might need to restart the Microsoft Windows machine for the service to recognize the change in the environment variable.

Ensure that the machine has a valid ODBC data source name (DSN) entry.

Microsoft SQL Server 2005 Express

Bundled database that you can use for small deployments of up to 5  hosts and 50  virtual machines.

If the machine has Microsoft SQL Native Client installed, remove it before installing vCenter Server with the bundled database.

Microsoft SQL Server 2005

Ensure that the machine has a valid ODBC DSN entry.

If Microsoft SQL Server 2005 is not already installed and the machine has MSXML Core Services 6.0 installed, remove MSXML Core Services 6.0 before installing Microsoft SQL Server 2005. If you cannot remove it using the Add or Remove Programs utility, use the Windows Installer CleanUp utility. See http://support.microsoft.com/kb/968749.

Microsoft SQL Server 2008

Ensure that the machine has a valid ODBC DSN entry.

Oracle 10g

If necessary, first apply patch 10.2.0.4 (or later) to the client and server. Then apply patch 5699495 to the client.

Ensure that the machine has a valid ODBC DSN entry.

For the Oracle Instant client, copy ojdbc14.jar to the vCenter Server tomcat directory (<vCenter install location>\Infrastructure\tomcat\lib)

The Oracle 10g client comes with ojdbc14.jar (<Oracle client install location>\oracle\product\10.2.0\<instance_name>\jdbc\lib). The vCenter Server installer copies the file from the Oracle client install location to the vCenter Server tomcat directory (<vCenter install location>\Infrastructure\tomcat\lib)

If the ojdbc14.jar file is not found in the Oracle 10g client location, the vCenter Server installer prompts you to copy the file manually. You can download the file from http://www.oracle.com/technology/software/tech/java/sqlj_jdbc/htdocs/jdbc101040.html.

Oracle 11g

Ensure that the machine has a valid ODBC DSN entry.

For the Oracle Instant client, copy ojdbc14.jar to the vCenter Server tomcat directory (<vCenter install location>\Infrastructure\tomcat\lib)

The Oracle 11g client comes with ojdbc14.jar (<Oracle client install location>\app\Administrator\product\11.1.0\<instancename>\sqldeveloper\jdbc\lib). The vCenter Server installer copies the file from the Oracle client install location to the vCenter Server tomcat directory (<vCenter install location>\Infrastructure\tomcat\lib)

If the ojdbc14.jar file is not found in the Oracle 11g client location, the vCenter Server installer prompts you to copy the file manually. You can download the file from http://www.oracle.com/technology/software/tech/java/sqlj_jdbc/htdocs/jdbc101040.html.