Control-M Upgrade

The Control-M upgrade process upgrades your current version of Control-M/Enterprise Manager, Control-M/Server, and Control-M/Agent to the latest annual or fix pack version on the same computer. This eliminates the need to migrate data and reduces downtime. To minimize downtime, Control-M processes stay up during the upgrade preparation process, which prepares all the required files. After the preparation completes, you are prompted to confirm the shutdown of Control-M processes. After the processes are shut down, the upgrade begins and completes with minimum downtime.

You can only upgrade from Control-M version 9.0.19 or higher. For lower versions of Control-M, you must first migrate your data, as described in Control-M Migration.

The upgrade process supports compatibility across all Control-M components, as follows:

  • An upgraded Control-M/EM is compatible with lower versions of Control-M/Server (from 9.0.19 and higher).

  • An upgraded Control-M/Server is compatible with lower versions of Control-M/EM (from 9.0.19 and higher).

  • An upgraded Control-M/EM is compatible with lower versions of Control-M client (from 9.0.19 and higher). However, the new features of the higher version are disabled.

    For more information, see Compatibility Mode and Control-M Client and Control-M/EM Server Compatibility Scenarios.

The following is a typical scenario of the upgrade flow:

  • Control-M/EM server: After the upgrade completes, Control-M/EM is in Compatibility Mode and older Control-M clients that were not upgraded can still work with the upgraded Control-M/EM server.

  • Control-M clients: The new features are disabled in Compatibility Mode. You can upgrade manually or with Client Distribution.

  • Control-M/Server

  • Turn off Compatibility Mode, as described in Turning off Compatibility Mode.

  • Control-M/Agents: You can upgrade manually or with Control-M/Agent deployment.

Before you upgrade, review Upgrade Requirements and Considerations

The following procedures describe how to upgrade Control-M/EM, Control-M/Server, and Control-M/Agent:

If you are using the BMC dedicated PostgreSQL database, after you have upgraded Control-M/EM or Control-M/Server, the PostgreSQL database server version remains the same and must be upgraded, as described in Control-M Upgrade.

If you are using an Oracle or MSSQL external database, see Upgrading an External Oracle or MSSQL Database Server.

Upgrade Requirements and Considerations

Review the following requirements and considerations to ensure that your environment is ready for the upgrade.

Component / Topic

Requirement

New Features

To use the new features of Control-M version 9.0.21, you must upgrade both Control-M/EM and Control-M/Server to the latest version.

HTTPS Protocol

The Control-M client connects to the Control-M/EM server via the Control-M Web Server. After the upgrade, BMC recommends to use the HTTPS protocol to secure the connection between the Control-M Web Server and Control-M/EM server, which is more secure than the HTTP protocol.

Control-M/Agent

  • You can upgrade Control-M/Agent from version 9.0.00.400 to version 9.0.21.

  • For Application Pack deployment, you must upgrade Control-M/Agent to version 9.0.21.

Control-M/EM Distributed

In a Control-M/EM Distributed environment, you must install the same version on both the Control-M/EM server and Control-M/EM Distributed hosts, as described in Upgrading Control-M/EM on UNIX and Upgrading Control-M/EM on Windows.

Client Distribution

  • This feature is disabled during upgrade

  • After the upgrade, you can only distribute Control-M client version 9.0.19 and higher

    For more information, see Client Distribution.

SSL

  • If your Control-M/EM environment is encrypted with SSL, and the CmsCommMode system parameter value is SSL or AUTO and at least one Control-M/Server is connected via SSL, the security policy must not use .kdb keystores, and the security policy must be configured to the TLS 1.2 protocol before the upgrade. To check the security policy attributes, see Security Policies.

  • If your Control-M/EM environment is encrypted with SSL, recycle the Reports service after the upgrade.

High Availability

If you are upgrading in a High Availability environment, see High Availability Requirements.

Control-M Workload Archiving

The Control-M Workload Archiving server is upgraded automatically when you upgrade Control-M/EM Distributed.

Control-M Automation API

Control-M Automation API CLI is not supported on Red Hat Enterprise Linux version 6 or lower after you upgrade Control-M/EM to version 9.0.21 or higher.

Promotion

Promotion from one environment to another is only available when both Control-M/EM and Control-M/Servers are the same version.

Compatibility Mode

  • If Compatibility Mode is On, you can promote from Control-M client 9.0.21 to all 9.0.21 environments.

  • If Compatibility Mode is Off, you can only promote from Control-M client 9.0.21 to 9.0.21 environments that compatibility mode is Off.

Demo Scripts

Modified demo scripts from previous versions that are stored in the $HOME/ctm_em/bin directory are overwritten during the upgrade and need to be recreated.

BMC recommends that you do one of the following:

  • Back up the scripts separately

  • Modify the demo scripts that are placed in the $HOME/ctm_em/bin directory as part of the upgrade.

Site Standards

Site Standards you created in the original version of Control-M are backed up in the def_items_table_backup.dat file when you upgrade.

If you want to downgrade, see Restoring Site Standards after Downgrade.

Compatibility Mode

Compatibility Mode allows users with previous versions of the Control-M client to connect to the latest version of Control-M/EM server in addition to the upgraded Control-M clients. However, when Compatibility Mode is on, new features are disabled in upgraded Control-M clients. This ensures system integrity during the transition to a higher version. After Compatibility Mode is turned off, the new features are enabled in the upgraded Control-M clients and older clients are disconnected. Users that have not upgraded their Control-M clients cannot log in.

The following table lists the features that are disabled in Control-M clients after you have upgraded and compatibility mode is on.

Source Version

Disabled Features
9.0.20.xxx

  • Users

  • Roles

  • API Tokens

  • Run as Management

  • System Settings

  • IdP Authentication (SAML)

  • Reference Folder

  • SHA512 encryption algorithm
9.0.19.xxx

  • User Views (Web)

  • Site Standards (Web)

  • XML validation

  • 85 character host name limit

  • Centralized Connection Profile

  • Control-M MFT Enterprise (Web)

  • RBA Authorizations

  • 9.0.20.xxx features

Turning off Compatibility Mode

This procedure describes how to turn off Compatibility Mode, which enables new features in upgraded clients.

  • After Compatibility Mode is turned off, users that have not upgraded their Control-M clients cannot log in.

  • After Compatibility Mode is turned off, you cannot turn it back on.

Begin

  1. From the CCM in the Manage tab, click Compatibility Mode.

  2. Click I have read and understand.

  3. Click Turn Off Compatibility Mode.

    Control-M/EM server components are restarted automatically.

Control-M Client and Control-M/EM Server Compatibility Scenarios

The following table lists the different Control-M client and Control-M/EM server compatibility scenarios after you upgrade Control-M/EM server from the source (compatibility version) to the new target version.

Control-M/EM Server Source Version

Control-M/EM Server Target Version

Client Version

Result
9.0.19.xxx 9.0.21

9.0.19.xxx

Compatibility Mode: On

 Success
9.0.19.xxx

9.0.21

9.0.19.xxx

Compatibility Mode: Off

Fail

Reason: When compatibility mode is off, the client must be in the same major release as the server target version.
9.0.19.xxx 9.0.21

9.0.21

Compatibility Mode: On

 Success

Upgrading Control-M/EM on UNIX

This procedure describes how to upgrade from Control-M/EM 9.0.18 (Default and Distributed) and higher to the latest version of Control-M/EM on UNIX. If you want to upgrade multiple instances of Control-M/EM on several computers using the same configuration, use the automatic installation, as described in this procedure.

  • The default upgrade is interactive and uses a GUI display. XServer must be running and configured using the DISPLAY environment variable. If you do not have XServer available, BMC recommends that you continue with the console upgrade or perform an automatic upgrade.

  • If you have a Control-M/EM Distributed installation, you must upgrade the default Control-M/EM first and then upgrade the Distributed Control-M/EM. The Workload Archiving server is upgraded automatically during the Control-M/EM Distributed upgrade.

Before You Begin

Ensure that you have met the following requirements:

Begin

  1. Copy the installation files from the temporary directory that you created in Obtaining Control-M installation files, to the home directory.

  2. Set your DISPLAY environment variable, as described in Setting Environment Variables in UNIX.

  3. From your home directory, type the following command:

    <source_path>/setup.sh

  4. Do one of the following:

    • Interactive upgrade: Select the Control-M/Enterprise Manager option and continue with the on-screen instructions until the upgrade is complete.

    • Automatic upgrade: Create a parameter file and then run the automatic install in a non-interactive mode, as follows:

      1. Select the Control-M/Enterprise Manager option and continue with the on-screen instructions until the Summary window.

        There is no confirmation to shut down Control-M/EM processes. It is done automatically.

      2. Click Generate and select the location to create the XML parameter file.

      3. Click Yes to quit the upgrade.

        A confirmation message appears.

      4. Click Yes.

      5. Copy the automatic upgrade parameters file to a network location that is accessible to all computers where you want to perform an automatic upgrade.

      6. To run the upgrade script, type the following command:

        <source_path>/setup.sh -silent <xml_path>/<filename.xml>

        The upgrade logs can be found at the following location:

        <$HOME>/BMCINSTALL/log/BMC_Control-M_Enterprise_Manager_<date-time>.log

        To ensure compatibility between older versions of Control-M client, Control-M/EM is now running in Compatibility Mode.

Upgrading Control-M/EM on Windows

This procedure describes how to upgrade from Control-M/EM 9.0.19 (Default and Distributed) and higher to the latest version of Control-M/EM on Windows. If you want to install multiple instances of Control-M/EM on several computers using the same configuration, use the automatic installation, as described in this procedure.

If you have a Control-M/EM Distributed installation, you must upgrade the default Control-M/EM first and then upgrade the Distributed Control-M/EM. The Workload Archiving server is upgraded automatically during the Control-M/EM Distributed upgrade.

Before You Begin

Begin

  1. Log in to the computer using a user ID that has Administrator permissions.

  2. Copy the installation files from the temporary directory that you created in Obtaining Control-M installation files, to the home directory of the drive where the existing Control-M/EM is installed.

  3. From a command prompt window, enter <source_path>\setup.exe.

  4. Do one of the following:

    • Interactive upgrade: Select the Control-M/Enterprise Manager option and continue with the on-screen instructions until the upgrade is complete.

    • Automatic upgrade: Create a parameter file and then run the automatic install in a non-interactive mode, as follows:

      1. Select the Control-M/Enterprise Manager option and continue with the on-screen instructions until the Summary window.

        There is no confirmation to shut down Control-M/EM processes. It is done automatically

      2. Click Generate and select the location to create the XML parameter file.Click Yes to quit the upgrade.

      3. Click Yes to quit the upgrade.

      4. A confirmation message appears.Click Yes.

      5. Copy the automatic upgrade parameters file to a network location that is accessible to all computers where you want to perform an automatic upgrade.

      6. Log in using a user ID that has Administrator permissions on the current computer.

      7. Ensure that the upgrade DVD is still in the DVD drive, and run the upgrade script, as follows:

        <source_path>\Setup_files\components\em\setup.exe -silent <xml_path>\<filename.xml>

        The upgrade log can be found at the following location:

        %temp%\BMC_Control-M_Enterprise_Manager_<date-time>.log

        To ensure compatibility between older versions of Control-M client, Control-M/EM is now running in Compatibility Mode.

Upgrading Control-M Client on Windows

This procedure describes how to upgrade the Control-M client to the latest version on Windows. If you want to install multiple instances of Control-M client on several computers using the same configuration, use the automatic installation, as described in this procedure.

Before You Begin

Begin

  1. Log in to the computer using a user ID that has Administrator permissions.

  2. Copy the installation files from the temporary directory that you created in Obtaining Control-M installation files, to the home directory of the drive where the existing Control-M/EM is installed.

  3. From a command prompt window, enter <source_path>\setup.exe.

  4. Do one of the following:

    • Interactive upgrade: Select the Control-M/Enterprise Manager option and continue with the on-screen instructions until the upgrade is complete.

    • Automatic upgrade: Create a parameter file and then run the automatic install in a non-interactive mode, as follows:

      1. Select the Control-M/Enterprise Manager option and continue with the on-screen instructions until the Summary window.

      2. Click Generate and select the location to create the XML parameter file.Click Yes to quit the upgrade.

      3. Click Yes to quit the upgrade.

      4. A confirmation message appears.Click Yes.

      5. Copy the automatic upgrade parameters file to a network location that is accessible to all computers where you want to perform an automatic upgrade.

      6. Log in using a user ID that has Administrator permissions on the current computer.

      7. Ensure that the upgrade DVD is still in the DVD drive, and run the upgrade script, as follows:

        <source_path>\Setup_files\components\em\setup.exe -silent <xml_path>\<filename.xml>

        The upgrade log can be found at the following location:

        %temp%\BMC_Control-M_Enterprise_Manager_<date-time>.log

        To ensure compatibility between older versions of Control-M client, Control-M/EM is now running in Compatibility Mode.

Upgrading Control-M/Server on UNIX

This procedure describes how to upgrade from Control-M/Server 9.0.19 and higher to the latest version of Control-M/Server on UNIX. If you want to upgrade multiple instances of Control-M/Server on several computers using the same configuration, use the automatic upgrade, as described in this procedure.

The default upgrade is interactive and uses a GUI display. XServer must be running and configured using the DISPLAY environment variable. If you do not have XServer available, BMC recommends that you continue with the console upgrade or perform an automatic upgrade.

Before You Begin

Ensure that you have met the following requirements:

Begin

  1. Copy the installation files from the temporary directory that you created in Obtaining Control-M installation files, to the home directory.

  2. Set your DISPLAY environment variable, as described in Setting Environment Variables in UNIX.

  3. From your home directory, type the following command:

    <source_path>/setup.sh

  4. Do one of the following:

    • Interactive upgrade: Select the Control-M/Server option and continue with the on-screen instructions until the upgrade is complete.

    • Automatic upgrade: Create a parameter file and then run the automatic install in a non-interactive mode, as follows:

      1. Select the Control-M/Server option and continue with the on-screen instructions until the Summary window.

        NOTE: There is no confirmation to shut down Control-M/Server processes. It is done automatically.

      2. Click Generate and select the location to create the XML parameter file.

      3. Click Yes to quit the upgrade.

        A confirmation message appears.

      4. Click Yes.

      5. Copy the automatic upgrade parameters file to a network location that is accessible to all computers where you want to perform an automatic upgrade.

      6. To run the upgrade script, type the following command:

        <source_path>/Setup_files/components/ctm/setup.sh -silent <xml_path>/<filename.xml>

        The upgrade log can be found at the following location:

        <$HOME>/BMCINSTALL/log/BMC_Control-M_Server_<date-time>.log

Upgrading Control-M/Server on Windows

This procedure describes how to upgrade from Control-M/Server 9.0.19 and higher to the latest version of Control-M/Server on Windows. If you want to upgrade multiple instances of Control-M/Server on several computers using the same configuration, use the automatic upgrade, as described in this procedure.

Before You Begin

Begin

  1. Log in to the computer using a user ID that has Administrator permissions.

  2. Copy the installation files from the temporary directory that you created in Obtaining Control-M installation files, to the home directory of the drive where the existing Control-M/Server is installed.

  3. From a command prompt window, enter <source_path>\setup.exe.

  4. Do one of the following:

    • Interactive upgrade: Select the Control-M/Server option and continue with the on-screen instructions until the upgrade is complete.

    • Automatic upgrade: Create a parameter file and then run the automatic install in a non-interactive mode, as follows:

      1. Select the Control-M/Server option and continue with the on-screen instructions until the Summary window.

        There is no confirmation to shut down Control-M/Server processes. It is done automatically.

      2. Click Generate and select the location to create the XML parameter file.

      3. Click Yes to quit the upgrade.

        A confirmation message appears.

      4. Click Yes.

      5. Copy the automatic upgrade parameters file to a network location that is accessible to all computers where you want to perform an automatic upgrade.

      6. Log in using a user ID that has Administrator permissions on the current computer.

      7. Ensure that the upgrade DVD is still in the DVD drive, and run the upgrade script, as follows:

        <source_path>\Setup_files\components\ctm\setup.sh -silent <xml_path>\<filename.xml>

        The upgrade log can be found at the following location:

        %temp%\BMC_Control-M_Server_<date-time>.log

Upgrading Control-M/Agent on UNIX

This procedure describes how to upgrade from Control-M/Agent 9.0.00.300 and higher to the latest version of Control-M/Agent on UNIX, which includes Application Integrator and Automation API CLI. If you want to upgrade multiple instances of Control-M/Agent on several computers using the same configuration, use the automatic upgrade, as described in this procedure.

  • This procedure upgrades Control-M/Agent locally. To deploy and upgrade multiple Control-M/Agents from the CCM, see Control-M/Agent deployment.

  • If you upgrade the Agent, Application Integrator that was part of Application Pack is upgraded as well. If you roll back the Agent, then Application Integrator cannot work. To re-enable Application Integrator, you must uninstall and then reinstall Application Pack.

  • If Application Pack is installed, verify that all Application Integrator jobs have completed before upgrading the Agent.

The default upgrade is interactive and uses a GUI display. XServer must be running and configured using the DISPLAY environment variable. If you do not have XServer available, BMC recommends that you continue with the console upgrade or perform an automatic upgrade.

Before You Begin

Ensure that you have met the following requirements:

  • Ensure that your operating system is compatible with the new version of Control-M/Agent, as described in Agent System Requirements for Linux.

  • Define the external Java location, as described in Setting the Java Environment Variable.

  • Ensure that the Internal Process Communication (IPC) subsystem is enabled.

  • Verify that your locale is set to English before beginning the upgrade.

  • (AIX only) You must set the tcp_nodelayack to 1 as a root user, as follows:

    /usr/sbin/no -o tcp_nodelayack=1

Begin

  1. Log in as a Control-M/Agent user and then switch to user root.

  2. Copy the installation files from the temporary directory that you created in Obtaining Control-M installation files, to the home directory.

    If you are upgrading Control-M/Agent in non-root mode, log out user root and log in as the Control-M/Agent user.

  3. Set your DISPLAY environment variable, as described in Setting Environment Variables in UNIX.

  4. From your home directory, type the following command:

    <source_path>/setup.sh

  5. Do one of the following:

    • Interactive upgrade : Select the Control-M/Agent option and continue with the on-screen instructions until the upgrade is complete.

    • Automatic upgrade: Create a parameter file and then run the automatic install in a non-interactive mode, as follows:

      1. Select the Control-M/Agent option and continue with the on-screen instructions until the Summary window.

        There is no confirmation to shut down Control-M/Agent processes. It is done automatically.

      2. Click Generate and select the location to create the XML parameter file.

      3. Click Yes to quit the upgrade.

        A confirmation message appears.

      4. Click Yes.

      5. Copy the automatic upgrade parameters file to a network location that is accessible to all computers where you want to perform an automatic upgrade.

      6. To run the upgrade script, type the following command:

        <source_path>/Setup_files/components/agent/setup.sh -silent <xml_path>/<filename.xml>

        The upgrade log can be found at the following location:

        <$HOME>/BMCINSTALL/log/BMC_Control-M_Agent_<date-time>.log

Upgrading Control-M/Agent on Windows

This procedure describes how to upgrade from Control-M/Agent 9.0.00.300 and higher to the latest version of Control-M/Agent on Windows. If you want to upgrade multiple instances of Control-M/Agent on several computers using the same configuration, use the automatic upgrade, as described in this procedure.

  • This procedure upgrades Control-M/Agent locally. To deploy and upgrade multiple Control-M/Agents from the CCM, see Control-M/Agent deployment.

  • If you upgrade the Agent, Application Integrator that was part of Application Pack is upgraded as well. If you roll back the Agent, then Application Integrator cannot work. To re-enable Application Integrator, you must uninstall and then reinstall Application Pack.

  • If Application Pack is installed, verify that all Application Integrator jobs have completed before upgrading the Agent.

Before You Begin

Begin

  1. Log in to the computer using a user ID that has Administrator permissions.

  2. Copy the installation files from the temporary directory that you created in Obtaining Control-M installation files, to the home directory of the drive where the existing Control-M/Agent is installed.

  3. From a command prompt window, enter <source_path>\setup.exe.

  4. Do one of the following:

    • Interactive upgrade : Select the Control-M/Agent option and continue with the on-screen instructions until the upgrade is complete.

    • Automatic upgrade :Create a parameter file and then run the automatic install in a non-interactive mode, as follows:

      1. Select the Control-M/Agent option and continue with the on-screen instructions until the Summary window.

        There is no confirmation to shut down Control-M/Agent processes. It is done automatically.

      2. Click Generate and select the location to create the XML parameter file.

      3. Click Yes to quit the upgrade.

        A confirmation message appears.

      4. Click Yes.

        The automatic upgrade XML parameters file that is created (<filename>.xml) is relevant only for computers with the same agent instance name. Otherwise, a separate <filename>.xml file must be created for each computer, or modified manually for each computer.

      5. Copy the automatic upgrade parameters file to a network location that is accessible to all computers where you want to perform an automatic upgrade.

      6. Log in using a user ID that has Administrator permissions on the current computer.

      7. Ensure that the upgrade DVD is still in the DVD drive, and run the upgrade script, as follows:

        <source_path>\Setup_files\components\agent\setup.exe -silent <xml_path>\<filename.xml>

        The upgrade log can be found at the following location:

        %temp%\BMC_Control-M_Agent_<date-time>.log

Upgrading the PostgreSQL Database Server

This procedure describes how to upgrade the PostgreSQL database server to the latest supported version. After you have upgraded Control-M/EM or Control-M/Server, the PostgreSQL database server version remains the same. If you want to upgrade the PostgreSQL database server, perform this procedure.

If you upgrade from version 9.0.18 to 9.0.20 the PostgreSQL version (9.5.5) remains the same. However if you install a new Control-M with 9.0.20, the PostgreSQL version is 11.5.

  • After you have upgraded the dedicated PostgreSQL database server to PostgreSQL 11, you can no longer downgrade Control-M/EM or Control-M/Server to a version below 9.0.21.

  • In a Full installation environment, perform this procedure one time. The Control-M/EM and Control-M/Server PostgreSQL databases are upgraded together.

Before you begin:

  • Verify that there is enough disk space to contain an additional PostgreSQL database server. The free space must be greater than the size of the <Control-M_Home>\pgsql directory including an additional 25%. The upgrade checks if there is enough space and it fails if it is not enough. For example, if the size of the pgsql directory is 1 GB, the upgrade requires at least 1.25 GB of free space.

  • Upgrade Control-M/EM or Control-M/Server to version 9.0.21.

  • Note that the upgrade requires down time of Control-M. The time for upgrade depends on the size of database. In most scenarios, the upgrade completes in 10 minutes. In a large scale environment it might take up to an hour.

Begin

  1. Navigate to one of the following PostgreSQL server upgrade package locations:

    UNIX: <cdPath>/Setup_files/TOOLS/pg_server_upgrade.tar.gz

    Windows: <cdPath>\Setup_files\TOOLS\pg_server_upgrade.zip

  2. Copy the package to be parallel to the pgsql directory.

    The pgsql directory is located in one of the following locations:

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

    • Control-M/EM on UNIX: <Control-M Home>/ctm_em/

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

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

  3. Do one of the following:

    • UNIX: Type the following commands to open and uncompress:

      1. gunzip pg_server_upgrade.tar.gz

      2. tar -xvf pg_server_upgrade.tar

    • Windows: Extract the pg_server_upgrade.zip.

  4. Shut down Control-M/EM or Control-M/Server components (both for Full Install):

  5. Navigate to the pg_server_upgrade directory and run one of the following commands:

    • UNIX: PG_Upgrade.sh

    • Windows: PG_Upgrade.bat

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

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

Upgrading an External Oracle or MSSQL Database Server

This procedure describes how to upgrade an external Oracle or MSSQL database server after you have upgraded 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 have changed in the new database server, update Control-M/EM or Control-M/Server configuration to point to the new location, as described in Reconfiguring the Database Server Connection Data.

    • (Oracle only) You can upgrade Control-M to version 9.0.21 using 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.

Upgrading Control-M in a Disaster Recovery Configuration

This procedure describes how to upgrade Control-M/EM and Control-M/Server in a Disaster Recovery configuration on UNIX and Windows. In a disaster recovery environment, the database in the recovery site is set to read-only, which enables replication from the primary site. This procedure allows you to upgrade without changing the read-only status of the database and without interrupting the database replication.

The database in the disaster recovery environment must have read access.

Begin

  1. Set the inst_skip_db_changes environment variable to Y where the upgrade is executed.

  2. Do one of the following:

    To upgrade Control-M/EM, see Upgrading Control-M/EM on UNIX or Upgrading Control-M/EM on Windows.

    To upgrade Control-M/Server, see Upgrading Control-M/Server on UNIX or Upgrading Control-M/Server on Windows.

  3. Set the inst_skip_db_changes environment variable to N.