Control-M Database Server Upgrade

After you upgrade Control-M/EM or Control-M/Server to 9.0.22, you must upgrade the dedicated BMC-supplied PostgreSQL database or your external PostgreSQL, Oracle, or MSSQL database to one of the supported versions described in Database Upgrade Scenarios.

If you are connected to a dedicated BMC-supplied PostgreSQL database, the Control-M component upgrade does not affect the database operating system, and you must also upgrade the dedicated database to PostgreSQL 11.5 or 15.3.

The following procedures describe the database server upgrade process:

Database Upgrade Scenarios

The following table lists the supported upgrade options to upgrade to 9.0.22 based on your database and version.

Database

Source Database Version

Upgrade Action Steps

PostgreSQL (Dedicated BMC-Supplied)

9.5.5

  1. Upgrade to Control-M 9.0.20.

  2. Upgrade to PostgreSQL 11.5.

  3. Upgrade to Control-M 9.0.22.

  4. (Recommended) Upgrade to PostgreSQL 15.3.

PostgreSQL (Dedicated BMC-Supplied)

10.4

  1. Upgrade to Control-M 9.0.20.

  2. Upgrade to PostgreSQL 11.5.

    On AIX, you cannot upgrade to PostgreSQL 11.5. However, you can convert the BMC-provided PostgreSQL database to an external PostgreSQL database and upgrade to one of the supported versions, as listed in the Product Availability and Compatibility.

  3. Upgrade to Control-M 9.0.22.

  4. (Recommended) Upgrade to PostgreSQL 15.3.

PostgreSQL (Dedicated BMC-Supplied)

11.5

  1. Upgrade to Control-M 9.0.22.

  2. (Recommended) Upgrade to PostgreSQL 15.3.

Oracle

  • 11.x

  • 12.x

  • 18.x

  1. Upgrade to Control-M 9.0.20.

  2. Upgrade to Oracle 19.x.

  3. Upgrade to Control-M 9.0.22.
Oracle

19.x

Upgrade to Control-M 9.0.22.

MSSQL

 

 

 

 

 

 

2008

Windows 2016:

  1. Upgrade to MSSQL 2014SP3-2019.

  2. Upgrade to Control-M 9.0.20.

  3. Upgrade to Control-M 9.0.22.

Windows 2019:

  1. Upgrade to MSSQL 2016-2019.

  2. Upgrade to Control-M 9.0.20.

  3. Upgrade to Control-M 9.0.22.

  4. (Optional) Upgrade to MSSQL 2022.

MSSQL

2012

Windows 2016:

  1. Upgrade to MSSQL 2014SP3-2019.

  2. Upgrade to Control-M 9.0.20.

  3. Upgrade to Control-M 9.0.22.

Windows 2019:

  1. Upgrade to MSSQL 2016-2019.

  2. Upgrade to Control-M 9.0.20.

  3. Upgrade to Control-M 9.0.22.

  4. (Optional) Upgrade to MSSQL 2022.

MSSQL

2014SP3

Windows 2016:

  1. Upgrade to Control-M 9.0.20.

  2. Upgrade to Control-M 9.0.22.

  3. (Optional) Upgrade to MSSQL 2016-2019.

Windows 2019:

  1. Upgrade to Control-M 9.0.20.

  2. Upgrade to MSSQL 2016-2019.

  3. Upgrade to Control-M 9.0.22.

  4. (Optional) Upgrade to MSSQL 2022.

MSSQL

2016

Windows 2016:

  1. Upgrade to Control-M 9.0.20.

  2. Upgrade to Control-M 9.0.22.

  3. (Optional) Upgrade to MSSQL 2017-2019.

Windows 2019:

  1. Upgrade to Control-M 9.0.20.

  2. Upgrade to Control-M 9.0.22.

  3. (Optional) Upgrade to MSSQL 2017-2022.

MSSQL

2017

Windows 2016:

  1. Upgrade to Control-M 9.0.22.

  2. (Optional) Upgrade to MSSQL 2019.

Windows 2019:

  1. Upgrade to Control-M 9.0.22.

  2. (Optional) Upgrade to MSSQL 2019-2022.

MSSQL

2019

  1. (Windows 2016 and 2019) Upgrade to Control-M 9.0.22.

  2. (Optional for Windows 2019) Upgrade to MSSQL 2022.

MSSQL

2022

Upgrade to Control-M 9.0.22.

PostgreSQL (Existing)

  • 9.x

  • 10.x

  1. Upgrade to Control-M 9.0.20.

  2. Upgrade to PostgreSQL 11.x-12.x.

  3. Upgrade to Control-M 9.0.22.

  4. (Recommended) Upgrade to PostgreSQL 15.3 or higher.

PostgreSQL (Existing)

  • 11.x

  • 12.x

  • 13.x

  • 14.x

  • 15.x

  1. Upgrade to Control-M 9.0.22.

  2. (Recommended) Upgrade to PostgreSQL 15.3 or higher.

PostgreSQL (Existing)

16.x

Upgrade to Control-M 9.0.22.

Upgrading the PostgreSQL Database Server

This procedure describes how to upgrade the PostgreSQL database server to the latest supported version.

  • If you upgrade Control-M/EM or Control-M/Server 9.0.20 or 9.0.21 to version 9.0.22 or higher, the PostgreSQL database server version (10.4 or 11.5) remains the same. However, if you perform a new installation of Control-M 9.0.21.200 or higher, the PostgreSQL version is 15.3.

  • After you upgrade the dedicated BMC-supplied PostgreSQL database server to PostgreSQL 15, you can no longer downgrade Control-M/EM or Control-M/Server to a version lower than version 9.0.21.200.

  • In a Control-M Full Installation, you only need to perform this procedure once, since the Control-M/EM and Control-M/Server share the same PostgreSQL database server.

  • In a High Availability environment, you must perform this procedure once on the primary node.

  • If you want to upgrade the Control-M Workload Archiving PostrgreSQL database, see Control-M Workload Archiving Installation.

Before You Begin

  • Verify that there is enough disk space to contain an additional PostgreSQL database server. You must make at least 25% more free disk space than is used by the <Control-M_Home>\pgsql directory. The upgrade fails when there is not enough space.

    If the current size of the pgsql directory is 1 GB, you must reserve at least 1.25 GB of free disk space for the upgrade.

  • Verify that Control-M/EM or Control-M/Server 9.0.21.200 or higher is installed.

  • Prepare for Control-M downtime. This upgrade requires some Control-M downtime, which depends on the database size. In most scenarios, the upgrade completes in 10 minutes. A large-scale environment might take up to an hour to upgrade.

Begin

  1. Click Control-M/Server for UNIX and Microsoft Windows to navigate to the EPD, then search for and download one of the following installation packages:

    • Control-M Version 9.0.22 - PostgreSQL in place Upgrade for Microsoft Windows

    • Control-M Version 9.0.22 - PostgreSQL in place Upgrade for Linux

    • Control-M Version 9.0.21.200 - PostgreSQL in place Upgrade for IBM AIX

  2. Copy the package to one of the following locations:

    • Full Installation and Control-M/Server on UNIX: $HOME

    • Control-M/EM on UNIX: $HOME/ctm_em/

    • Full Installation on Windows: <Control-M/Server Home>

    • Control-M/Server on Windows: <Control-M/Server Home>

    • Control-M/EM on Windows: <Control-M/EM Home>

  3. Do one of the following:

    • UNIX: Run the following commands to open and uncompress the upgrade package:

      1. gunzip pg_server_upgrade.tar.gz

      2. tar -xvf pg_server_upgrade.tar

    • Windows: Extract the pg_server_upgrade.tar.gz.

  4. Shut down the Control-M/EM or Control-M/Server components and verify that the processes are down.
    For a Full Installation, shut down both components.
    For a High Availability installation, shut down the primary and secondary components.

  5. Verify that the PostgreSQL database server is up and online.

  6. Navigate to the pg_server_upgrade directory and type one of the following:

    • UNIX: ./PG_Upgrade.sh

    • Windows: PG_Upgrade.bat

  7. Follow the on-screen instructions until the upgrade is complete.

    If you want to roll back to the old PostgreSQL database server version, rename the pgsql.old.<timestamp> directory to pgsql. The database server reverts to the existing version before the upgrade. Any changes made to the new PostgreSQL database server are not applied to the downgraded PostgreSQL database server version.

Upgrading an External PostgreSQL, Oracle or MSSQL Database Server

This procedure describes how to upgrade an external PostgreSQL, Oracle or MSSQL database server after you upgrade Control-M/EM or Control-M/Server.

Begin

  1. Verify that the database server version is supported, as described in Product Availability & Compatibility.

  2. Verify the database server requirements, as described in Database Server Requirements.

  3. Contact your DBA to upgrade your database server.

    • If the connection properties changed in the new database server, update the Control-M/EM or Control-M/Server configuration to point to the new location, as described in Control-M/EM Database Hostname or Parameter Changes.

    • (Oracle only) You can upgrade Control-M to version 9.0.22 and use Oracle 12c as an external database server, but you must upgrade your external database server to a supported version before you start up Control-M components.