Error: Invalid spaceKey on retrieving a related space config.

BMC Atrium Core checks

This topic provides information about the checks performed by the BMC Remedy Configuration Check utility for BMC Atrium Configuration Management Database (BMC Atrium CMDB). It also describes the expected results of the checks and corrective actions to be taken if a check fails.

BMC recommends that you run all the pre-upgrade checks before you upgrade to a higher version. If you encounter any error or warning, address the issue as it may prevent a successful upgrade.

 

CMDB Config Params Check

Description

This check verifies whether the following parameters are specified as per the recommended values: 

  • CMDB-Inline-Normalization
  • CMDB RPC Normalization Queue
TypePre-upgrade check
Check performed and expected result
  • If CMDB-Inline-Normalization is set to 'F' or Private-RPC-Socket is set to any value other than  390699  2 4, the check fails.
  • If the parameter values are as per the recommended values, the check is successful.
Corrective action
  • Set CMDB-Inline-Normalization to 'T'.
  • To specify the value of the CMDB RPC Normalization Queue, look up Private-RPC-Socket setting in the Normalization Engine row in the table provided at Configuring private queue threads.

Go to top

CMDB - Enum Attribute Customization Check 

Note: This check is applicable only if you are upgrading from version 9.0 or lower.

Description

This check verifies whether any custom ID values were added to the selection type attributes (OSType , SystemType, ProcessorFamily). If a custom value is added to the list, it is considered as a customization.

Note: Before this check was introduced, customizations were included in the regular enum list. Now, they are included within the custom ID range. For more information on enum types, see Enum Type . BMC Atrium Core has reserved a range of enum IDs from 0 to 10,000 for these selection type attributes. All new custom values must be added with ID value starting from 10,001. 

Type

Pre-upgrade check 

Check performed and expected result

If the above mentioned customization is detected, the custom values are moved to the custom ID range (10,001 onwards) during the upgrade.

The details are logged in the CMDB Server Log.
Example:
<WARN> <TID: 0000000360> <User: sa> /* Sun Jul 19 2015 23:13:19.318 */   Moving item Windows 10 from index 77 to index 10001 as _Windows 10. Similar Item added at 78.  

Corrective action

No action required.

 Go to top

 CMDB - Max-Num-Caches Check

DescriptionThis check verifies whether the value of Max-Num-Caches is other than 1 and whether the Development cache mode is ON.

If the parameter Max-Num-Caches:1 is enabled in the ar.cfg (or ar.conf) file and the Development cache mode is OFF, the installation of BMC Atrium Core 9.0 can fail. However, if you set the Development cache mode to ON, Max-Num-Caches:1 has no effect.

Type

Configuration check 

Check performed and expected result

If the parameter Max-Num-Caches:1 is enabled in the ar.cfg (or ar.conf) file and the Development cache mode is OFF, the check fails and displays the following error message:

Max-Num-caches set to 1. This may cause Atrium upgrade failure. Disable this parameter in ar.cfg/ar.conf file -OR- turn ON Development cache mode.

Corrective actionDisable the parameter Max-Num-Caches:1 in the Centralize Configuration, or set the Development cache mode to ON.

Go to top

CMDB - Remedy Application Password Check

DescriptionThis check verifies whether the BMC Remedy Configuration Check utility can communicate with the BMC Remedy AR System server by using the password provided for members of the server group. This check validates whether a valid password is stored in the UDM:RAppPassword form.
TypePre-upgrade check, configuration check
Check performed and expected result

If no password is stored in the UDM:RAppPassword form or the stored password is incorrect, the check fails and displays the following error message:
The check could not verify the password for: 'Remedy Application Service' on '<hostname>' : <full error message>.

Corrective ActionUpdate the password on the UDM:RAppPassword form for the suggested server.

Go to top

CMDB - Schema Data Threshold Check

Description

This check validates forms for the data threshold limit for the records size.

Type

Configuration check 

Check performed and expected result

This check validates the following forms and their data threshold limits:

  • UDM:JobLog — 1000

  • RE:Job_Runs — 1000

  • RE:Job_Events — 10000

  • NE:JobRun — 1000

  • DSM:Log — 500

If the number of records in any of the forms exceeds the threshold limit, the check fails and displays the name of the form.

Corrective actionManually reduce the number of records in the forms so that the number in each form is lower than the threshold limit.

Go to top

CMDB Class Overlay Check

Description

This check verifies whether any overlays are created for BMC Atrium CMDB forms.

Note: BMC Atrium CMDB does not support overlay forms.

TypePre-upgrade check, configuration check
Check performed and expected result

If overlays are created for BMC Atrium CMDB forms, the check fails and displays the details of the overlays.

Corrective actionCheck the form name from the result file displaying the name of form containing overlay. Delete the overlay from the respective form before you proceed with the upgrade.

Go to top

CMDB Metadata Check

Description

This check verifies whether BMC Atrium CMDB metadata has any pending metadata operation, using the CDMChecker utility.

TypePre-upgrade check, configuration check
Check performed and expected result
  • If a pending metadata operation fails, the log file information is displayed. The log file is AtriumCoreInstallDir/Logs/pending_entries.log
  • If a specific functional failure occurs, a reference to a knowledge article is displayed.

Note:
If the BMC Remedy Configuration Check utility does not find the CDMChecker utility under the cmdb/server/bin directory, it displays an error.

Corrective action

Ensure that metadata operations do not exist in the pending state. After the pending operations are completed, proceed with the upgrade.

Go to top

CMDB OOTB Index Check

Description

This check verifies whether any out-of-the-box (OOTB) indexes are missing.

Type

Pre-upgrade check 

Check performed and expected result

If any OOTB index is missing, the check fails and one or more of the following error messages are displayed:

  • Index [BMC.CORE:BMC_BaseRelationship->530060100,6,400127400,400129200] is not present

  • Index [BMC.CORE:BMC_BaseRelationship->530060100,6,400129200] is not present

  • Index [BMC.CORE:BMC_BaseElement->530060100,6,400129200] is not present

  • Index [BMC.CORE:BMC_BaseElement->530060200,400127400] is not present

  • Index [BMC.CORE:BMC_BaseElement->530010100,400127400] is not present

Corrective action

 Go to indexes, and check whether missing indexes were created. If indexes are missing, create the missing indexes manually. For more information, see CMDB Indexes .

Go to top

Is CMDB Running Check

DescriptionThis check verifies whether the BMC Atrium CMDB engine is running prior to upgrade.
TypePre-upgrade check; configuration check
Check performed and expected result
  • If the BMC Atrium CMDB engine is running, the check is successful.
  • If the BMC Atrium CMDB engine is not running, the check fails and displays an error message.
Corrective actionsEnsure that the BMC Atrium CMDB engine is running before upgrading.

Go to top

Plug-in port configuration Check

DescriptionThis check verifies whether the plug-in port number and host name match with the plug-in server configuration information.
Type

Pre-upgrade check, configuration check 

Check performed and expected result
  • If the plug-in port specified in the ar.cfg (or ar.conf) file matches the port specified in the pluginsvr_config.xml file, the check is successful.
    If the ports do not match, the check fails and displays the following error:
    Plug in port is not configured correctly, values in ar.cfg and pluginsvr_config.xml do not match
  • For all the plug-ins configured in the pluginsvr_config.xml file, the check validates whether the files specified in the <filename> and <pathelement> parameters actually exist.
    If the files do not exist, the check fails and displays the following error:
    File <filename> configured for Plug-in: <plugin name> does not exists, check pluginsvr_config.xml.
  • For all plug-ins configured in the pluginsvr_config.xml file, the check validates whether a corresponding entry is present in the ar.cfg (or ar.conf) file:
    • If a corresponding entry exists, the check validates whether the port in the pluginsvr_config.xml file matches the port in the ar.cfg (or ar.conf) file.
    • If a corresponding entry does not exist in the pluginsvr_config.xml file and the ar.cfg (or ar.conf) file, but the port numbers do not match, the check fails and displays the following error message:
      Plug in port is not configured correctly, for Plug-in: <plugin name> in Server-Plugin-Alias entry ar.cfg.
    • If corresponding entries do not exist in the pluginsvr_config.xml file and the ar.cfg (or ar.conf) file, the check fails and displays the following error message:
      Configuration for plug-in: <plugin name> is missing in ar.cfg.
  • The check validates if any duplicate entries exist in the pluginsvr_config.xml for a single plug-in. If duplicates exist, the check displays a warning message.

Note:
The BMC Remedy Configuration Check utility considers that pluginsvr_config.xml is always present in the %ATRIUMCORE_HOME%\cmdb\plugins\shared\ directory.

Corrective actions
  • Ensure that the plug-in port specified in the Centralized Configuration matches the plug-in port specified in the pluginsvr_config.xml file.
  • For all plug-ins configured in the pluginsvr_config.xml file, ensure that the files specified in the <filename> and <pathelement> parameters actually exist.
  • For all plug-ins configured in the pluginsvr_config.xml file, ensure that a corresponding entry is present in the Centralized Configuration. Also, ensure that the port in the pluginsvr_config.xml file matches the port in the Centralized Configuration.
  • Ensure that no duplicate entries exist in the pluginsvr_config.xml for a single plug-in.

To more information on using centralized configuration form, see Centralized configuration .

Go to top

Reconciliation Engine Private Queue Check

DescriptionThis check validates whether the Reconciliation Engine private queue is configured to use either port 390698 or port 390699.
TypeConfiguration check
Check performed and expected result
  • In the ar.cfg (or ar.conf) file, if the value of the Reconciliation Engine private queue is set to any port other than 390698 or 390699, the check fails and displays the following error message:
    Reconciliation Private Port <port number> is not set according to recommended values.
  • In the ar.cfg (or ar.conf) file, if the value of the Reconciliation Engine private queue is not set, the check fails and displays the following error message:
    Private port is not configured for Reconciliation Engine.
  • In the ar.cfg (or ar.conf) file, if the parameter for the Reconciliation Engine private queue is specified but the parameter for BMC Remedy AR System private queue is not specified, the check fails and displays the following error message:
    AR private port is not configured for RE-Private-Port <Port no>.
Corrective actions
  • In the Centralized Configuration form, set the value of Reconciliation Engine private queue to either port 390698 or port 390699.
  • In the Centralized Configuration form, specify the value of the AR System private queue.

To more information on using centralized configuration form, see Centralized configuration .

Go to top

Related topics

BMC Remedy AR System checks

BMC Remedy ITSM checks

BMC Remedy ITSM Process Designer checks

BMC Service Level Management checks

BMC Service Request Management checks

Unified Data Management (UDM) checks

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

Comments