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

Note

vCenter Update Manager also requires a database. VMware recommends that you use separate databases for vCenter Server and vCenter Update Manager.

If your VirtualCenter 2.x database is not supported for upgrade to vCenter Server 4.0 Update 1 and later, first upgrade your database (or import your database into a database that is supported for upgrade to vCenter Server) and then upgrade vCenter Server.

Configuration and Patch Requirements lists the configuration and patch requirements for the databases that are supported for upgrade to vCenter Server. If your database is not listed in this table, see Database Scenarios.

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

Configuration and Patch Requirements

Database Type

Patch and Configuration Requirements

Microsoft SQL Server 2005 Express

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

You cannot install the bundled database during an upgrade to vCenter Server. If you want to use the bundled database, Microsoft SQL Server 2005 Express must be already installed or you must perform a clean installation of vCenter Server.

Microsoft SQL Server 2005

For Microsoft Windows XP, apply MDAC  2.8 SP1 to the client. Use the SQL Native Client driver (version 9.x) for the client.

Ensure that the machine has a valid ODBC DSN entry.

Microsoft SQL Server 2008

For Microsoft Windows XP, apply MDAC  2.8 SP1 to the client. Use the SQL Native Client driver (version 10.x) for the client.

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.