This documentation supports the 19.02 version of Remedy Deployment.

To view the latest version, select the version from the Product version menu.

Performing the BMC Atrium CMDB upgrade


Upgrade BMC Atrium CMDB after you upgrade the BMC Remedy AR System server. The installer upgrades the following features:

  • BMC Atrium CMDB
  • Reconciliation Engine
  • Normalization Engine

If BMC Atrium CMDB and BMC Atrium Core Web Services are on the same computer, both are upgraded together. 

Note

Although the installer is not expected to affect data directly during upgrade, the installer runs the following data operation that can increase the time to upgrade BMC Atrium CMDB depending on the data size:

The BMC Atrium Core installer populates the MarketVersion attribute for existing product CIs in all datasets with the value that is set for the VersionNumber attribute. BMC Remedy Asset Management version 7.6.03, and later, refers to the MarketVersion attribute (instead of the VersionNumber attribute) of a product CI to manage software licenses. The VersionNumber attribute is still used in other areas of BMC Remedy Asset Management and BMC Remedy ITSM Suite version 7.6.03 and later.  

In this section

Before you begin

If you have not done so already, perform the tasks in Preparing for the BMC Atrium Core upgrade.


To upgrade BMC Atrium CMDB

Note

- While the upgrade is processing, you should not perform any Remedy AR System or Atrium CMDB administrative functions until the upgrade is complete for that system.

- When upgrading, disable the Record Object Relationships option from Administration Console > Configurations tab.

  1. If you have not already done so, download the BMC Atrium Core System installer from EPD, or navigate to the installation directory on the DVD.
  2. Unzip the installer.
  3. Navigate to the Disk 1 folder.
  4. Start the installer.
    • For Windows, run setup.exe.
    • For UNIX, run setup.sh.
  5. In the Welcome panel, click Next.
  6. Review the license agreement, click I agree to the terms of license agreement, and then click Next.
  7. In the AR System Server Information panel, perform the following actions:
    1. Enter AR System username and password.
    2. Enter AR System port number and host name.
    3. Navigate to the directory in which you want to install BMC Atrium CMDB.
      The default locations are:
      • Windows: C:\Program Files\BMC Software\AtriumCore
      • UNIX or Linux: /opt/bmc/AtriumCore
    4. Click Next.
      The installer validates the system resources of your computer.
  8. If you are upgrading from version 7.6.04, in the Disabling status history on CDM forms panel, select Yes if you want to delete the history data of CDM tables. BMC recommends that you delete the history tables for better performance.
  9. In the Install mode panel, select Upgrade, and then click Next.
    During upgrade, only existing BMC Atrium Core components are upgraded.
  10. In the Confirmation panel, review that the database is backed-up and the memory requirement is met. Then click Yes and Next.
  11. Resolve the errors and warnings, if reported, in the BMC Configuration Check report before proceeding with the upgrade. If you ignore the installer instructions, the installer requires that you acknowledge those errors and warnings by selecting a check box before you proceed with installation or upgrade.

  12. Review the NE Plugin and Atrium Plugin ports. 
  13. In the Java Information panel, select the JRE path and click Next.
    The Run Health Check panel appears. BMC recommends that you run this check.
  14. Click Next.
    The installer validates your inputs in the previous panels, and then the Installation Preview panel appears, listing the product and product features that will be installed. 
  15. Click Install.
    A summary of the installation appears.
  16. Click View Log to review the installer log for any errors or warningsThe install logs are available at the following location:
    • (Windows) C:\Users_<installUser>_\AppData\Local\Temp\atriumcore_install_log.txt
    • (UNIX and Linux) \tmp\atriumcore_install_log.txt
    If the installation fails, see Troubleshooting BMC Atrium Core issues.
  17. To exit the BMC Atrium Core installer, click Done.
  18. Restart the BMC Remedy Mid Tier.

After you upgrade BMC Atrium CMDB

  • After you upgrade, check whether a patch or fix has been released in Release notes and notices. When you upgrade the product, you must install the latest service pack and then apply the latest patch (if available). Patches are not full installations and must be applied over the latest full installation (main release or a service pack).
  • (Staged upgrade only)  Immediately after you upgrade BMC Remedy Atrium CMDB on the destination server (production staging server or QA), disable the Reconciliation Engine and the Service Level Management collector in armonitor.conf or armonitor.cfg by placing a leading # (hash) on each line:

    • arcmdbd
    • arrecond
    • BMC.FILTERAPI.NORM.ENGINE
    • slmbrsvc
    • slmcollsvc

    Restart the AR System server. For instructions, see Starting and stopping the BMC Remedy AR System server

  • (Staged upgrade only) Ensure that the DSO and escalation services are still disabled. For instructions on how to disable these services, see To disable DSO and escalations after you set up a staging system.


To verify the BMC CMDB archive utility

During the upgrade process, if the CMDB installation is completed successfully but the archive utility fails to run, you must run archive utility later on after the upgrade installation is complete, and make sure that the archive policy is set for all the classes successfully.  You must run the CMDB Archive Manager only after the archive policy is set for all the classes. Failing to do so may result in data inconsistencies and orphan data. 

Warning

The archive data cannot be restored back in CMDB as CIs.

For information on steps to run the archive utility, see  CMDB data archive overview .

To perform a health check of BMC Atrium CMDB

Before you upgrade, you must verify that the class definitions in your data model are correct. Class definitions in your data model are verified when you perform a health check of BMC Atrium CMDB.

Follow these steps to manually verify the data model and perform a health check:

  1. From the BMC Atrium CMDB Maintenance tool, run the health check. See  Performing a health check . For more information about possible errors and resolving the errors, refer to  kA214000000
  2. Examine the arerror.log located at <InstallDirectory>\BMC Software\ARSystem\Arserver\Db and cmdbengdebug.log located at <InstallDirectory>\BMC Software\ARSystem\Arserver\Db files for any errors about starting the cmdbEngine.
    Search for the string cmdbEngine to find errors. When the cmdbEngine is started, it validates the class definitions. The following example shows an error message that you might see in arerror.log:

    *Mon Dec 11 16:10:18 2006 390600 : The specified super class with given classId is not found. : Class ID: OB005056C00008PlV3RQU3oZAAHO8C, Super Class ID: OB005056C00008F1V3RQd#IYAAD90C (ARERR 120132)*
  3. Perform the following steps to verify that all classes in your data model are active:
    1. In a browser, open the OBJSTR:Class form in search mode.
    2. In the Advanced Search Bar at the bottom of the window, specify the following query:

      'OSStatus' != "Active" OR 'Pending ID' != "0" OR 'System Status*' != "Active" OR 'Record Status' != "Active" OR 'Status' != "Active"

      If this query returns any rows, it means that those classes were either not correctly created or not correctly deleted.

    3. Check the classes listed in the result window to investigate the issue.
  4. Perform the following steps to verify that all attributes for the classes are Active.
    1. In a browser, open the OBJSTR:AttributeDefinition form in Search mode.
    2. In the Advanced Search Bar at the bottom of the window, specify the following query:

      'OSStatus' != "Active" OR 'Pending ID' != "0" OR 'Record Status' != "Active"

      If this query returns any rows, it means that those attributes were either not correctly created or not correctly deleted.

  5. (If upgrading from version 9.0 or later) To identify pending metadata:

    1. Run cmdbdriver from the BMC Remedy AR System server .
      For information, see  cmdbdriver program  in BMC Atrium Core documentation.

      Note

      On a UNIX computer, you may need to open the arcmdbd.sh file and set LD_LIBRARY_PATH to the path where the BMC Atrium CMDB files and directories are installed.

    2. Type the glc command to get the list of classes.
      Accept default values for all prompts displayed for this command. A list of classes is displayed. 

      Note

      If BMC Remedy AR System server fails to copy the cmdb-9.1.00-SNAPSHOT.jar file into BMC_AR_SYSTEM_HOME\deploy folder, the AtriumPluginSvr log reports the following error: "RPC failed with: ERROR (8203): The server's RPC version is not supported." Other log files also report errors that indicate the cmdb-9.1.00-SNAPSHOT.jar  file is missing from the deploy folder. For more information about the possible errors and resolving these errors, refer to kA214000000

  6. Only if upgrading a clone of your current production environment(staged upgrade) or upgrading in-place, ensure that the ARDBC.Notify plug-in is running. 
    ARDBC.Notify plug-in is a component installed with BPPM CMDB extensions. 
    The condition does not apply when upgrading against a database (DB-only upgrade).

    Important

    If you find that the ARDBC.Notify plug-in is not running, from the ar.conf or the ar.cfg file, set the following parameters to match your environment: Plugin, BMC-ARDBC-NOTIFY-Server-Port, BMC-ARDBC-NOTIFY-Protocol-V1-Encrypt, BMC-ARDBC-NOTIFY-Event-Cache, and BMC-ARDBC-NOTIFY-Verify-Log.

  7. Import the NOE:QueryTransaction form. If you are upgrading from BMC Atrium Core version 7.6.04 or 8.1 to version 18.08 perform the following steps:

    1.  Ensure that you have imported the NOE:QueryTransaction form. The NOE:QueryTransaction  is a custom form in version 8.1 and during the upgrade, the installer converts the form to a regular non-overlaid form. 
    2. Choose the Best Practice mode.
    3. Delete the Custom NOE:QueryTransaction form and import the attached NOE:QueryTransaction.xml file using the Base Development mode in dev studio (version 1808). You can import the entire NOE:QueryTransaction definition file with Overwrite option on.

      See  Knowledge article 000157623  for more information.

  8. Configure the AtriumPluginSvr 9556 plugin. Sometimes during the upgrade process, the AtriumPluginSvr 9556 plugin fails to upgrade. This is caused by bad log4j_configsvr.xml in 8.1. Perform the following steps.

    1. Create the file using the attached sample files, pluginsvr_config.xml and log4j_pluginsvr.xml.
    2. Edit the file and replace the drive letter C: with the drive letter of your computer. Change the hostname in the pluginId to match the server on which the plugin is running.

    See  Knowledge article 000157623  for more information.

  9. When you upgrade BMC Atrium Core, overlays in CMDB forms can cause major issues. You must remove overlays from the CMDB forms before you perform the upgrade.

Troubleshooting the BMC Atrium Core upgrade

Consult the following topics for information about issues you might encounter during the upgrade:

Where to go from here

Next task

If BMC Atrium Core web services is on a different computer, perform the BMC Atrium Core Web Services upgrade after you upgrade BMC Remedy AR System and BMC Atrium CMDB.

When you have finished upgrading Atrium Core components, proceed to Completing the BMC Atrium Core upgrade.

Up to process

If you have finished upgrading the platform, return to the appropriate upgrade process:

Was this page helpful? Yes No Submitting... Thank you

Comments