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 and host requirements

Click here to see the OS and hardware requirements for the installer host.

Operating system

Hardware

Permissions

  • Red Hat Enterprise Linux 5.x (64-bit)
  • Red Hat Enterprise Linux 6.x (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

Installer host port requirements

Click here to see the port requirements for the installer host.

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 table. The installer uses these ports to run commands to check application connectivity, database connections, RSCD connectivity, remote installation status, and so on. The port number in the table is the default value 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 port is enabled in the firewall.

Note

The Cloud Portal and Database System 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 post-installation, 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 post-installation 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

During the Cloud Portal and Database server installation using the BMC Cloud Lifecycle Management installer, the installer attempts to connect to the database using the user-supplied database port to ensure that the database is running. 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

During the BMC Server Automation installation using the BMC Cloud Lifecycle Management installer, the installer attempts to connect to the database using the user-supplied database port to ensure that the database is running. 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 is applicable for 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

During the BMC Network Automation installation using the BMC Cloud Lifecycle Management installer, the installer attempts to connect to the database using the user-supplied database port to ensure that the database is running . 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

During the PXE installation using the BMC Cloud Lifecycle Management installer, the installer attempts to connect to the database using the user-supplied database port to ensure that the database is running . 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.

For more information about the ports used by BMC Cloud Lifecycle Management, see Port mappings.

Preparing the installer host

Click here to see a list of the preparatory tasks you must complete for the installer host .

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

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.

Click here to review the steps.
  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>).
  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.

Failed to execute the [info] macro. Cause: [The required content is missing.]. Click on this message for details.

To update BMC Server Automation RSCD Agent and NSH to the required version

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.5 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:

Click here to review the steps.
  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..

To install packages on Linux 5.x computers

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

Note

Contact your Linux system administrator to check for these packages.

Click here for a list of packages to install on the installer host.
  • 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 if the RPM is installed, enter the following command:

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

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.

Click here to review the steps.
  1. Install the following 32-bit RPM packages:
    • unixODBC-devel-2.2.11-7.1
    • unixODBC-2.2.11-7.1
    • libX11-1.3-2.el6.i686.rpm
    • libXau-1.0.5-1.el6.i686.rpm
    • libxcb-1.5-1.el6.i686.rpm
    • libXext-1.1-3.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
    • libstdc++-4.4.4-13.el6.i686.rpm
    • openssl-1.0.0-4.el6.i686.rpm
    • libgssglue-0.1-8.1.el6.i686.rpm
    • krb5-libs-1.8.2-3.el6.i686.rpm
    • libcom_err-1.41.12-3.el6.i686.rpm
    • keyutils-libs-1.4-1.el6.i686.rpm
    • libselinux-2.0.94-2.el6.i686.rpm
    • zlib-1.2.3-25.el6.i686.rpm
    • libidn-1.18-2.el6.i686.rpm
    • libcap-2.16-5.2.el6.i686.rpm
    • libattr-2.4.44-4.el6.i686.rpm
    • Linux-PAM (Pluggable Authentication Modules for Linux) RPM
  2. Install the following 64-bit RPM packages:
    • elfutils-libelf-devel-0.137-3.el5
    • elfutils-libelf-devel-static-0.137-3.el5
    • libaio-devel-0.3.106-5
    • libgcc-4.1.2-50.el5
    • libstdc++-devel-4.1.2-50.el5
    • unixODBC-2.2.11-7.1
    • unixODBC-devel-2.2.11-7.1
    • gcc-4.1.2-50.el5.x86_64
    • glibc-devel-2.5-58.i386
    • glibc-devel-2.5-58.x86_64
    • glibc-headers-2.5-58.x86_64
    • kernel-headers-2.6.18-238.el5.x86_64
    • glibc-2.5-58.i686
    • glibc-2.5-58.x86_64
    • glibc-common-2.5-58.x86_64
    • gcc-c++-4.1.2-50.el5.x86_64
    • sysstat-7.0.2
    • compat-libstdc++-33-3.2.3-69.el6.i686.rpm
    • libstdc++.so.5 (under /usr/lib)
    • libtermcap.so.2
    • libstdc++-4.4.4-13.el6.i686.rpm
    • openssl-1.0.0-4.el6.i686.rpm
    • libgssglue-0.1-8.1.el6.i686.rpm
    • krb5-libs-1.8.2-3.el6.i686.rpm
    • libcom_err-1.41.12-3.el6.i686.rpm
    • keyutils-libs-1.4-1.el6.i686.rpm
    • libselinux-2.0.94-2.el6.i686.rpm
    • zlib-1.2.3-25.el6.i686.rpm
    • libidn-1.18-2.el6.i686.rpm
    • libcap-2.16-5.2.el6.i686.rpm
    • libattr-2.4.44-4.el6.i686.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 if the RPM is installed, enter the following command:

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

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. The requirements outlined in this topic are for a small deployment only. For more information about product-specific hardware requirements per deployment type, see deployment architecture and sizing guidelines.

BMC Remedy product requirements

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

Product or component

Requirements

BMC Remedy AR System & IT Service Management Suite – Primary

Click here to see the hardware, software, and product-specific requirements.

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.5 (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.

BMC Remedy AR System & IT Service Management Suite – Secondary

Click here to see the hardware, software, and product-specific requirements.

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.5 (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.

BMC Remedy Mid Tier

Click here to see the hardware, software, and product-specific requirements.

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.5 (64-bit)
  • Oracle JRE 1.7 (64-bit)

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

BMC Atrium Core Web Registry requirements

Click here to see the hardware, software, and product-specific requirements for the BMC Atrium Core Web Registry.

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) orRed Hat Linux 5.5 (64-bit)
  • Oracle JRE 1.7 (64-bit)
  • Review the required list of packages to install this product.

BMC Server Automation product requirements

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

Product or component

Requirements

BMC Server Automation – Application Server & Console

Click here to see the hardware, software, and product-specific requirements.

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.5 (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.
  • Ensure that the libtermcap.so.2 RPM package is installed.

BMC Server Automation – Multiple Application Server (MAS)

Click here to see the hardware, software, and product-specific requirements.

Hardware and software requirements:

  • Red Hat Linux 6.x (64-bit) or Red Hat Linux 5.5 (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.

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

Click here to see the hardware, software, and product-specific requirements.

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.5 (64-bit)

BMC Server Automation – Advanced Repeater (Optional)

Click here to see the hardware, software, and product-specific requirements.

Hardware and software requirements:

  • Red Hat Linux 6.x (64-bit) or Red Hat Linux 5.5 (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

PXE Server (Optional

Click here to see the hardware, software, and product-specific requirements.

Hardware and software requirements:

  • Red Hat Linux 6.x (64-bit) or Red Hat Linux 5.5 (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.

BMC Server Automation – File Server (Optional)

Click here to see the hardware, software, and product-specific requirements.

Hardware and software requirements:

  • Red Hat Linux 6.x (64-bit) or Red Hat Linux 5.5 (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 Atrium Orchestrator product requirements

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

Product or component

Requirements

BMC Atrium Orchestrator – Configuration Distribution Peer

Click here to see the hardware, software, and product-specific requirements.

Hardware and software requirements:

  • Red Hat Linux 5.5 (64-bit)
  • 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)

Click here to see the hardware, software, and product-specific requirements.

Hardware and software requirements:

  • 2 CPUs
  • 4 GB RAM
  • Hard disk space: 
    • Installation directory: 590 MB 
    • Temp (tmp) directory: 3598 MB
  • Red Hat Linux 5.5 (64-bit)
  • Msvcr71.dll

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 Network Automation product requirements

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

Product or component

Requirements

BMC Network Automation

Click here to see the hardware, software, and product-specific requirements.

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.5 (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

Click here to see the hardware, software, and product-specific requirements.

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.5 (64-bit)

BMC Cloud Lifecycle Management product requirements

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

Product or component

Requirements

Cloud Database Extensions

Click here to see the hardware, software, and product-specific requirements.

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.5 (64-bit)

Cloud Platform Manager 

Click here to see the hardware, software, and product-specific requirements.

Hardware and software requirements:

  • 2 CPUs
  • 4 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.5 (64-bit)

Cloud Portal AR Extensions – Primary 

Click here to see the hardware, software, and product-specific requirements.

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) 

Cloud Portal AR Extensions – Secondary 

Click here to see the hardware, software, and product-specific requirements.

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)

Database requirements for Linux

This section outlines the database requirements for Linux platforms.

Requirements common to database platforms

This section outlines the requirements that are common to Microsoft SQL Server and Oracle.

Supported database versions

The BMC Cloud Lifecycle Management solution supports the following databases:

  • Microsoft SQL Server 2008 R2 Enterprise 64-bit (if you require Cluster capabilities) on Microsoft Windows 2008 R2 64-bit OS.
    Otherwise, you can use Microsoft SQL Server 2008 R2 Standard 64-bit for single installations.

    Tip

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

  • Oracle Database 11g 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 <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.
  • 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 precreate options, tablespace requirements, and database requirements. The BMC Cloud Lifecycle Management solution supports Oracle Database 11g R2 64-bit on the Red Hat Enterprise Linux 5.5 64-bit OS.

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 libgcc_s.so.1

Packages required for Red Hat Linux 5.5

  • 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)
  • gcc-4.1.2-50.el5.x86_64
  • glibc-devel-2.5-58.i386
  • glibc-devel-2.5-58.x86_64
  • glibc-headers-2.5-58.x86_64
  • kernel-headers-2.6.18-238.el5.x86_64
  • glibc-2.5-58.i686
  • glibc-2.5-58.x86_64
  • gcc-c++-4.1.2-50.el5.x86_64
  • libstdc++.so.5 libgcc_s.so.1
  • sysstat-7.0.2

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 4.0 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; 

 

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