Knowledge Base

The VMware Knowledge Base provides support solutions, error messages and troubleshooting guides
 
Search the VMware Knowledge Base (KB)   View by Article ID
 

Installing and configuring a vCloud Director 5.1 or 5.5 database (2034540)

Purpose

vCloud Director 5.1 and 5.5 cells use a database to store shared information. This database must exist before you can complete installation and configuration of vCloud Director software.  This article describes how to create these databases so you can complete your vCloud Director installation.

Note: Regardless of the database software you choose, you must create a separate, dedicated database schema for vCloud Director to use. vCloud Director cannot share a database schema with any other VMware product.

Resolution

Supported vCloud Director databases
 
vCloud Director supports Oracle and Microsoft SQL Server databases. The most current information about supported databases is available from the VMware Product Interoperability Matrixes. 
 
Configuring an Oracle database
 
Oracle databases have specific configuration requirements when you use them with vCloud Director 5.1 and 5.5. You must install and configure a database instance and create the vCloud Director database user account the before you install vCloud Director.
 
To configure an Oracle database: 
  1. Configure the database server. A database server configured with 16GB of memory, 100GB storage, and 4 CPUs should be adequate for most vCloud Director clusters.
  2. Create the database instance. Use commands with this form to create separate data (CLOUD_DATA) and index (CLOUD_INDX) tablespaces:

    Create Tablespace CLOUD_DATA datafile '$ORACLE_HOME/oradata/cloud_data01.dbf' size 1000M autoextend on;
    Create Tablespace CLOUD_INDX datafile '$ORACLE_HOME/oradata/cloud_indx01.dbf' size 500M autoextend on;

  3. Create the vCloud Director database user account. This command creates database user name vcloud with password vcloudpass:

    Create user $vcloud identified by $vcloudpass default tablespace CLOUD_DATA;

    Note: When you create the vCloud Director database user account, you must specify CLOUD_DATA as the default tablespace, and vcloudpass must be the password.

  4. Configure database connection, process, and transaction parameters. The database must be configured to allow at least 75 connections per vCloud Director cell plus about 50 for Oracle's own use. You can obtain values for other configuration parameters based on the number of connections, where C represents the number of cells in your vCloud Director cluster:
     
    Oracle Configuration Parameter Value for C Cells
    CONNECTIONS 75*C+50
    PROCESSES = CONNECTIONS
    SESSIONS = PROCESSES*1.1+5
    TRANSACTIONS = SESSIONS*1.1
    OPEN_CURSORS = SESSIONS

  5. Create the vCloud Director database user account. Do not use the Oracle system account as the vCloud Director database user account. You must create a dedicated user account for this purpose. Grant these system privileges to the account:

    CONNECT
    RESOURCE
    CREATE TRIGGER
    CREATE TYPE
    CREATE VIEW
    CREATE MATERIALIZED VIEW
    CREATE PROCEDURE
    CREATE SEQUENCE


  6. Note the database service name so you can use it when you configure network and database connections. To find the database service name, open the file $ORACLE_HOME/network/admin/tsnames.ora on the database server and look for an entry with this form:

    (SERVICE_NAME = orcl.example.com) 
Configuring a Microsoft SQL Database
 
Microsoft SQL databases have specific configuration requirements when you use them with vCloud Director. You must install and configure a database instance, and create the vCloud Director database user account before you install vCloud Director.
 
vCloud Director database performance is an important factor in overall vCloud Director performance and scalability. vCloud Director uses the Microsoft SQL tmpdb file when storing large result sets, sorting data, and managing data that is being concurrently read and modified. This file can grow significantly when vCloud Director is experiencing heavy concurrent load.
 
It is a good practice to create the tmpdb file on a dedicated volume that has fast read and write performance. For more information
about the tmpdb file and Microsoft SQL Server performance, see http://msdn.microsoft.com/en-us/library/ms175527.aspx.
 
Note: You must be familiar with Microsoft SQL Server commands, scripting, and operation. To configure Microsoft SQL Server, log on to a Microsoft SQL server using administrator credentials. You must configure Microsoft SQL server to run with the LOCAL_SYSTEM identity, or any identity with the privilege to run a Windows service.
 
To configure your Microsoft SQL database for vCloud Director:
  1. Configure the database server. A database server configured with 16GB of memory, 100GB storage, and 4 CPUs should be adequate for most vCloud Director clusters.
  2. Specify Mixed Mode authentication during Microsoft SQL setup. Windows Authentication is not supported when using Microsoft SQL with vCloud Director.
  3. Create the database instance. This script creates the database and log files, specifying the proper collation sequence:

    USE [master]
    GO
    CREATE DATABASE [vcloud] ON PRIMARY
    (NAME = N'vcloud', FILENAME = N'C:\vcloud.mdf', SIZE = 100MB, FILEGROWTH = 10% )
    LOG ON
    (NAME = N'vcdb_log', FILENAME = N'C:\vcloud.ldf', SIZE = 1MB, FILEGROWTH = 10%)
    COLLATE Latin1_General_CS_AS
    GO


    Note: The values shown for SIZE are suggestions. You might need to use larger values depending on the size of your environment.

  4. Set the transaction isolation level. This script sets the database isolation level to READ_COMMITTED_SNAPSHOT:

    USE [vcloud]
    GO
    ALTER DATABASE [vcloud] SET SINGLE_USER WITH ROLLBACK IMMEDIATE;
    ALTER DATABASE [vcloud] SET ALLOW_SNAPSHOT_ISOLATION ON;
    ALTER DATABASE [vcloud] SET READ_COMMITTED_SNAPSHOT ON WITH NO_WAIT;
    ALTER DATABASE [vcloud] SET MULTI_USER;
    GO

    For more information about transaction isolation, see the Microsoft article http://msdn.microsoft.com/en-us/library/ms173763.aspx.

    Note: The preceding link was correct as of September 11, 2012. If you find the link is broken, provide feedback and a VMware employee will update the link.
  5. Create the vCloud Director database user account. This script creates database user name vcloud with password vcloudpass:

    USE [vcloud]
    GO
    CREATE LOGIN [vcloud] WITH PASSWORD = 'vcloudpass', DEFAULT_DATABASE =[vcloud],
       DEFAULT_LANGUAGE =[us_english], CHECK_POLICY=OFF
    GO
    CREATE USER [vcloud] for LOGIN [vcloud]
    GO

    Note: You must use the username vcloud and password vcloudpass.

  6. Assign permissions to the vCloud Director database user account. This script assigns the db_owner role to the database user created in Step 5:

    USE [vcloud]
    GO
    sp_addrolemember [db_owner], [vcloud]
    GO 

Update History

01/17/2014 - Added vCloud Director 5.5 to products

Request a Product Feature

To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature page.

Feedback

  • 7 Ratings

Did this article help you?
This article resolved my issue.
This article did not resolve my issue.
This article helped but additional information was required to resolve my issue.
What can we do to improve this information? (4000 or fewer characters)
  • 7 Ratings
Actions
KB: