In BusinessObjects Enterprise, a database can be defined as a data repository that organizes a collection of information into structures called tables for rapid search and information retrieval.
Databases allow tables to be grouped together into collections of logically related tables called tablespaces. Tables are grouped into tablespaces within a database system in the same way that files are grouped into a directory within a file system.
Note: This documentation uses the terms "tablespace" and "database" interchangeably.
The following database systems are supported for the Central Management System (CMS) database:
See the BusinessObjects Enterprise Supported Platforms documents on the CA Business Intelligence DVD for a full list of database systems supported for each component of BusinessObjects Enterprise.
You are free to use any database system with BusinessObjects Enterprise as long as it is also supported by the CA Technologies product implementing BusinessObjects Enterprise (see your CA Technologies product documentation). If you do not have a database system ready, the BusinessObjects Enterprise installer can create and configure a MySQL database system as part of the installation process.
Notes:
BusinessObjects Enterprise uses several databases to store internal system information. They can be configured as several tablespaces within a single database system, or as tablespaces distributed across several database systems.
The following table details the different database or tablespace repositories used by BusinessObjects Enterprise.
|
Repository |
Description |
Mandatory for Installation? |
|---|---|---|
|
CMS |
Main repository that stores BusinessObjects Enterprise user, group, security, content, and service information. If you do not have a CMS database from a previous installation, objects in this database will be initialized by the BusinessObjects Enterprise installer. |
Yes |
|
Auditing |
Activity tracking repository that allows administrators to view system usage information, such as the number of report generation or login events. Auditing can be enabled and configured during the installation process. |
No |
BusinessObjects Enterprise scripts require database user privileges that permit the creation and deletion of database objects, including tables, indexes, and temporary data. Rather than assign administrative privileges to the account used by BusinessObjects Enterprise, this table summarizes the privileges required for each supported database system.
|
Database |
Required Account or Role Privileges |
|---|---|
|
IBM DB/2 |
User with Connect to database, Create tables, and Create schemas implicitly enabled |
|
Oracle Database |
User with the following privileges enabled:
Alternatively, a user with the CONNECT and RESOURCE roles enabled, and the Admin Option setting disabled for both roles. |
|
MySQL |
Default database owner (DBO) account permissions |
|
Microsoft SQL Server |
Default database owner (DBO) account permissions |
|
Sybase ASE |
Default database owner (DBO) account permissions |
Databases may require specific configuration to function best with BusinessObjects Enterprise. The following table provides a list of additional configuration settings.
|
Database |
Additional Required Settings |
|---|---|
|
IBM DB/2 |
DB2CODEPAGE=1208 |
|
Oracle |
NLS_LANG must be set to a valid UTF-8 setting, such as AMERICAN_AMERICA.WE8MSWIN1252 or AMERICAN_AMERICA.AL32UTF8. The FORCE setting must be enabled. |
|
Sybase |
LC_ALL must be set to a valid locale, as found in the configuration file SYBASE_HOME/locales/locales.dat. |
|
Copyright © 2010 CA.
All rights reserved.
|
|