Share This:

  • Review the System requirements for the Application Server and ETL Engine to ensure that your system meets the new requirements before starting the upgrade.
  • Review the database and client requirements to ensure that your system meets the new requirements before starting the upgrade. For TSCO 20.02 is required to install oracle client 12 or later
  • Starting version 11.5 and later, the memory requirements for the system that hosts the Application Server, has been increased from 8 GB to 16 GB. Ensure that your system has enough RAM to accommodate this increase in value.
  • Ensure that the Datahub system has a minimum of 10 GB of free space for the H2 data migration. The next command will tell how much space is free on the $CPITBASE file system:

cd $CPITBASE # The TSCO installation Directory, by default, /opt/bmc/BCO
df -h .

  • Ensure that you have a full backup of the TSCO database and file-system of the Application Server installation folder ($CPITBASE, by default /opt/bmc/BCO)
  • Copy the installation image to each of the TSCO servers that will be upgraded. This step will save you a lot of time when you are ready to start the setup execution. Download TSCO Installer.
  • For an X-Windows upgrade, make sure is working properly on each server (you can run the '' on the machines to make sure it works). We have been in situations where upgrade is canceled due to this detail.

This KA: The TSCO or TSCO Gateway Server/Agent installation fails with error, "java.lang.NoClassDefFoundError: Could not initialize class java.awt.Toolkit" when there isn't a valid DISPLAY assists on common issues for this point.

  • BMC recommends that you upgrade using root user, because the Shared Repository option is available only to the root user. But If you aren't making that change to the repository then you can run the TSCO upgrade as the TSCO Installation Owner user (the 'cpit' user by default)





TSCO Upgrade - Best Practices

TSCO Upgrade - Start

TSCO Upgrade - PostChecks

TSCO Upgrade - Common Questions