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.  

Note

BMC Cloud Lifecycle Management 4.6.00.001 and later versions support Red Hat Enterprise Linux 7.6 or earlier (64-bit).

Linux installer host requirements

Before you launch the BMC Cloud Lifecycle Management installer, make sure 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)
  • Red Hat Enterprise Linux 7.6 or earlier (64-bit)
  • Oracle/Zulu JRE 1.8 (64-bit)

  • Minimum 1 GB free hard-disk space for the installation directory
  • Minimum 30 GB free hard-disk space for storing installation applications
  • 8 vCPU
  • Minimum 8 GB RAM during installation
You need root user credentials to perform all the installation

Back to top

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.

ComponentPort numberDescription
BMC Cloud Lifecycle Management installation program12333, 9998, 22

Installer ports

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

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 12433 or 9998 (for BladeLogic Server Automation), 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.

SSH port 22 is required for the installer to authenticate credentials of target host as well as the SCP connection for RSCD installer copy.

BMC AR System Server - Cloud Portal and Database - Primary0 (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

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


Back to top

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
      #board-roar 9700/tcp # Board M.I.T. Service
      #board-roar 9700/tcp # Board M.I.T. Service
    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. 

  3. Ensure that you have execute permission on the default /tmp directory. 

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: 15 GB 
    • Temp (tmp) directory: 10 GB
  • Red Hat Enterprise Linux 7.6 or earlier (64-bit) or Red Hat Enterprise Linux 6.x (64-bit) or Red Hat Enterprise Linux 5.x (64-bit)
  • Oracle/Zulu JRE 1.8 (64-bit)
  • For local and remote databases: Oracle 11g R2 or Oracle 12c + patch 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. For more information about starting the rpcbind process for Red Hat Enterprise Linux, see Preparing to run the installer on a Linux computer.

Back to top

BMC Remedy Mid Tier

Hardware and software requirements:

  • 2 CPUs
  • 4 GB RAM
  • Hard disk space: 
    • Installation directory: 9 GB 
    • Temp (tmp) directory: 9 GB
  • Red Hat Enterprise Linux 7.6 or earlier (64-bit) or Red Hat Enterprise Linux 6.x (64-bit) or Red Hat Enterprise Linux 5.x (64-bit)
  • Oracle/Zulu JRE 1.8 (64-bit)

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

Back to top

BMC AR System Server – Cloud Portal and Database – Secondary

Hardware and software requirements:

  • 2 CPUs
  • 4 GB RAM
  • Hard disk space: 
    • Installation directory: 15 GB 
    • Temp (tmp) directory: 10 GB
  • Red Hat Enterprise Linux 7.6 or earlier (64-bit) or Red Hat Enterprise Linux 6.x (64-bit) or Red Hat Enterprise Linux 5.x (64-bit)
  • Oracle/Zulu JRE 1.8 (64-bit)
  • For local and remote databases: Oracle 11g R2 or Oracle 12c + patch 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.

Back to top

BMC Atrium Core Web Registry requirements

Hardware and software requirements:

  • 2 CPUs
  • 6 GB RAM
  • Hard disk space: 
    • Installation directory: 9 GB 
    • Temp (tmp) directory: 9 GB
  • Red Hat Enterprise Linux 7.6 or earlier (64-bit) or Red Hat Enterprise Linux 6.x (64-bit) or Red Hat Enterprise Linux 5.x (64-bit)
  • Oracle/Zulu JRE 1.8 (64-bit)
  • Review the required list of packages to install this product.

Back to top

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: 6 GB 
    • Temp (tmp) directory: 6 GB
  • Red Hat Enterprise Linux 7.6 or earlier (64-bit) or Red Hat Enterprise Linux 6.x (64-bit) or Red Hat Enterprise Linux 5.x (64-bit)
  • For local and remote databases: Oracle 11g R2 or Oracle 12c + patch 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.

Back to top

(Optional) PXE Server

Hardware and software requirements:

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

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 Enterprise Linux 7.6 or earlier (64-bit) or Red Hat Enterprise Linux 6.x (64-bit) or Red Hat Enterprise Linux 5.x (64-bit)
  • 2 CPUs
  • 1 GB RAM
  • Hard disk space: 
    • Installation directory: 5 GB 
    • Temp (tmp) directory: 5 GB

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 Enterprise Linux 7.6 or earlier (64-bit) or Red Hat Enterprise Linux 6.x (64-bit) or Red Hat Enterprise Linux 5.x (64-bit)
  • For local and remote databases: Oracle 11g R2 or Oracle 12c + patch 64-bit database (shares the database with BMC Server Automation Application Server & Console)
  • 2 CPUs
  • 8 GB RAM
  • Hard disk space: 
    • Installation directory: 6 GB 
    • Temp (tmp) directory: 6 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 Enterprise Linux 7.6 or earlier (64-bit) or Red Hat Enterprise Linux 6.x (64-bit) or Red Hat Enterprise Linux 5.x (64-bit)
  • 2 CPUs
  • 8 GB RAM
  • Hard disk space: 
    • Installation directory: 6 GB 
    • Temp (tmp) directory: 6 GB

Note

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

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 Enterprise Linux 7.6 or earlier (64-bit) or Red Hat Enterprise Linux 6.x (64-bit) or Red Hat Enterprise Linux 5.x (64-bit)
  • For local and remote databases: Oracle 11g R2 or Oracle 12c + patch 64-bit database
  • 2 CPUs
  • 2 GB RAM
  • Hard disk space: 
    • Installation directory: 5 GB 
    • Temp (tmp) directory: 10 GB

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 Enterprise Linux 7.6 or earlier (64-bit) or Red Hat Enterprise Linux 6.x (64-bit) or Red Hat Enterprise Linux 5.x (64-bit)
  • For local and remote databases: Oracle 11g R2 or Oracle 12c + patch 64-bit database
  • 2 CPUs
  • 4 GB RAM
  • Hard disk space: 
    • Installation directory: 5 GB 
    • Temp (tmp) directory: 10 GB

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.

Back to top

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: 4 GB 
    • Temp (tmp) directory: 6 GB
  • Red Hat Enterprise Linux 7.6 or earlier (64-bit) or Red Hat Enterprise Linux 6.x (64-bit) or Red Hat Enterprise Linux 5.x (64-bit)
  • For local and remote databases: Oracle 11g R2 or Oracle 12c + patch 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: 5 GB 
    • Temp (tmp) directory: 5 GB
  • Red Hat Enterprise Linux 7.6 or earlier (64-bit) or Red Hat Enterprise Linux 6.x (64-bit) or Red Hat Enterprise Linux 5.x (64-bit)

Back to top

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:  

  • Install the Cloud Database Extensions on the same host as BMC Remedy AR System - Cloud Database.
  • Red Hat Enterprise Linux 7.6 or earlier (64-bit) or Red Hat Enterprise Linux 6.x (64-bit) or Red Hat Enterprise Linux 5.x (64-bit)

Back to top

Cloud Platform Manager 

Hardware and software requirements:

  • 2 CPUs
  • 8 GB RAM
  • Hard disk space: 
    • Installation directory: 5 GB 
    • Temp (tmp) directory: 5 GB
  • Red Hat Enterprise Linux 7.6 or earlier (64-bit) or Red Hat Enterprise Linux 6.x (64-bit) or Red Hat Enterprise Linux 5.x (64-bit)
  • Oracle/Zulu JRE 1.8 (64-bit)

Back to top

Cloud Portal AR Extensions – Primary

Hardware and software requirements: 

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

Back to top

Cloud Portal AR Extensions – Secondary

Hardware and software requirements: 

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

Back to top

CLM Self-Check Monitor (Optional)

Hardware and software requirements:

  • 2 CPUs
  • 4 GB RAM
  • Hard disk space: 
    • Installation directory: 5 GB 
    • Temp (tmp) directory: 5 GB
  • Red Hat Enterprise Linux 7.6 or earlier (64-bit) or Red Hat Enterprise Linux 6.x (64-bit) or Red Hat Enterprise Linux 5.x (64-bit)
  • Oracle/Zulu JRE 1.8 (64-bit)

Product-specific requirements: Set the PATH environment variable on the CLM Self-Check Monitor host to jrePath/bin.

Back to top

Cloud Portal Web Application (Optional)

Hardware and software requirements:

  • 2 CPUs
  • 4 GB RAM
  • Hard disk space: 
    • Installation directory: 5 GB 
    • Temp (tmp) directory: 5 GB
  • Red Hat Enterprise Linux 7.6 or earlier (64-bit) or Red Hat Enterprise Linux 6.x (64-bit) or Red Hat Enterprise Linux 5.x (64-bit)
  • Oracle/Zulu JRE 1.8 (64-bit)

Product-specific requirements: Set the PATH environment variable on the Cloud Portal Web Application host to jrePath/bin

Back to top

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 or Oracle 12c + patch 64-bit on the Red Hat Enterprise Linux 7.x, 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 Enterprise Linux 7.x

  • unixODBC-devel-2.3.1-11.el7.x86_64
  • unixODBC-devel-2.3.1-11.el7.i686.rpm
  • unixODBC-2.3.1-11.el7.x86_64
  • unixODBC-2.3.1-11.el7.i686
  • glibc-devel-2.17-196.el7.x86_64
  • glibc-devel-2.17-196.el7.i686
  • compat-libstdc++-33-3.2.3-72.el7.x86_64
  • compat-libstdc++-33-3.2.3-72.el7.i686
  • libgcc-4.8.5-16.el7.x86_64
  • libgcc-4.8.5-16.el7.i686
  • bc-1.06.95-13.el7.x86_64

Packages required for Red Hat Enterprise 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
  • bc-1.06.95-1.el6.x86_64

Packages required for Red Hat Enterprise 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
  • bc-1.06-21

All the packages listed are required for an Oracle client.

Environment variables

Make sure that you properly set the following Oracle environment variables in /root/.bash_profile:

  • ORACLE_HOME
  • ORACLE_SID
  • TWO_TASK

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 pre-created tablespace or allow the installer to create a tablespace for a given product, if the product supports it, during the installation. 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 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 pre-created tablespace is supported. However, you can 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 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 pre-created 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 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.


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.

Product

Oracle requirements for Linux

Additional information

BMC AR System Server - Cloud Portal and Database

  • Data tablespace: 7000 MB
  • Temp tablespace: 1024 MB
  • Redo log file size: 500 MB minimum, 1 GB recommended
  •  Pre-create tablespace support: Yes, but optional

    Note: When you pre-create the tablespace, specify the tablespace name as ARSystem.

BMC Server Automation

  • Data tablespace: 200 MB
  • Index tablespace: 50 MB (The database's temp tablespace will be set to its default value.)
  • Precreate tablespace support: Yes, but optional (Precreate data and temp tablespaces, create the user, and run the provided schema script.)
  • The system user and password are required to create the necessary tablespace and user.
  • On Oracle, edit the init.ora file to set the following initialization parameters: 
    • db_block_size = 8192
    • processes > or = 20*
  • For more information about how to pre-create a database, see setting up an Oracle database for BMC Server Automation.
  • Oracle RAC clustering is supported for BMC Server Automation.

BMC Network Automation

  • Data tablespace: 500 MB (The database's temp tablespace will be set to its default value.)
  • Precreate tablespace support: Yes, optional (Create user with default and temp tablespaces.)
  • The system user and password are required to create the necessary tablespace and user. The installer prompts you for inputs to create the database user and tablespace during the BMC Network Automation installation. However, you can also optionally precreate user and tablespace information.  
  • For more information about creating tablespace and user, see (Optional) Setting up BMC Network Automation on Linux.

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.

Back to top

Where to go from here

End-to-end installation flow

Was this page helpful? Yes No Submitting... Thank you

Comments