Question: What DB permissions are required after the install of vCenter 4.1?
Currently KB 1022104 states the following:
1. Make sure your database requirements and patch levels are compliant:
Note: For more information, see vSphere Compatibility Matrix and vCenter Server Database Patch and Configuration Requirements. To use an existing database, you will need to provide a 64 bit system DSN which points to the vCenter Server database. Also, ensure that you have created a full backup of your database before proceeding. If you are using Oracle see Upgrading to vCenter Server 4.1 fails with the error: Trigger, procedure or function created with PL/SQL compilation error (1026331).
o Microsoft SQL server Database Support:
§ Microsoft SQL Server 2005 Express
Note: Microsoft SQL Server 2005 Express is intended to be used for small deployments of up to 5 hosts and/or 50 virtual machines.
§ Microsoft SQL Server 2005 Standard edition (SP1, SP2, SP3)
§ Microsoft SQL Server 2005 Standard edition (SP2, SP3) 64 bit
§ Microsoft SQL Server 2005 Enterprise edition (SP1, SP2, SP3)
§ Microsoft SQL Server 2005 Enterprise edition (SP2, SP3) 64 bit
§ Microsoft SQL Server 2008 Standard Edition
§ Microsoft SQL Server 2008 Standard Edition 64-bit
§ Microsoft SQL Server 2008 Enterprise Edition
§ Microsoft SQL Server 2008 Enterprise Edition 64-bit
o Oracle Database Support:
§ Oracle 10g Standard edition (Release 2 [10.2.0.4])
§ Oracle 10g Enterprise edition (Release 2 [10.2.0.4])
§ Oracle 10g Enterprise edition (Release 2 [10.2.0.4]) 64-bit
§ Oracle 11g Standard edition
§ Oracle 11g Enterprise edition
o IBM DB2 9 Support
§ IBM DB2 Express C
§ IBM DB2 Express Edition 9
§ IBM DB2 Workgroup Server Edition 9
§ IBM DB2 Enterprise Server Edition 9
Note: IBM DB2 database is only supported for vCenter. There is no support for Update Manager or any plug-in that requires a database.
2. Make a full backup of the vCenter database.
3. Make sure that you have these permissions:
o Microsoft SQL:
§ Grant the System DSN user of the vCenter Database db_owner privileges on the vCenter database.
§ Grant the System DSN user of the vCenter Database db_owner privileges on the MSDB database.
Note: The db_owner privileges on the MSDB database are required for installation and upgrade only.
o Oracle:
§ Grant dba permissions to the vCenter Server user.
4. Ensure that your ODBC System DSN is using the proper driver and that it is a 64-bit DSN.
Microsoft SQL must use the SQL Native Client driver.
a. Stop the VirtualCenter Server service. This step is recommended, especially if the vCenter Server database is on a remote system.
b. Click Start > Control Panel > Administrative Tools > Services > VMware VirtualCenter Server.
c. Log in to your vCenter Server with a Local Administrator account on your Windows system to run the upgrade.
d. Ensure no processes are running that conflict with the ports that vCenter Server uses.
e. Configure any new vSphere 4.1 licences.
Page 69 of the vSphere 4.1 Install guide at https://www.vmware.com/pdf/vsphere4/r41/vsp_41_esxi_i_vc_setup_guide.pdf also provides information concerning the database permissions.
VMwarewolf