Preparing your data and performing a health check before you upgrade BMC Atrium Core

To prepare data for upgrade from any version of BMC Atrium Core

If you have jobs that are defined against deprecated classes, the jobs do not successfully upgrade and errors might occur. To overcome these errors, delete all rules that have been defined for deprecated classes. For details about the changes to BMC Atrium common data model (CDM), see Summary of changes to the Common Data Model 

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.

   1. 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.

Where to go from here

Related Topics

Troubleshooting issues with ARDBC plug-ins.