Knowledge Base

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

Configuring Oracle databases for VMware vCloud Director (1025768)

Purpose

This article provides best practice procedures for configuring an Oracle database before installing VMware vCloud Director.

Resolution

 
Note: The commands in this article are run when Oracle is installed on Microsoft Windows and when you are connected to SQLPlus as SYSDBA. To connect to SQLPlus as SYSDBA, run the commands:
 
C:\Users\Administrator> set ORACLE_SID=orcl
C:\Users\Administrator> sqlplus "/as sysdba"
SQL*Plus: Release 10.2.0.1.0 - Production on Wed Jul 21 14:54:44 2010
Copyright (c) 1982, 2005, Oracle. All rights reserved.

Connected to:
Oracle Database 10g
Enterprise Edition Release 10.2.0.1.0 - Production
 
Follow these best practices for configuring an Oracle database:
  • Verify that the database is supported and compatible with VMware Cloud Director. These databases are compatible:
    • Oracle 10g Standard Edition Release 2 (10.2.0.1.0)
    • Oracle 10g Enterprise Edition Release 2 (10.2.0.1.0)
    • Oracle 11g Standard Edition
    • Oracle 11g Enterprise Edition

  • A separate database for VMware vCloud Director is strongly recommended. Use commands of the following 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;


  • When you create the Cloud Director database user account, you must specify CLOUD_DATA as the default tablespace.
    Create user $vclouduser identified by $vcloudpass default tablespace CLOUD_DATA;

  • Ensure that these system privileges are granted to the user account:
    • CONNECT
    • RESOURCE
    • CREATE VIEW
    • CREATE TRIGGER
    • CREATE TYPE
    • CREATE PROCEDURE
    • CREATE SEQUENCE
    • CREATE MATERIALIZED VIEW
To grant these privileges, run the command:

SQL> grant CONNECT,RESOURCE,CREATE VIEW, CREATE TRIGGER, CREATE TYPE, CREATE PROCEDURE, CREATE SEQUENCE, CREATE MATERIALIZED VIEW to <user>;

Grant succeeded.
  • The database must be configured to use the AL16UTF16 character set. To check the National Character Set, run the command:

    SQL> select * from nls_database_parameters where parameter = 'NLS_NCHAR_CHARACTERSET';

  • The database must be configured to allow at least 75 connections per Cloud Director cell. The number of connections must not exceed 75*S, where S is the number of cells in the Cloud Director cluster. There is one cell for each Cloud Director server in the cluster. Each Cloud cell, by default, may open up to 75 Database connections. Oracle, by default, may only allow 150 maximum connections to any schema. Therefore, 3 cells under reasonably high load may begin to experience rejected connections.
    • To check the number of configured sessions, run the command:

      SQL> show parameter sessions;

      The output appears similar to:

      NAME TYPE VALUE
      ------------------------------------ ----------- ----------------------------
      sessions integer 49

    • To change the number of sessions, run the command:

      SQL> alter system set sessions=150 scope=spfile;

      System altered.
  • The firewall on Cloud Director host must allow traffic over TCP port 1521, which is used as a default Oracle database port.

Tags

vcloud-director-database

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

  • 15 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)
  • 15 Ratings
Actions
KB: