Control-M Full Installation System Requirements

Before you install Control-M, verify that your operating system, processor, and database server are supported and have the correct amount of memory and disk space. For a full list of requirements, see the Control-M 9.0.21.100 Release Notes.

Depending on your operating system, verify that your system meets one of the following requirements:

Full Installation UNIX System Requirements
Full Installation Windows System Requirements

The number of processes limit must be equal to or greater than the number of expected parallel running jobs.

Full Installation UNIX System Requirements

The following table lists the prerequisite requirements for a UNIX platform. These values represent the minimum requirements for an entry level deployment. For higher capacity workloads, add resources.

Resource	Specification	Requirement
Compatible Processors	AIX	IBM RISC System/6000 (RS/6000)
Compatible Processors	Linux	x86_64
Memory	N/A	24 GB (minimum)
Disk Space	N/A	100 GB If you are installing Control-M with a remote database server, 15 GB must be free on the database server. BMC Software recommends that you reserve 1.5 times the amount of host memory in disk swap space. For example, a host with 24 GB of memory requires 36 GB of disk space.
CPU	4 vCPU	100 SPEC rating (2006_int_rate) 30 rPef (AIX only)

Full Installation Windows System Requirements

The following table lists the prerequisite requirements for a Windows platform. These values represent the minimum requirements for an entry level deployment. For higher capacity workloads, add resources.

Resource	Requirement
CPU	Intel Xeon 64-bit AMD Opteron
Compatible Processors	x86_64
Display	16-bit (65,536) colors or higher
Memory	24 GB
Disk Space	100 GB If you are installing Control-M with a remote database server, 15 GB must be free on the database server. BMC Software recommends that you reserve 1.5 times the amount of host memory in disk swap space. For example, a host with 24 GB of memory requires 36 GB of disk space.
Related Software	Google Chrome or Microsoft Edge Microsoft .NET Framework 4.7.2.
CPU	4 vCPU 100 SPEC rating (2006_int_rate) The <install folder> must have Read, List folder contents, Write, and Read & execute permissions assigned to the Users group.

Database Server Requirements

The following table lists the database server options for the Control-M full installation.

You might experience performance degradation when the following occurs:

Too heavy of a workload is placed on too few hard disks.
Redo Log files are saved on RAID-5 disks.
Rollback tablespace is saved on RAID-5 disks.

For more information, see 000105549.

Database Server	Description	Version
PostgreSQL (BMC-Supplied)	Installs automatically in the background when you install Control-M. During an upgrade, the PostgreSQL database server version is not updated.	11.5
PostgreSQL (Existing)	A customer-supplied existing PostgreSQL full database server must be present (non-BMC source). The database server must have the following two extensions: plpgsql dblink OS authenticated logins to the database are not supported. An External PostgreSQL database is supported only if it is compatible with the Open Source PostgreSQL. The database must be configured to use user-password authentication. Trust authentication is not supported. The external PostgreSQL server must be configured to password based connectivity. The $PGDATA/pg_hba.conf file can have a line such as: host all all 0.0.0.0/0 password	11.x 12.x 13.x 14.x
Oracle	A customer-supplied existing Oracle full Enterprise or Standard Edition database server must be present. An Oracle instant client is supplied in the background when you install Control-M. Control-M/EM and Control-M/Server supports only a single address in the tnsnames.ora file in any Oracle configuration including RAC and Data Guard. For more details, see Oracle Database Server Requirements.	19c
MSSQL	A customer-supplied existing MSSQL full database server must be present. The following must be present on any computer that hosts Control-M/EM or Control-M/Server: Microsoft ODBC Driver 17 for SQL Server. Microsoft Command Line Utilities 15 for SQL Server. Microsoft SQL Server 2012 Native Client. You must use an MSSQL server SA account to perform the installation. Installation with a Windows User is not supported. Control-M installation with MSSQL must always be performed using an existing English language MSSQL database server. If you want to have the database built with a different collate than the standard Latin1 or CJK, you need to define the CTM_FORCE_COLLATE environment variable such as Chinese_Taiwan_Stroke_CI_AS or HEBREW_Bin.	2022 2019 2017 2016 2014 SP3 (Windows 2016 and lower)

The following table contains the parameter information required to install Control-M on supported existing database servers. Check with your system Administrator for the exact information required.

Database Server	Host Name	Port	Service Name	Database Server Administrator Password	Database Location	Log Location
PostgreSQL	Yes	Yes		Yes	(UNIX/Linux) Yes
Oracle	Yes	Yes	Yes	Optional	Yes
MSSQL	Yes		Yes	Yes	Yes	Yes

PostgreSQL: If you need to enable CJK, the default Control-M PostgreSQL client encoding is UTF8. Ensure the template_utf Database with UTF8 encoding is present in your existing PostgreSQL server. If you do not need to enable CJK, the default Control-M PostgreSQL client encoding is LATIN1. Ensure the template1 Database with LATIN1 encoding is present in your existing PostgreSQL server. For more information, see 000380214.
PostgreSQL and MSSQL: The username and password must begin with a letter (A–Z, a–z) followed by 5–29 alphanumeric characters and _ (underscores).
Oracle: The username and password must begin with a letter (A–Z, a–z) followed by 5–29 alphanumeric characters and _ (underscores).

Optimizing Database Performance

This procedure describes how to optimize the Control-M/EM and Control-M/Server databases. You might need to perform this procedure if your databases have a high transaction rate and high job count.

Begin

Verify that the Oracle or PostgreSQL database is installed on a dedicated computer that does not have the UNIX SWAP file.
Assign the Redo Log, WAL, and Transaction logs to a separate disk drive.
Verify that the Redo Log, WAL, and Transactions log file is not using a RAID-5 disk (No RAID. RAID 0, RAID 0+1, RAID 10 are OK).
Assign the Rollback tablespace Log to a separate disk drive.
Verify that the Rollback tablespace file is not using a RAID-5 disk (No RAID, RAID 0, RAID 0+1, or RAID 10 are OK).
Assign the Control Files Log to a separate disk drive.
Verify that the Control Files are not using a RAID-5 disk (No RAID, RAID 0, RAID 0+1, or RAID 10 are OK).