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.

Upgrade issues

This topic describes issues that you might encounter when upgrading to a new BMC Release Process Management version.

This topic consists of the following sections:

Upgrading without database migration clean up

An upgrade operation fails when upgrading to a new folder without database migration clean up. This occurs when upgrading from BMC Release Process Management version 4.4 to version 4.6 on a Linux platform with an installed PostgreSQL database.

Workaround: In this case, before you perform the upgrade operation, do the following:

  1. At the installer root folder, locate the postgresql_patch.sh file.
  2. Copy the postgresql_patch.sh file to the <RLM>/pgsql/ folder, where <RLM> is the home folder for the previous version.
  3. Open a terminal session and change to the <RLM>/pgsql directory: cd <RLM>/pgsql
  4. Change the permissions of the postgresql_patch.sh file: chmod +x postgresql_patch.sh
  5. Run the script file: ./postgresql_patch.sh
  6. After the script completes, verify the following:
    • The word Done appears.
    • The <RLM>/pgsql/postmaster file is present. (This file is a symbolic link to <RLM>/pgsql/postgres.)

Saving time when upgrading silently to a new installation folder

In the 4.6.00, 4.6.00.02, and 4.6.00.03 versions of the BMC Release Process Management installer, the value for the BMC_AUTOMATION_RESULTS property is ignored and the COPY_DATA option is used instead. If you have a lot of data in the automation_results folder, it can take a long time to copy automations to a new installation folder.

Workaround: In this case, upgrade to a new installation folder by doing the following:

  1. Stop the BMC Release Process Management service.
  2. Move the content from the automation_results folder somewhere out of the <RLM> folder.
  3. Upgrade to a new folder.
  4. Stop the BMC Release Process Management service after the upgrade.
  5. Move the content from the automation_results folder back to the <RLM>/automation_results folder.
  6. Start the BMC Release Process Management service.

Upgrading from 4.4.x to 4.6.x version 

If you have many files with automation results and you upgrade BMC Release Process Management version 4.4.x to 4.6.x, either the RLM\automation_results folder can be deleted or the files in the folder can be replaced with zero bit files. 

Workaround: Back up the automation_results folder by doing the following:

  1. Go to the RLM folder.

  2. Rename the existing automation_results folder.

    Tip

    Instead of manually renaming the folder, you can use symbolic links. 

  3. Create an empty folder named automation_results.
  4. Perform the upgrade.
  5. After the upgrade, delete the empty automation_results folder and rename the folder with your automation results automation_results.

Related topics

Installing

Uninstalling

Upgrading

 

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