Database requirements

This topic describes the requirements for the TrueSight Capacity Optimization database and the two database technologies. Refer to the following sections for details:

TrueSight Capacity Optimization supports two different database technologies:

You must validate these options for your environment by performing an appropriate sizing exercise. For more information, see Planning. The Running the database on a virtual machine section provides recommendations for using a virtualized server.

Oracle database requirements

The following software is required for the TrueSight Capacity Optimization database server that uses an Oracle database:

  • Operating system: Any 64-bit operating system supported by the Oracle database.

Oracle Database Server: The following versions are currently supported:

12c R2
  • Standard Edition 2 (SE2)
  • Enterprise Edition (EE)
12c R1
  • Standard Edition One (SE1)
  • Standard Edition (SE)
  • Enterprise Edition (EE)
  • Express Edition (XE) (11.2 only)
11g R2 and later

1 - Oracle version does not work as expected (caused by Oracle bug 20508819). You can perform one of the following tasks as a workaround:

  • Add Oracle instance init parameter _optimizer_aggr_groupby_elim=false to use Oracle version
  • Use Oracle version or


  • The Database Server supports both the Oracle 12c R1 multi-tenancy options: Container Database (CDB) and Pluggable Database (PDB).
  • You must use Oracle 12c R1 with CentOS 7.x, Red Hat Enterprise Linux 7.x, and Oracle Enterprise Linux 7.x because Oracle 11g R2 is not supported on these operating systems.
  • The Oracle Advanced Compression (OAC) feature is not recommended for use with a TrueSight Capacity Optimization Database Server. Activating this feature can have a significant impact on performance in terms of ETL execution time and data warehouse (DWH) data processing time.
  • SQL*PLUS and SQL*LDR do not work on Oracle client 11g R2 running on an AMD processor platform. To fix this issue, you need to deploy Oracle Patch Set 8670579 after you install the Oracle Client.
    This issue is not a TrueSight Capacity Optimization issue, but a known issue in the Oracle 11gR2 client.


BMC strongly recommends use of the following software for the TrueSight Capacity Optimization Database Server:

  • Character set: AL32UTF8 — As part of Internationalization support and Unicode standard alignment, use this character set to prevent issues related to wrong character encoding during the integration of heterogeneous datasources.
  • Oracle Partitioning: Install and enable Oracle Partitioning on the Database Server, especially for very large databases to ensure maximum performance.
  • Oracle Java Virtual Machine (JVM): Install and enable Oracle JVM on the Database Server.
  • Oracle Database version: Use Oracle database 11gR2 version or later.

Configuration recommendations

Configuration itemRecommendation
  • TrueSight Capacity Optimization database schema uses four tablespaces: two for capacity data and two for indexes. For better performance, BMC recommends that the two data tablespaces be allocated on a different physical device than the two index tablespaces.
  • The default schema owner user is BCO_OWN. This user must have permissions on the five tablespaces and also on a temporary tablespace. 

The schema uses global temporary tables that can reach considerable size.

Space allocation recommendations

  • Allocate a minimum of 3 GB for the temporary tablespace.
  • Allocate a minimum of 3 GB for the UNDO tablespace.
Memory Management

Use automatic memory management. Configure only the limit, and Oracle will manage the SGA and PGA.


Set the memory limit at 80 percent of the total memory.

Listener configuration

By default, the Oracle instance sets the listener port to 1521. You can also set a different port according to Oracle guidelines.


Set the max sessions parameter to 300. This is the minimum requirement.

For very large deployments involving many Capacity Optimization servers (that is, more than five ETL engines), you must increase the max sessions parameter to avoid saturation.

Block size

The default block size should be used.


Set a block size between 8 KB and 32 KB.

Archive logging

BMC recommends running the database in archive logging (ARCHIVELOG) mode and using Oracle best practices:

  • Perform periodic full backups (for example, weekly).
  • Perform incremental backups (for example, daily).
  • Perform continuous archive log backups (for example, every 6 hours).

The size and frequency needed for the archive logs depends linearly on the size of the TrueSight Capacity Optimization database in terms of daily population load. As a rough estimation, provide 2.5 GB/hour for every 10 million rows loaded per day. For example, provide 5 GB/hour for a TrueSight Capacity Optimization database sized for 20 million rows per day.

Archive logging allows you to do a full backup without shutting down TrueSight Capacity Optimization. Daily shutdown for backup can cause problems to application tasks and services: no task can be executed in the database maintenance window, so you would have to reconfigure OOTB tasks. If the database is shut down, TrueSight Capacity Optimization will log several exceptions and send the administrator an email, so you would also have to stop TrueSight Capacity Optimization components before turning off the database.

REDO logs
  • Allocate at least 4 GB for the REDO logs. You must allocate enough archive space to accommodate the REDO logs for the backup period. For example, if backup is taken every six hours, the archive space will need to be at least 24 GB.
  • Recommended number of groups and file size: Six groups of REDO logs, with redo file size of 512MB.
Auto space advisorIf you schedule this task, it is recommended that you schedule it for execution on a weekly basis.
Gather database statisticsIf you schedule this task, it is recommended that you schedule it for execution after every 2 or 3 days.


These recommendations are based on technical considerations. Refer to the latest Oracle documents for details about any licensing restrictions.

PostgreSQL database requirements

The following software is required for the TrueSight Capacity Optimization Database Server:

  • Operating system: Any 32- or 64-bit operating system supported by the PostgreSQL Database Server

  • PostgreSQL Database Server: Versions 9.6, 9.5, 9.4 and 9.3.6 are currently supported.


    Install PostgreSQL version 9.4 or later for improved performance.


  • The current compatibility offering for the PostgreSQL database supports large environments handling up to 80 million records per day.
  • The EnterpriseDB PostgreSQL database is not supported.

Configuration recommendations

Configuration itemRecommendation
Users, Roles
  • The first installation of TrueSight Capacity Optimization Application Server will automatically create the users and roles needed by the application. The installer will request the credentials for the PostgreSQL privileged user (usually named postgres). 
  • Default names are provided for users and roles but they can be customized during installation.
  • The default schema owner user is BCO_OWN.
Schema and Tablespaces
  • TrueSight Capacity Optimization database schema uses five tablespaces: two for capacity data, two for indexes, and one for view configurations. For better performance, BMC recommends that the two data tablespaces be allocated on a different physical device than the two index tablespaces.
  • Default names are provided for tablespaces (BCO_DATA, BCO_DATA_IDX, BCO, BCO_IDX) but they can be customized during installation.
  • Tablespaces are automatically created during installation of the first TrueSight Capacity Optimization Application Server. Before launching the installation, a proper directory structure must be prepared on Database Server to host tablespaces. 
    • For example, a parent directory like "/var/lib/pgsql/data" can be used to host tablespace files (or any other directory on the Database Server machine). Inside this parent folder, a folder for each tablespace must be created before launching the installation. By default the structure could be as follows (the names are case sensitive)
      • /var/lib/pgsql/data
        • /BCO_DATA
        • /BCO_DATA_IDX
        • /BCO
        • /BCO_IDX
    • The folders created above must be accessible and owned by the OS user that runs the PostgreSQL process. The directories must be empty. The Capacity Optimization installer will request the location of the above tablespaces folder.
Client Authentication
  • Make sure all TrueSight Capacity Optimization server machines (excluding Remote ETL Servers) can access the Database Server by allowing access in pg_hba.conf
  • Recommended configuration in pg_hba.conf is to use MD5 encryption for passwords.
Instance parameters
  • BMC recommends adding the following parameters to the configuration of the Database Server in postgresql.conf or equivalent file:
listen_addresses = '*'
max_connections = 300
default_statistics_target = 50
constraint_exclusion = on
wal_buffers = 8MB

min_wal_size = 1GB
max_wal_size = 2GB

checkpoint_timeout = 15min
checkpoint_completion_target = 0.9
log_min_messages = fatal
log_min_error_statement = fatal

#following parameters should be tuned according to actual memory available to Database server machine
#example of configuration for 8GB RAM

maintenance_work_mem = 512MB
effective_cache_size = 5GB
work_mem = 48MB
shared_buffers = 2GB

Note: For PostgreSQL 9.5, 9.4, and 9.3.6, add checkpoint_segments = 32 parameter instead of min_wal_size = 1GB and max_wal_size = 2GB parameters.

Running the database on a virtual machine

The TrueSight Capacity Optimization database can be set up by using a virtual machine, instead of a physical machine.

  • Ensure that resources are available to the TrueSight Capacity Optimization database, similar to mission critical workloads hosted on virtual machines. The choice of hypervisor and its configuration determines the levels of contention with other virtual machines sharing the CPU, memory, and other resources.
  • For TrueSight Capacity Optimization, I/O throughput is a key sizing parameter, as explained in Sizing considerations. Configure the hypervisor layer to ensure that the required I/O throughput is available.
Was this page helpful? Yes No Submitting... Thank you