Troubleshooting your rolling upgrade

To help troubleshoot the rolling upgrade process, use the upgrade log to look for any errors. The system also prompts you with error messages.

Log file

For troubleshooting purposes, check the upgrade log under this directory:
  • $EGO_TOP/upgrade/logs
  • Installation_top\upgrade\logs

This file contains informational messages, in addition to warnings and errors that you may want to review. Some egoupgrade cluster warnings may be logged because your installation has customized files that the upgrade is unaware of; in this case, you can safely ignore the missing file warnings.

Error handling for common problems

Common upgrade problems include the following issues:
  • If you encounter errors while running the upgrade commands, ensure that you sourced your upgrade environment. Ensure also that you are logged on with a user account that has permission to start EGO. You should perform your upgrade using the same user account that you used to install your previous version of IBM® Spectrum Symphony.
  • The system detects whether the same product edition of IBM Spectrum Symphony exists on your environment. If there are compatibility issues, and your environment does not meet the prerequisites for upgrading IBM Spectrum Symphony, the system prompts with error messages.
  • If the system detects an issue with installing any of the .rpm files, the system prompts with error messages.
  • If you run the upgrade commands in the wrong order or without the appropriate prerequisites, the system prompts you. For example, if you run the egoupgrade rollback host command before running the egoupgrade rollback cluster command, the CLI prompts with an error to run the egoupgrade rollback cluster command first.
  • If you run the egoupgrade cluster command unsuccessfully on a host that is configured for remote startup, check that the user account you logged in with can remotely start EGO on all primary candidate hosts.
  • When you upgrade IBM Spectrum Symphony on the primary candidate hosts, ensure that you specify the same installation path on the primary candidate hosts as you used for the primary host installation; otherwise, the installer will not be able to start and stop the primary candidate, causing issues for the cluster upgrade process.
  • If you encounter issues with the cluster management console, ensure that you clear your browser cache and cookies. Also, clear the $EGO_TOP/gui/work and $EGO_TOP/gui/workarea directories.

Upgrading add-on features after upgrading IBM Spectrum Symphony

If you previously used add-on features with IBM Spectrum Symphony, after you complete the rolling upgrade process, you can continue to use these add-on features by appending the add-on feature entitlements to the IBM Spectrum Symphony entitlement file (platform.entitlement) for your upgraded version of IBM Spectrum Symphony. Copy the add-on feature entitlements from sym_*_entitlement.dat to platform.entitlement, so that the entitlement file contains all the required entitlements.

Restoring the previous version

After you upgrade your local hosts and cluster, test your cluster functionality before enabling any new functionality.

If you require restoring to the IBM Spectrum Symphony 7.3.2 level, you can run the egoupgrade rollback commands.

Once you have rolled back the cluster and hosts, you can rerun the IBM Spectrum Symphony upgrade, or you can completely uninstall your upgraded version of IBM Spectrum Symphony.

Note:
  • If you have multiple products in your cluster (for example, IBM Spectrum Symphony and IBM Spectrum Conductor) and you roll back your upgrade, the rolled back product does not function because common components may be affected by the rollback. Once you successfully rerun the upgrade, all products within your cluster will function.
  • Running the egoupgrade cluster command backs up existing configuration files to a backup directory within your shared location (shared_top) directory. This backup includes configuration files in your the system (such as EGO service XML files, application profile files, and so on), used for your previous version of IBM Spectrum Symphony, but does not include backing up the previous IBM Spectrum Symphony service package. Do not upgrade the service package during your cluster upgrade and application upgrade stages. If you upgrade the service package during these stages, and you require rolling back to the previous version of IBM Spectrum Symphony, the service package will not be correctly configured for the previous application profile, and your application will not work. If you rollback, ensure you have the previous service package working with the previous application profile.

Uninstalling the previous version

Once you uninstall the EGO core package from Windows, EGO shuts down. If you have another version of EGO core installed, you must restart it manually:
egosh ego start