Database requirements

Not every product in the BMC Cloud Lifecycle Management solution requires a database. Certain products can share a database with other products in the solution, as explained in the table in this topic. You can install the database on the same host as the BMC product, or you can install a remote database. Regardless of where you install the database, you can use the pre-create database option if you meet the requirements listed in this topic.

This topic explains the database requirements for the following products:

  • BMC Remedy AR System Server & IT Service Mgt. Suite
  • BMC Remedy AR System Server – Cloud Database
  • BMC Atrium Core – Web Registry
  • BMC BladeLogic Server Automation
  • BMC BladeLogic Network Automation

Supported database versions

The BMC Cloud Lifecycle Management solution supports Microsoft SQL Server 2008 64 bit database on Windows and Oracle 11g 64 bit database on Linux systems.

UNICODE and character set requirements for databases

The UNICODE and character set requirements explained this section apply to both MS SQL and Oracle databases.

  • You must synchronize all your databases so that their character sets and UNICODE settings are correctly aligned with their BMC Remedy AR System settings.
  • You must run UNICODE to UNICODE or NON-UNICODE to NON-UNICODE. Do not mix these settings.
  • You must set the character sets to AL32UTF8.

Oracle requirements for Linux

This section explains the Oracle requirements for a Linux installation, such as pre-create options, tablespace requirements, and database requirements.

Tablespace and database instance requirements

For products in the solution that require a database, you can use a local or remote database. Certain products in the solution can share a database. Therefore, a specific Oracle database instance can be applied to one or more product installations, as explained in the table in this topic. Before you begin your product installations, make sure that the database and instance that you created are running.

Additionally, you can use a pre-created tablespace or allow the installer to create a tablespace for a given product, if the product supports it, during the installation. If you want to use the pre-created tablespace option, you must have required system user and password credentials. For more information about the tablesapce and database requirements per product in the solution, see the table in this topic.

Note

Make sure that the instance name you provide is less than or equal to 8 characters. Otherwise, the installer does not accept the instance name.

Oracle Real Application Clusters (RAC) Automatic Storage Management (ASM) requirements

If you are using Oracle ASM in your environment, make sure that the  DB_CREATE_FILE_DEST is set to an appropriate value. Otherwise the Tablespace will not be created successfully.


Example code: ALTER SYSTEM SET DB_CREATE_FILE_DEST = '+DATA2';

Pre-create database support and requirements

In the table, the values for the pre-created tablespace support for Oracle are:

  • Yes, but optional — This means that a pre-created tablespace is supported. However, you can optionally choose to have the installer create the tablespace during the installation process.
  • No, mandatory — This means that a pre-created tablespace is not supported. You must allow the installer to create a tablespace. However, you must create default, index, and temporary tablespaces for the user in advance.

Note

The BMC Cloud Lifecycle Management installer creates Oracle tablespaces with default file sizes with auto-extend set to on, as listed in the following table, and user for products that require them. If you want to use the pre-created database option, make sure that you use the file size details listed in the table.

For more information about pre-created databases, see the documentation for the respective product in the documentation for related products topic.

MS SQL requirements for Windows

This section explains the MS SQL requirements for the Windows installation, such as pre-create options, tablespace requirements, and database requirements.

Pre-create database support

For MS SQL databases, you can either have the installer create a database during the installation process or pre-create a database for your products, as indicated in the table in this topic. However, the installer will require you to authenticate a pre-created database.

Note

To create the database (MS SQL) or tablespace (Oracle), and users (MS SQL and Oracle) for the pre-created database or installer-created database option, database administrator (DBA) credentials are required.

In the table, the values for the pre-create database support for MS SQL are:

  • Yes, but optional — This means that an existing database is supported. However, you can optionally choose to have the installer create the database during the installation process.
  • Yes, and mandatory — This means that you must use a pre-created database.
  • No — This means that an existing database is not supported. You must allow the installer to create a database and a user.

Note

The BMC Cloud Lifecycle Management installer creates an MS SQL database with the default data and log file sizes listed in the following table, and user for products that require them. If you want to use the pre-created database option, make sure that you use the file size details listed in the table.

For more information about pre-created databases, see the documentation for the respective product in the documentation for related products topic.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*