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.

System requirements for Linux

This topic summarizes the system requirements for the installer host, the supporting products, and databases used by BMC Cloud Lifecycle Management on Linux operating systems:

Linux installer host requirements

Before you launch the BMC Cloud LifeCycle Management installer, ensure that the installer host meets the requirements described in the following sections, based on your operating system. An installer host is the physical or virtual machine host on which you run the installer.

Installer host operating system, hardware, and permissions

Software

Hardware

Permissions

  • Red Hat Enterprise Linux 5.x (64-bit)
  • Red Hat Enterprise Linux 6.x (64-bit)
  • Oracle JRE 1.7 (64-bit)
  • Minimum 1 GB free hard-disk space for the installation directory
  • Minimum 30 GB free hard-disk space for storing installation applications
  • 2 CPUs (3-GHz dual processor)
  • Minimum 1 GB RAM during installation

You need root user credentials to perform all the installation

Failed to execute the [export-ignore] macro.

Installer host port requirements

If a firewall is configured in your environment, ensure that the firewall allows communication from the BMC Cloud Lifecycle Management installer host to the target computers by using the ports listed in The following section. The installer uses these ports to run commands to check application connectivity, database connections, RSCD connectivity, remote installation status, and so on. The port numbers in the table are the default values and might change based on user input or user environment configuration. For example, the database might be installed on port 1522 instead of port 1521. In that case, you must ensure that the correct port is enabled in the firewall.

 

Note

The Cloud Portal and Database server is installed by default on portmapper; the port number assigned in that case is port 0. For the Cloud Portal and Database server, the port number cannot be changed during the installation.

Component

Port number

Description

BMC Cloud Lifecycle Management installation program

12333, 9998

Installer ports

On the BMC Cloud Lifecycle Management installer host, ensure that port 12433 is free.

The BMC Cloud Lifecycle Management installer runs product installations remotely, using a silent installation. The product installations that are launched on the target hosts use port 12333 or 9998, as applicable, during invocation on the target host. The BMC Cloud Lifecycle Management installer queries the ports over the network to check whether the installation launched successfully. If a firewall is between the BMC Cloud Lifecycle Management installer host and a target host, ensure that these ports are not blocked.

 

BMC AR System Server - Cloud Portal and Database - Primary

0 (default value)

Cloud Portal and Database server, AR System server postinstallation, and Cloud Portal AR Extensions port

The default port on which Cloud Portal and Database server is installed by the BMC Cloud Lifecycle Management installer is port 0. The BMC Cloud Lifecycle Management installer queries the port over the network during AR System server postinstallation to check whether the AR System server is running. If a firewall is between the BMC Cloud Lifecycle Management installer host and a target host, ensure that this port is not blocked.

 

1521 (default value)

Cloud Portal and Database server database port

When installing Cloud Portal and Database, the installer attempts to ensure that the database is running by connecting to it through the user-supplied port. If the target Oracle database is installed using default values, the default port is 1521. If a firewall is between the BMC Cloud Lifecycle Management installer host and the database host, ensure that this port is not blocked.

BMC Server Automation

1521 (default value)

BMC Server Automation database port

When installing BMC Server Automation, the installer attempts to ensure that the database is running by connecting to it through the user-supplied port. If the target Oracle database is installed using the default values, the default port is 1521. If a firewall is between the BMC Cloud Lifecycle Management installer host and the database host, ensure that this port is not blocked.

 

4750

BMC Server Automation RSCD agent port

This requirement applies to all hosts (product hosts as well as the BMC Cloud Lifecycle Management installer host). If a firewall is between the BMC Cloud Lifecycle Management installer and a target host, ensure that port 4750 is not blocked, because the BMC Cloud Lifecycle Management installer executes remote commands for target host installations to the RSCD agent on the target host (which uses port 4750).

BMC Network Automation

1521 (default value)

BMC Network Automation database port

When installing BMC Network Automation, the installer attempts to ensure that the database is running by connecting to it through the user-supplied port . If the target Oracle database is installed using the default values, the default port is 1521. If a firewall is between the BMC Cloud Lifecycle Management installer host and the database host, ensure that this port is not blocked.

Preboot Execution Environment (PXE)

1521 (default value)

Requires the BMC Server Automation database port for PXE provisioning

When installing PXE, the installer attempts to ensure that the database is running by connecting to it through the user-supplied port . If the target Oracle database is installed using the default values, the default port is 1521. If a firewall is between the BMC Cloud Lifecycle Management installer host and the database host, ensure that this port is not blocked.

Failed to execute the [export-ignore] macro.

Preparing the installer host

Ensure that your installer host is correctly configured before you launch the installer, as described in the following sections:

To check for existing installer

Check if there is an existing installer from a previous installation on the host. If there is, back up and delete the previous /opt/bmc/Planner installation folder. Also, back up and delete the /opt/bmc/ProductRegistry.xml file.

To install from the tmp directory

If you want to install the BMC Cloud Lifecycle Management solution from the /tmp directory, ensure that you update the /etc/fstab filesystem with the correct mount property for the installationPath/tmp directory. Set the default value of the fourth column of the filesystem to exec. For more information, see Updating the fstab filesystem in Linux.

The installer also let you select Enable sub product remote staging directory option to enter an alternative staging area that you can use for all product installations if the /tmp directory on the remote hosts does not have sufficient space.
image2014-2-18 16:32:32.png 

To set the screen resolution

Set your computer screen to the recommended resolution of 1280 x 800 or greater.

To verify product host connectivity

Ensure that you can successfully launch the installation on a product host.

  1. Ensure that you can contact all target hosts (on which you want to install BMC products) from the installer host (for example, ping <hostName> -c 5).
  2. Run the ifconfig eth0 command on the target host, and verify that the IP address returned in the preceding step matches the target computer's IP address returned in this step.
Recommendation

Use tools such as Xmanager, Xming, or VConsole for connecting to the Linux computer and running the installer. With Xmanager and Xming, X applications installed on remote UNIX based computers run seamlessly with Windows applications side by side.

Failed to execute the [export-ignore] macro.

To remove existing NSH and RSCD

Notes

  • Domain credentials (even though they have admin permissions) are not supported during the RSCD installation using the BMC Cloud Lifecycle Management installer.
  • This task is not required for upgrades.

For new installations, the BMC Cloud Lifecycle Management installer installs version 8.6.01 of the BMC Server Automation Remote Server Call Daemon (RSCD) Agent and BMC Network Shell (NSH). The installer uses NSH to execute silent installation commands, which are accepted by the RSCD agent installed on the target hosts. The RSCD agent executes the commands so that the installer can remotely install the supporting BMC products.

If an existing RSCD Agent and NSH are installed, uninstall the RSCD agent and NSH:

  1. Go to /opt/bmc/BladeLogic/NSH/NSH. or /opt/bmc/Planner/NSH.
  2. Type the command ./Uninstall and follow the uninstallation process.
  3. Go to /opt/bmc/bladelogic directory and delete the RSCD folder (if it exists).
  4. Manually delete the /usr/lib/rsc folder and the /etc/rsc folder (if it exists).
  5. Reboot the machine after you have completed the cleanup.

For more information, see the Uninstalling other components on UNIX and Linux topic in the BMC Server Automation online technical documentation..

Failed to execute the [export-ignore] macro.

To install packages on Linux 5.x hosts

Specific packages are required to access the graphical user interface (GUI) on Red Hat Linux 5.x computers.

Note

Contact your Linux system administrator to check for these packages.

  • libXi-1.0.1-4.el5_4
  • libX11-1.0.3-11.el5
  • libXau-1.0.1-3.1
  • libICE-1.0.1-2.1
  • libSM-1.0.1-3.1
  • libXtst-1.0.1-3.1
  • libXtst-1.0.1-3.1.i386
  • libXext-1.0.1-2.1
  • compat-libstdc++-33-3.2.3-61.i386
  • compat-libtermcap-2.0.8-49.el6.x86_64
  • libXi.i386
  • xorg-x11-server-Xorg
  • xorg-x11-utils
  • xorg-x11-xauth

To verify whether the RPM is installed and to determine its current version, enter the following command:

yum list package
yum list compat-libstdc++-33

Failed to execute the [export-ignore] macro.

To install packages on Linux 6.x computers

Specific packages are required to access the graphical user interface (GUI) on Red Hat Linux 6.2 computers.

Note

Contact your Linux system administrator to check for these packages.

  1. Install the following 32-bit RPM packages:
    • unixODBC-devel-2.2.14-12.el6_3.i686.rpm
    • unixODBC-2.2.14-12.el6_3.i686.rpm
    • libX11-1.5.0-4.el6.i686.rpm
    • libXau-1.0.5-1.el6.i686.rpm
    • libxcb-1.8.1-1.el6.i686.rpm
    • libXext-1.3.1-2.el6.i686.rpm
    • libXi-1.3-3.el6.i686.rpm
    • libXtst-1.0.99.2-3.el6.i686.rpm
    • libXp-1.0.0-15.1.el6.i686.rpm
    • openssl-1.0.0-20.el6_2.5.i686.rpm
    • libgssglue-0.1-11.el6.i686.rpm
    • krb5-libs-1.10.3-10.el6_4.2.i686.rpm
    • libcom_err-1.41.12-14.el6.i686.rpm
    • keyutils-libs-1.4-4.el6.i686.rpm
    • libselinux-2.0.94-5.3.el6.i686.rpm
    • zlib-1.2.3-29.el6.i686.rpm
    • libidn-1.18-2.el6.i686.rpm
    • libcap-2.16-5.5.el6.i686.rpm
    • libattr-2.4.44-7.el6.i686.rpm
    • libstdc++-4.4.4-13.el6.i686.rpm
    • elfutils-libelf-devel-0.152-1.el6.i686.rpm
    • elfutils-libelf-devel-static-0.152-1.el6.i686.rpm
    • libaio-devel-0.3.107-10.el6.i686.rpm
    • libgcc-4.4.7-3.el6.i686.rpm
    • libstdc++-devel-4.4.6-4.el6.i686.rpm
    • glibc-devel-2.12-1.107.el6.i686.rpm
    • glibc-2.12-1.107.el6.i686.rpm
    • compat-libstdc++-33-3.2.3-69.el6.i686.rpm
    • compat-libtermcap-2.0.8-49.el6.i686.rpm
    • pam.i686 – Linux-PAM (Pluggable Authentication Modules for Linux) RPM
  2. Install the following 64-bit RPM packages:
    • unixODBC-devel-2.2.14-12.el6_3.x86_64.rpm
    • unixODBC-2.2.14-12.el6_3.x86_64.rpm
    • libX11-1.5.0-4.el6.x86_64.rpm
    • libXau-1.0.5-1.el6.x86_64.rpm
    • libxcb-1.8.1-1.el6.x86_64.rpm
    • libXext-1.3.1-2.el6.x86_64.rpm
    • libXi-1.3-3.el6.x86_64.rpm
    • libXtst-1.0.99.2-3.el6.x86_64.rpm
    • libXp-1.0.0-15.1.el6.x86_64.rpm
    • openssl-1.0.0-20.el6_2.5.x86_64.rpm
    • libgssglue-0.1-11.el6.x86_64.rpm
    • krb5-libs-1.10.3-10.el6_4.2.x86_64.rpm
    • libcom_err-1.41.12-14.el6.x86_64.rpm
    • keyutils-libs-1.4-4.el6.x86_64.rpm
    • libselinux-2.0.94-5.3.el6.x86_64.rpm
    • zlib-1.2.3-29.el6.x86_64.rpm
    • libidn-1.18-2.el6.x86_64.rpm
    • libcap-2.16-5.5.el6.x86_64.rpm
    • libattr-2.4.44-7.el6.x86_64.rpm
    • libstdc++-4.4.4-13.el6.x86_64.rpm
    • elfutils-libelf-devel-0.152-1.el6.x86_64.rpm
    • elfutils-libelf-devel-static-0.152-1.el6.x86_64.rpm
    • libaio-devel-0.3.107-10.el6.x86_64.rpm
    • libgcc-4.4.7-3.el6.x86_64.rpm
    • libstdc++-devel-4.4.6-4.el6.x86_64.rpm
    • gcc-4.4.6-4.el6.x86_64.rpm
    • glibc-devel-2.12-1.107.el6.x86_64.rpm
    • glibc-headers-2.12-1.107.el6.x86_64.rpm
    • kernel-headers-2.6.32-279.el6.x86_64.rpm
    • glibc-2.12-1.107.el6.x86_64.rpm
    • glibc-common-2.12-1.107.el6.x86_64.rpm
    • gcc-c++-4.4.6-4.el6.x86_64.rpm
    • sysstat-9.0.4-20.el6.x86_64.rpm
    • compat-libstdc++-33-3.2.3-69.el6.x86_64.rpm
    • compat-libtermcap-2.0.8-49.el6.x86_64.rpm
    • Linux-PAM (Pluggable Authentication Modules for Linux) RPM
  3. To ensure that the BMC Remedy AR System services start, install the compat-libstdc++-33-3.2.3-69.el6.i686.rpm RPM package.
  4. To ensure that the RSCD Agent installs properly, install the libtermcap-2.0.8-49.el6.x86_64.rpm package.
  5. From the /usr/lib folder, verify that the libstdc++.so.5 library exists. Install the library if it does not exist.

  6. Start the rpcbind process with the -i option on Cloud Portal and Database host before installing to avoid install failures:

    # service rpcbind stop
    # rpcbind -i
    # service rpcbind status

  7. To verify whether the RPM is installed, enter the following command:

    rpm -ql package
    rpm -ql compat-libstdc++-33-3.2.3-69.el6.i686.rpm

Failed to execute the [export-ignore] macro.

To set the minimum JVM heap size

For optimal performance, set the minimum JVM heap size to 1024 MB. Otherwise, the install planner might hang.

Failed to execute the [export-ignore] macro.

Linux supporting product requirements

The following sections list the hardware and software requirements, and the tasks that you must perform before you install the BMC Cloud Lifecycle Management solution on Linux. For more information about product-specific hardware requirements per deployment type, see deployment architecture and sizing guidelines.

Requirements for installing all Linux product hosts

  1. On each product host:
    1. Open /etc/services.

    2. Comment out the following entries:

      #ssad   4750/tcp    # Simple Service Auto Discovery
      #ssad   4750/udp    # Simple Service Auto Discovery
    3. Save the file and reboot the host.
  2. Synchronize the same system time on the install planner host and all the product hosts, for example, Pacific Standard Time. 

BMC Remedy product requirements

The following section lists the product-specific requirements for the BMC Remedy products.

BMC AR System Server – Cloud Portal and Database – Primary

Hardware and software requirements:

  • 2 CPUs
  • 8 GB RAM
  • Hard disk space: 
    • Installation directory: 10526 MB 
    • Temp (tmp) directory: 10 GB
  • Red Hat Linux 6.x (64-bit) or Red Hat Linux 5.x (64-bit)
  • Oracle JRE 1.7 (64-bit)
  • For local and remote databases: Oracle 11g R2 64-bit database
  • For remote databases: Oracle 11g R2 64-bit client with Administrator installation type (ensure that the installation includes oracle utilities such as imp).
  • Review the required list of packages to install this product.

Start rpcbind in insecure mode:

#service rpcbind stop
#rpcbind -i

Failed to execute the [export-ignore] macro.

BMC Remedy Mid Tier

Hardware and software requirements:

  • 2 CPUs
  • 4 GB RAM
  • Hard disk space: 
    • Installation directory: 360 MB 
    • Temp (tmp) directory: 2609 MB
  • Red Hat Linux 6.x (64-bit) or Red Hat Linux 5.x (64-bit)
  • Oracle JRE 1.7 (64-bit)

Product-specific requirements: Set the PATH environment variable on the mid tier host to jrePath/bin. 

Failed to execute the [export-ignore] macro.

BMC AR System Server – Cloud Portal and Database – Secondary

Hardware and software requirements:

  • 2 CPUs
  • 4 GB RAM
  • Hard disk space: 
    • Installation directory: 10526 MB 
    • Temp (tmp) directory: 9064 MB
  • Red Hat Linux 6.x (64-bit) or Red Hat Linux 5.x (64-bit)
  • Oracle JRE 1.7 (64-bit)
  • For local and remote databases: Oracle 11g R2 64-bit database (shares the database with BMC Remedy AR System & IT Service Mgt. Suite - Primary)
  • For remote databases: Oracle 11g R2 64-bit client with Administrator installation type (ensure that the installation includes oracle utilities, for example, imp).
  • Review the required list of packages to install this product.

Failed to execute the [export-ignore] macro.

BMC Atrium Core Web Registry requirements

Hardware and software requirements:

  • 2 CPUs
  • 6 GB RAM
  • Hard disk space: 
    • Installation directory: 1345 MB 
    • Temp (tmp) directory: 5223 MB
  • Red Hat Linux 6.x (64-bit) or Red Hat Linux 5.x (64-bit)
  • Oracle JRE 1.7 (64-bit)
  • Review the required list of packages to install this product.

Failed to execute the [export-ignore] macro.

BMC Server Automation product requirements

The following section lists the product-specific requirements for the BMC Server Automation components.

BMC Server Automation – Application Server & Console

Hardware and software requirements:

  • 2 CPUs
  • 8 GB RAM
  • Hard disk space: 
    • Installation directory: 745 MB 
    • Temp (tmp) directory: 1626 MB
  • Red Hat Linux 6.x (64-bit) or Red Hat Linux 5.x (64-bit)
  • For local and remote databases: Oracle 11g R2 64-bit database
  • Review the required list of packages to install this product.

Product-specific requirements: 

  • Before you begin installing BMC Server Automation – Application Server & Console, ensure that port 9700 is available on the host on which you want to install the product.
    To free up port 9700 on Linux, perform the following steps:
    1. Open the /etc/services file.

    2. Comment out the entries that use port 9700, for example, board-roar.

      board-roar      9700/tcp                # Board M.I.T. Service
      board-roar      9700/udp                # Board M.I.T. Service
    3. Reboot the VM.
    4. After the reboot is finished, start the Oracle database and the BladeLogic Application Server.
    5. To verify that the Application Server is running, launch the BMC Server Automation Console and log on to the server.
      If you can successfully log on, the BladeLogic Application Server is running. 
    6. Close the BMC Server Automation Console.
  • Ensure that the libtermcap.so.2 RPM package is installed.

 

Failed to execute the [export-ignore] macro.

(Optional) PXE Server

Hardware and software requirements:

  • Red Hat Linux 6.x (64-bit) or Red Hat Linux 5.x (64-bit)
  • 2 CPUs
  • 4 GB RAM
  • Hard disk space: 
    • Installation directory: 46 MB 
    • Temp (tmp) directory: 1626 MB

Product-specific requirements: Ensure that the libtermcap.so.2 RPM package is installed.

(Optional) BMC Server Automation – Advanced Repeater

Hardware and software requirements:

  • Red Hat Linux 6.x (64-bit) or Red Hat Linux 5.x (64-bit)
  • 2 CPUs
  • 1 GB RAM
  • Hard disk space: 
    • Installation directory: 265 MB 
    • Temp (tmp) directory: 391 MB

Product-specific requirements: 

  • Ensure that the following rpm packages are installed:
    • libXp.i386
    • libXp.x86_64
    • libXcursor.i386
    • libXcursor.x86_64
    • libXfixes.i386
    • libXfixes.x86_64
    • libXi.i386
    • libXi.x86_64
    • libXpm.i386
    • libXpm.x86_64
    • xorg-x11-server-utils.x86_64
    • libXi.i386

BMC Server Automation – Multiple Application Server (MAS)

Hardware and software requirements:

  • Red Hat Linux 6.x (64-bit) or Red Hat Linux 5.x (64-bit)
  • For local and remote databases: Oracle 11g R2 64-bit database (shares the database with BMC Server Automation Application Server & Console)
  • 2 CPUs
  • 8 GB RAM
  • Hard disk space: 
    • Installation directory: 9 GB 
    • Temp (tmp) directory: 3 GB

Product-specific requirements: 

  • Before you begin installing BMC Server Automation – Application Server & Console, ensure that port 9700 is available on the host on which you want to install the product.
  • Ensure that the libtermcap.so.2 RPM package is installed.

(Optional) BMC Server Automation – File Server

Hardware and software requirements:

  • Red Hat Linux 6.x (64-bit) or Red Hat Linux 5.x (64-bit)
  • 2 CPUs
  • 8 GB RAM
  • Hard disk space: 
    • Installation directory:  50 MB 
    • Temp (tmp) directory:  1 GB

Note

You require additional hard disk space for storage on the File Server.

BMC Server Automation – Remote System Call Daemon (RSCD) Agent

Hardware and software requirements:

  • 2 CPUs
  • 8 GB RAM
  • Hard disk space: Install directory: 100 MB
  • Red Hat Linux 6.x (64-bit) or Red Hat Linux 5.x (64-bit)

Failed to execute the [export-ignore] macro.

BMC Atrium Orchestrator product requirements

The following section lists the product-specific requirements for the BMC Atrium Orchestrator components.

BMC Atrium Orchestrator – Configuration Distribution Peer

Hardware and software requirements:

  • Red Hat Linux 6.x (64-bit) or Red Hat Linux 5.x (64-bit)
  • For local and remote databases: Oracle 11g R2 64-bit database
  • 2 CPUs
  • 2 GB RAM
  • Hard disk space: 
    • Installation directory: 590 MB 
    • Temp (tmp) directory: 3598 MB

Product-specific requirements:

  • Install the BMC Atrium Orchestrator Development Studio client so that you can export the IP Address Management (IPAM) modules to the BMC Atrium Orchestrator grid.  For more information, see Installing BMC Atrium Orchestrator Development Studio.
  • Ensure that the libtermcap.so.2 RPM package is installed.

BMC Atrium Orchestrator – Configuration Distribution Peer (HA)

Hardware and software requirements:

  • Red Hat Linux 6.x (64-bit) or Red Hat Linux 5.x (64-bit)
  • For local and remote databases: Oracle 11g R2 64-bit database
  • 2 CPUs
  • 4 GB RAM
  • Hard disk space: 
    • Installation directory: 590 MB 
    • Temp (tmp) directory: 3598 MB

Product-specific requirements:

  • Install the BMC Atrium Orchestrator Development Studio client so that you can export the IP Address Management (IPAM) modules to the BMC Atrium Orchestrator grid. For more information, see Installing BMC Atrium Orchestrator Development Studio.
  •  Ensure that the libtermcap.so.2 RPM package is installed.

Failed to execute the [export-ignore] macro.

BMC Network Automation product requirements

The following section lists the product-specific requirements for the BMC Network Automation components.

BMC Network Automation

Hardware and software requirements:

  • 2 CPUs
  • 4 GB RAM
  • Hard disk space: 
    • Installation directory: 1245 MB 
    • Temp (tmp) directory: 997 MB
  • Red Hat Linux 6.x (64-bit) or Red Hat Linux 5.x (64-bit)
  • For local and remote databases: Oracle 11g R2 64-bit database
  • Review the required list of packages to install this product.

BMC Network Automation – Device Agent

Hardware and software requirements:

  • 2 CPUs
  • 4 GB RAM
  • Hard disk space: 
    • Installation directory: 2093 MB 
    • Temp (tmp) directory: 770 MB
  • Red Hat Linux 6.x (64-bit) or Red Hat Linux 5.x (64-bit) 

Failed to execute the [export-ignore] macro.

BMC Cloud Lifecycle Management product requirements

The following section lists the product-specific requirements for the BMC Cloud Lifecycle Management components.

Cloud Database Extensions

Hardware and software requirements:  

  • Hard disk space:
    •  Installation directory: 521 MB 
    • Temp (tmp) directory: 1933 MB
  • Install the Cloud Database Extensions on the same host as BMC Remedy AR System - Cloud Database.
  • Red Hat Linux 6.x (64-bit) or Red Hat Linux 5.x (64-bit)

Failed to execute the [export-ignore] macro.

Cloud Platform Manager

Hardware and software requirements:

  • 2 CPUs
  • 8 GB RAM
  • Hard disk space: 
    • Installation directory: 521 MB 
    • Temp (tmp) directory: 1933 MB
  • Red Hat Linux 6.x (64-bit) or Red Hat Linux 5.x (64-bit)

Failed to execute the [export-ignore] macro.

Cloud Portal AR Extensions – Primary

Hardware and software requirements: 

  • Hard disk space:  
    • Installation directory: 521 MB 
    • Temp (tmp) directory: 1933 MB
  • Install the Cloud Portal AR Extensions on the same host as BMC AR System Server – Cloud Portal and Database – Primary.
  • Red Hat Linux 6.x (64-bit) 

Failed to execute the [export-ignore] macro.

Cloud Portal AR Extensions – Secondary

Hardware and software requirements: 

  • Hard disk space:  
    • Installation directory: 521 MB  
    • Temp (tmp) directory: 1933 MB
  • Install the Cloud Portal AR Extensions – Secondary on the same host as BMC AR System Server – Cloud Portal and Database – Secondary.
  • Red Hat Linux 6.x (64-bit)

Failed to execute the [export-ignore] macro.

Oracle database requirements for Linux

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

Database requirements overview

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. 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 section explains the database requirements for the following products:

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

Supported Oracle database version

The BMC Cloud Lifecycle Management solution supports Oracle Database 11g R2 64-bit on the Red Hat Enterprise Linux 6.x or 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.

Failed to execute the [export-ignore] macro.

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*