Unsupported content This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

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 Product-specific database requirementssection. 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 & IT Service Management Suite
  • BMC Remedy AR System Server – Cloud Database
  • BMC Server Automation
  • BMC Network Automation
  • BMC ProactiveNet Performance Management Central Server (Linux only)
  • BMC ProactiveNet Performance Management Server (Linux only)

This topic provides the following information:

Supported database versions

The BMC Cloud Lifecycle Management solution supports the following databases:

  • Microsoft SQL Server 2008 R2 64-bit on Microsoft Windows 2008 R2 64-bit OS
  • Oracle Database 11_g_ R2 64-bit on Red Hat Enterprise Linux 5.5 64-bit OS

UNICODE and character set requirements for databases

The following UNICODE and character set requirements apply to both MS SQL Server 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.
  • For Oracle, you must set the character sets to AL32UTF8.
  • For MS SQL Server, you must set the Unicode data types to nchar, nvarchar, and ntext.

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, you can apply a specific Oracle database instance to one or more product installations, as explained in the Product-specific database requirementssection. 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 tablespace and database requirements per product in the solution, see the Product-specific database requirementssection.

Note

The instance name that you provide must be less than or equal to 8 characters. Otherwise, the installer does not accept the instance name.

Oracle RAC ASM requirements

If you are using Oracle Real Application Clusters (RAC) Automatic Storage Management (ASM) in your environment, make sure that the DB_CREATE_FILE_DEST property is set to an appropriate value. Otherwise the tablespace is not created successfully.

Example
ALTER SYSTEM SET DB_CREATE_FILE_DEST = '+DATA2';

Pre-create database support and requirements

In the table in Product-specific database requirements, the values for the pre-created tablespace support for Oracle are as follows:

  • Yes, but optional — A pre-created tablespace is supported. However, you can optionally choose to have the installer create the tablespace during the installation process.
  • No, mandatory — 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 users for products that require them. If you want to use the pre-created database option, ensure that you use the file size details listed in the table. You require database administrator (DBA) credentials to create the tablespace and users for the pre-created database and installer-created database option.

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

SQL Server requirements for Windows

For SQL Server databases, you can have the installer create a database during the installation process or you can pre-create a database for your products, as indicated in the table in product-specific database requirements. However, the installer requires you to authenticate a pre-created database.

Note

You require DBA credentials to create the database and users for the pre-created database and installer-created database option.

In the table in product-specific database requirements, the values for the pre-created database support for SQL Server are as follows:

  • Yes, but optional — A pre-created database is supported. However, you can optionally choose to have the installer create the database during the installation process.
  • Yes, and mandatory — You must use a pre-created database.
  • No — A pre-created 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 SQL Server database with the default data and log file sizes listed in the following table, and users for products that require them. If you want to use the pre-created database option, ensure 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.

Product-specific database requirements

The following table list the requirements for SQL Server and Linux databases. For specific preparatory tasks that you must perform before you complete product installation, see the Additional information column.

 

Where to go from here

End-to-end installation flow

 

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