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 Windows database requirements for supporting products and the Linux database requirements for supporting products sections. 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 precreate database option if you meet the requirements listed in this topic.

This topic explains the database requirements for the following products:

  • BMC AR System Server – Cloud Portal and Database
  • BMC Server Automation
  • BMC Network Automation

This topic provides the following information:

Oracle requirements for Linux

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

Supported Oracle database version

The BMC Cloud Lifecycle Management solution supports Oracle Database 11g R2 64-bit on the Red Hat Enterprise Linux 5.x 64-bit OS.

Unicode and character set requirements for the Oracle database

The following Unicode and character set requirements apply to Oracle databases:

  • You must synchronize all your databases so that their character sets and Unicode settings are correctly aligned with their <product>, for example, 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.

Packages required for the Oracle client

Install these packages for products that require an Oracle client.


Packages required for Red Hat Linux 6.x

  • unixODBC-devel-2.2.14-11.el6.x86_64

  • unixODBC-devel-2.2.14-11.el6.i686

  • unixODBC-2.2.14-11.el6.i686

  • unixODBC-2.2.14-11.el6.x86_64

  • glibc-devel-2.12-1.47.el6_2.12.x86_64

  • glibc-devel-2.12-1.47.el6.i686

  • libstdc++.so.5 (use yum install compat-libstdc++-33.x86_64)

  • libgcc_s.so.1

Packages required for Red Hat Linux 5.x

  • compat-libstdc++-33-3.2.3-61

  • elfutils-libelf-devel-0.137-3.el5
  • elfutils-libelf-devel-static-0.137-3.el5
  • libaio-devel-0.3.106-5  (64-bit  and 32-bit)
  • libgcc-4.1.2-50.el5
  • libstdc++-devel-4.1.2-50.el5
  • unixODBC-2.2.11-7.1 (32-bit)
  • unixODBC-devel-2.2.11-7.1 (32-bit)
  • glibc-devel-2.5-58.i386
  • glibc-devel-2.5-58.x86_64
  • glibc-2.5-58.i686
  • glibc-2.5-58.x86_64
  • libstdc++.so.5 libgcc_s.so.1

All the packages listed are required for an Oracle client.

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 requirements. Before you begin your product installations, make sure that the database software and the instance that you created are running.

Additionally, you can use a precreated tablespace or allow the installer to create a tablespace for a given product, if the product supports it, during the installation. To use the precreated 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 requirements.

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, ensure 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';

Precreate database support and requirements for Linux

In the table in the product-specific database requirements, the valid values for the precreated tablespace support for Oracle are as follows:

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

For more information about precreated databases, see the documentation for the respective product in the documentation for related products.

Linux database requirements for supporting products

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

Oracle processes and sessions in Compact Deployment

If you are installing Compact Deployment or upgrading 3.1.x Single VM RDS on the Linux/Oracle platform, set the Oracle processes and sessions in the init.ora file to at least 300, if it not already configured. For example:
alter system set processes=300 scope=spfile; 

Oracle Virtual Private Database (VPD)

Oracle Virtual Private Database (VPD) is not officially supported for BMC Cloud Lifecycle Management, BMC AR System, BMC Server Automation, or BMC Network Automation, because BMC Software has not tested it. Many 3rd-party technologies are transparent for use with BMC products.  If Oracle VPD (or any other database feature) is 100% transparent, for example, to the AR System server or BMC Server Automation, it should not affect your installation or usage of these BMC products. If there are problems that can be reproduced in an environment without Oracle VPD, contact BMC Support so that they can investigate whether or not this is a BMC product issue.

SQL Server requirements for Windows

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

Note

You must have DBA credentials to create the database and users for the precreated database and installer-created database option.

Supported SQL Server database version

The BMC Cloud Lifecycle Management solution supports Microsoft SQL Server 2012 Enterprise Edition 64-bit on Microsoft Windows Server 2012 R2 Standard Edition 64-bit.

Tip

Microsoft Support provides useful information on determining the version and edition of SQL Server and its components.


Unicode and character set requirements for the SQL Server database

The following Unicode and character set requirements apply to the MS SQL Server database:

  • You must synchronize all your databases so that their character sets and Unicode settings are correctly aligned with their <product>, for example, BMC Remedy AR System settings.
  • You must run Unicode to Unicode or non-Unicode to non-Unicode. Do not mix these settings.
  • For MS SQL Server, you must set the Unicode data types to nchar, nvarchar, and ntext.

Precreate database support and requirements for Windows

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

  • Yes, but optional — A precreated 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 precreated database.
  • No — A precreated 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 table in the following section, and users for products that require them. If you want to use the precreated database option, ensure that you use the file size details listed in the table.

For more information about precreated databases, see the documentation for the respective product in the documentation for related products.

Windows database requirements for supporting products

The following table lists the requirements for SQL Server 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

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.

Comments