Is there anything that I should know or do before upgrading my production environment? The answer is yes and the following answer will explain all things that you should review before starting the upgrade to 1808. 1808 upgrade failure may trigger the Zero Down Time roll back if the upgrade fails. This is something we want to avoid because it will roll back the AR Server as well as AtriumCore. Some of these checks are already done by the installer and you may get a Warning message about them. Below is a list of all issues we've found during the upgrade that was tested from version 8.1. - Check for Classes in Pending or Delete status in OBJSTR:Class. Delete them if you find any, but first check to see if there is an Active "Copy" of that same Class record. The installer detects CMDB attributes (missing fields) that are out of synch with AR metadata, but it does not detect out of the box fields and classes. Please see this KA for understanding of AR and CMDB metadata: AtriumCore CMDB CDM break down within the ARSCHEMA database Also please see previously known issues with upgrades prior to 9.1.04: Upgrading AtriumCore from 7.5 to 8.1 and 9.1 - What you should know to prevent upgrade failures Prior to upgrade:- Check for classes in Pending status in OBJSTR:Class Please see KA000052300 "Reconciliation performance issues caused by too many records in the RE:Job_Runs forms" : for reference. Although we think that the upgrade will do fine if all these precautions are taken care off. This KA was researched and prepared by BMC Software support organization. |
This knowledge article may contain information that does not apply to version 21.05 or later which runs in a container environment. Please refer to Article Number 000385088 for more information about troubleshooting BMC products in containers. We've validated this upgrade extensively and while most found issues got fixed, some issue remain open. BMC documentation has published a list for 1808 known issues which is available here: Known and corrected issues for AtriumCore 1808 Here is what you need to know: A. SYSTEM RESOURCES First concern is the resources of the system on which the AR system is hosted. Older versions of the product can be hosted on systems that are under the bar for version 1808. We've tested upgrades on systems below 16 Gigs of RAM, 2 CPUs, and limited space available for swap file. Each attempt has failed at some stage or another. As a result of this testing our recommendation is to have a minimum of 16 Gigs of RAM, 4 CPUs and enough room for swap file(*1) and logs. (*1)Windows Swap file should be setup to match the recommendation made by the operating system. If the system has 16 Gigs of RAM then make sure the VM size is set recommended by the VM setting. Make sure that the "Space available" is not lower than BMC recommendations for free disk space which also needs to be able to accommodate the size of the swap file: B. UPGRADE PRE-CHECKS & KNOWN ISSUES THAT MAY COME UP DURING THE VALIDATION STAGE.
For Solaris related installs or upgrades please see: https://selfservice.bmc.com/casemgmt/sc_KnowledgeArticle?sfdcid=000159441 |