Completing the BMC Atrium Core upgrade
After you have finished upgrading Atrium Core components, complete the tasks in the following table.
Task | Action | Additional information |
---|---|---|
1. | Review the upgrade log files. | The installer writes status messages to a log file, giving a detailed account of all changes made to your data model during the upgrade. If the upgrade fails and you must run the installer again, the installer resumes after the last operation it completed, rather than repeating operations that have already been completed. |
2. | Enable entries in the armonitor and ar configuration files. | Enable the entries that you commented out before the upgrade. |
3. | Clean up normalized CI relationships. | The datamig utility cleans up the configuration items (CIs) in the staging datasets for which relationship names are normalized following the old best-practice relationship rules, and impact relationships are generated following the old best-practice impact normalization rules. |
4. | Verify the CMDB OOTB indexes. | Run the BMC Remedy Configuration Check utility to validate the CMDB OOTB Index Check. |
5. | Perform denormalization of the CDM classes and relationships. |
Where to go from here
Up to process | When you have finished upgrading the Atrium Core components and the platform, return to the appropriate upgrade process: |
---|
Was this page helpful? Yes No
Submitting...
Thank you
Comments
Step 5 "Denormalize the Common Data Model (CDM)" gets "Page Not Found"
Also - Reading documentation for 9.1.04 (https://docs.bmc.com/docs/ac91/performing-denormalization-of-common-data-model-609846892.html), it is stated as a prerequisite before performing this step "Create a staging server". We are upgrading "in Place" and therefore has no staging server. How should I understand step 5 above - should it be omitted or what...?
Hi Peter,
The link is fixed. you can access the content now.
Also, please see the Gustavo's response below for your query on staging server.
Regards, Maithili
Hi Peter,
A Staging server is a requirement but sometimes if you don´t have the resources it can be optional.
What is really important is that you take a DB Backup because the Denormalization process does not have a fallback mechanism, so in case where there is a failure you will need to revert the DB to recover your environment.
Take note that if you do not have staging server and this process fails you will not be able to use the server until you revert the DB.
Log in or register to comment.