This documentation supports the 9.1 version of BMC Remedy ITSM Deployment.

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

BMC Remedy AR System checks

The BMC Remedy Configuration Check utility performs the following checks on the BMC Remedy Action Request (AR) System. The expected results are described in addition to corrective actions you can take if a check fails.

Best Practice

BMC recommends that you run all the pre-upgrade checks before you upgrade to a later version. Use the version of the utility to which you want to upgrade. Address errors or warnings because these issues might prevent a successful upgrade. Some of the AR System checks are initiated by the installer.

 The following checks are described:

Approval Socket Test

Description

This check verifies that both the Approval-RPC-Socket and Plugin-Loopback-RPC-Socket parameters are set to a valid number, but are not the same value. For more information, see Configuring private queue threads and KA 000114508.

Type

Configuration check 

Check performed and expected result
  • If only the Approval-RPC-Socket or the Plugin-Loopback-RPC-Socket parameter is configured in the Centralized Configuration, the check is successful.
  • If both the Approval-RPC-Socket and Plugin-Loopback-RPC-Socket parameters are configured in the Centralized Configuration, and both the parameters are configured to different RPC program values, the check is successful.
  • If both the Approval-RPC-Socket and Plugin-Loopback-RPC-Socket parameters in the Centralized Configuration file are set to same RPC program values, the check fails  and displays a warning message.
Corrective action

Ensure that both Approval-RPC-Socket and Plugin-Loopback-RPC-Socket parameters in the Centralized Configuration file are configured to different RPC program values. See Configuring server settings for BMC Remedy Approval Server logging and loopback calls

Go to top

AR System Email Engine Service Name Check

Description

(Microsoft Windows only) This check verifies the following:

  • The value of BMC_EMAIL_SERVICE_NAME parameter in the <ARSystemInstallDir>\ARSystemInstalledConfiguration.xml file matches with the value of BMC Remedy Email Engine service from services.msc.
    <ARSystemInstallDir> is the location where the AR System server is installed. The default location is C:\Program Files\BMC Software\ARSystem .
  • The installer ensures that the location of AREmail directory is valid, and this is an additional validation.
  • The location of the AREmail directory matches the value of the the Current Directory parameter from the Microsoft Windows registry entry.
Type

Configuration check 

Check performed and expected result

The check is successful if both the following conditions are met:

  • The value of the BMC_EMAIL_SERVICE_NAME parameter from ARSystemInstalledConfiguration.xml file matches the value of BMC Remedy Email Engine service from services.msc.
  • The location of the AREmail directory matches with the Current Directory parameter from Microsoft Windows registry entry.

If any of the conditions is not met, the check fails and displays an error message.

Corrective action

If the value of BMC_EMAIL_SERVICE_NAME parameter from ARSystemInstalledConfiguration.xml file does not match with the value of BMC Remedy Email Engine service from services.msc, delete the BMC Remedy Email Engine service. Then, proceed with the upgrade. During the upgrade, the installer will create a new BMC Remedy Email Engine service in services.msc. Alternatively, you can update the service name in the ARSystemInstalledConfiguration.xml file.

The default location of AREmail directory is C:\Program Files\BMC Software\ARSystem\AREmail .
To find the registry entry, perform the following steps:

  1. Open the Microsoft Windows Registry Editor.
  2. Navigate to HKEY_LOCAL_MACHINE > SYSTEM > ControlSet001 > Services > BMC Remedy Email Engine > Parameters.
    Note the value of parameter Current Directory.
    The location of the AREmail directory must match the value of the Current Directory parameter.

Go to top

ASJ Thread Count Test

Description

This check verifies that the ASJ-Thread-Count parameter is configured to a nonzero value in the Centralized Configuration.

ASJ Thread count s pecifies the total number of worker threads that process various approval requests.

Type

Configuration check 

Check performed and expected result
  • If the value of  ASJ-Thread-Count parameter is set to a nonzero value, the check is successful. 
  • If the value of  ASJ-Thread-Count parameter is set to 0, the check fails and displays an error message.
Corrective actionEnsure that the value of  ASJ-Thread-Count parameter is set to a nonzero value in the Centralized Configuration.

Go to top

Attachment Extension Security Exemption Check

Description

This check verifies that the files with the required list of extensions specified in the ars_check.xml file can be downloaded by the installer while performing an installation or upgrade, and the extensions are added in the Supported-Extensions list of the AR System server.

You must manually add the required list of extensions in the ars_check.xml file. The ars_check.xml file is bundled with the BMC Remedy Configuration Check utility and exists in the config directory. Add the extensions to the <param name> parameter.

Extension to <param name> parameter
  • To add the extensions in the Supported-Extensions list of AR System server, configure the Attachment Security parameters from the AR System Administration > Server Information > Attachment Security tab.
    Based on the Attachment Criteria and the Comma separated list of limit extensions that you specify on the Attachment Security tab, the mode is set as follows:
    • Mode 0 — Disabled
    • Mode 1 — Enabled, but allows only the files with extensions specified in the Comma separated list of limit extensions field. Files with other extensions are not allowed.
    • Mode 2 — Enabled, but does not allow files with extensions specified in the Comma separated list of limit extensions. Files with all other extensions are allowed.
Type Pre-upgrade check
Check performed and expected result

Depending upon the configuration of Attachment Criteria, this check performs the following checks:

  • If Attachment Criteria is disabled (Mode 0), the check is successful.
  • If Attachment Criteria is enabled in Mode 1, and the required extensions are present in the Comma separated list of limit extensions field, the check is successful.
  • If Attachment Criteria is enabled in Mode 1, and the required extensions are not present in the Comma separated list of limit extensions field, the check fails, and displays an error message.
  • If Attachment Criteria is enabled in Mode 2, and the required extensions are not present in the Comma separated list of limit extensions field, the check is successful.
  • If Attachment Criteria is enabled in Mode 2, and the required extensions are present in the Comma separated list of limit extensions field, the check fails, and displays an error message.
Corrective action

Ensure that any one of the following conditions are true:

  • The Attachment Criteria is disabled (Mode 0).
  • If Attachment Criteria is enabled in Mode 1, the required extensions are included in the Comma separated list of limit extensions field.
  • If Attachment Criteria is enabled in Mode 2, the required extensions are not included in the Comma separated list of limit extensions field.

Go to top

Filter Correction Check 

Description

In BMC Remedy AR System 8.1.02, the Ap:Alt-SetPermissions filter was introduced in one of the hotfixes (HF\pinatubo\CertifiedHotFixes\8.1.02\Multitenancy\SW00488367-ApprovalServer\MultiTenancy_Approval_Hotfix_81SP2). The same filter in 9.1.02 is included with an upper case 'P' in the form name: AP:Alt-SetPermissions. When upgrading from 8.1.02 with that hotfix to 9.1.02, you encounter the following error:

"ERROR RIKMain  - 382 The value(s) for this entry violate a unique index that has been defined for this form"

The check validates the casing in the AP:Alt-SetPermissions filter name.

TypePre-upgrade check
Check performed and expected result

When upgrading from 8.1.02 with that hotfix to 9.1.02, the check detects a lower case 'p' in the AP:Alt-SetPermissions filter name and displays the following error message:

Please correct the filter name from Ap:Alt-SetPermissions to AP:Alt-SetPermissions. Execute the following SQL statement to fix it:

UPDATE filter SET name = 'AP:Alt-SetPermissions', resolvedName = 'AP:Alt-SetPermissions' WHERE name = 'Ap:Alt-SetPermissions';

Corrective action

Execute the SQL statement provided in the preceding row to update the filter name.

Go to top

Dependent Library Check for Linux and Solaris

Description

This check verifies that the following mandatory packages required for running the BMC Remedy AR System server reside on a computer. 

For Linux

  • libstdc++.x86_64
  • libstdc++
  • compat-libstdc++-33
  • compat-libstdc++-33.i686
  • glibc

The check also verifies that the libstdc++.so.6 library resides in the \lib or \usr\lib directory for Linux.

For Solaris

  • system/picl
  • compatibility/ucb

Notes:

  • You can configure the name of the mandatory file in the ars_check.xml file.
    The ars_check.xml file is bundled with the BMC Remedy Configuration Check utility and resides in the config directory.
Type Pre-upgrade check
Check performed and expected result
  • If the libstdc++.so.6 (for Linux) is present in the \lib or \usr\lib directory and the required packages are present, the check is successful.
  • If the libstdc++.so.6 (for Linux) is not present in the \lib or \usr\lib directory or any of the mandatory packages is missing, the check fails and displays an error message.
Corrective action
  • Download the packages from the respective product sites of Linux and Solaris.
  • Ensure that the libstdc++.so.6 library required for running the BMC Remedy AR System server on a Linux computer exists in the \lib or \usr\lib directory.

Go to top

FTS Indexes Check

Description

This check investigates whether Lucene indexes used for search operations are corrupted or inconsistent. The read operation fails when the index is corrupted.

Type

Configuration check 

Check performed and expected result
  • If the Lucene indexes are valid, the check is successful.
  • If the Lucene indexes are corrupted or inconsistent, the check fails and displays an error message.
Corrective action

If the Lucene indexes are corrupted or inconsistent, perform the following actions:

  1. Create a backup of existing indexes from the directory where the indexes are located.
    The default location is <ARSystemInstallDir>/ARSystem/ftsconfiguration/collection directory.
  2. Delete the contents of the directory where the indexes are located.
  3. Proceed with the upgrade.
  4. After the upgrade is complete, perform the global re-index. (On AR System Administration Console, navigate to System > General > Server Information. On the FTS tab, select the Reindex checkbox.). Ensure that the server is running when you perform global re-index.

Go to top

Incorrect Overlay Field Mapping Check

Description

This check verifies that the form corresponding to a field or view in overlay mode is also in the overlay mode.

TypePre-upgrade check
Check performed and expected result
  • If the field or view is in an overlay and the corresponding form is also in the overlay mode, the check is successful.
  • If the field or view is in an overlay, but the corresponding form is not in the overlay mode, the check fails with an error and displays an error message containing the list of fields and forms with issues:

    AR metadata in database seems to have some issues for <Schema_name, Schema_ID, and Field_ID> and will cause failure in upgrade. Please contact BMC customer support team to get these issues resolved before starting the upgrade.

    Where, <Schema_name, Schema_ID and Field_ID> is the list of forms and fields that have overlay issues.
Corrective actionIf the field or view is in overlay mode, but the corresponding form is not in overlay mode, you must contact BMC Support to resolve this issue.

Go to top

Join Form Validation Check

 

Description

This check verifies that no join forms with invalid customizations exist in the system, where the primary and secondary forms are different in Base and Overlay.

TypePre-upgrade check
Check performed and expected result
  • If forms do not have invalid customization and all primary and secondary forms in Base and Overlay are the same, the check is successful.
  • If forms with invalid customizations are present and the primary and secondary forms in Base and Overlay are not same, the check fails and displays an error message with the list of Schema IDs of forms that contain invalid customizations.
Corrective action

Delete the overlays of the join forms that contain the invalid customizations. See Deleting overlay objects

Go to top

Network Address Check for Server

Description

This check verifies that the IP address configured for the server (in the hosts file) is a valid physical network address (not a loopback address 127.0.0.1 or 127.0.1.1). Connection issues might occur in a server group environment. If you configure the server address as 127.0.0.1 or 127.0.1.1 in the host file, the other servers in the server group environment cannot communicate with this server.  

Note: This check is specific to Linux system.

Type

Pre-upgrade check, configuration check

Check performed and expected result
  • If an IP address is found, and it is other than 127.0.0.1 and 127.0.1.1, the check is successful.
  • If an IP address is not found, the check is successful.
  • If an IP address is found and it is either 127.0.0.1 or 127.0.1.1, the check fails.
Corrective ActionConfigure the IP address to a physical IP address identifiable over the network.

Go to top

Next Request ID Block Size Check

Description

This check verifies that the value of Next Request ID Block Size is greater than or equal to 100. For information on the benefits of setting the block-size, see Allocating blocks of Next-IDs for faster create operations

Type

Configuration check 

Check performed and expected result
  • If the value of Next Request ID Block Size is set to greater than or equal to 100, the check is successful.
  • If the value of Next Request ID Block Size is less than 100, the check fails and displays an error message.
Corrective ActionOn the Configuration tab of the Server Information page in the AR System Administration Console, set the value of Next Request ID Block Size to 100.

Go to top

Object Reservation Check

DescriptionThis check verifies that the BMC Remedy AR System object reservation on the target system is ON or OFF. Object reservation supports team development of applications by enabling one developer to prevent other developers from modifying objects. When developing an application with others, you need to prevent them from overwriting your object changes. To do this, you need to use object reservation. For example, before starting a development task, you can reserve the objects you plan to change. After completing and testing the changes, you can release the objects, so that others can work on them.
TypePre-upgrade check
Check performed and expected result
  • If object reservation is OFF, the check is successful.
  • If object reservation is ON, the check verifies that any objects are reserved:
    • If any objects are reserved, the check fails and reports the names of first five reserved objects in an error message.
    • If no objects are reserved, the check displays a warning message.
Corrective action

Release all reserved objects. From the AR System Server Administration Console, set object reservation to OFF. See Using object reservation

Go to top

OS Compatibility Check

Description

This check validates whether the system on which you are installing is a supported operating system. It checks for OS compatibility according to the OS Supportability Matrix document.

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

The check gets the current version of the OS on which the BMC Remedy Configuration Check utility runs and compares it with the minimum supported values. The following list shows minimum supported versions of the supported operating systems:

  • Microsoft Windows server 2008 R2 x64 version 6.1
  • RedHat Enterprise Linux 6.5 x64
  • CentOS 6.5 (x64)
  • SUSE Enterprise Linux Server 11 SP3
  • Oracle Solaris 10

Depending on the OS type, this check performs the following checks:

  • If the OS on which the BMC Remedy AR System is installed is not supported, the check displays the following error message:
    <OS name> is not a supported operating system for installing AR System Server. Please refer to the Installation Guide for more details on supported hardware and operating systems.
  • If BMC Remedy AR system is installed is Linux on 32-bit platform, the check displays the following error message:
    AR Server installation cannot continue on 32bit platform.  Install on 64 bit platform.
  • If the OS on which BMC Remedy AR System is installed is a version that is earlier than the recommended version, the check displays a warning message for that particular operating system, with the minimum version recommended according to the OS Supportability Matrix document.
Corrective action

Ensure that the version of the operating system of the computer on which BMC Remedy AR System is installed is the same or later than the minimum supported version. BMC Solution And Product Availability And Compatibility Utility (SPAC)  

Go to top

Read-Only-Tran Check

 

Description

This check verifies that  the Read-Only-Tran-Off parameter in ar.cfg (ar.conf) is set to T (True).

Type

Configuration check  

Check performed and expected result
  • If the Read-Only-Tran-Off parameter is not configured in the ar.cfg (ar.conf) file, or it is configured as T, the check is successful.
  • If the Read-Only-Tran-Off parameter is configured in the ar.cfg (ar.conf) file as F, the check fails and displays an error message.
Corrective actionEnsure that the Read-Only-Tran-Off parameter is configured in the Centralized Configuration and the value is set to T (True).

Go to top

RPC Check

Description

(Solaris only) This check verifies that the RPC-Non-Blocking-IO parameter in the ar.cfg (ar.conf) is set to F (False).

Type

Configuration check 

Check performed and expected result
  • If RPC-Non-Blocking-IO is set to F (False), the check is successful.
  • If RPC-Non-Blocking-IO is set to T (True), the check fails and displays a warning message.
Corrective actionEnsure that the RPC-Non-Blocking-IO parameter in the Centralized Configuration is set to F (False).

Go to top

Secondary Server Down Check

Description

This validation ensures that the secondary AR System server or servers are not running while the primary AR System server is being upgraded. The installer automatically brings the secondary AR System server(s) down while the primary AR Server is being upgraded.

TypePre-upgrade check
Check performed and expected result
  • If the secondary AR System server is not running when the primary AR System server is being upgraded, the check is successful.
  • If the secondary AR System server is running when the primary AR System server is being upgraded, the check fails and displays an error message.

Note: If you are running the upgrade in Zero downtime (ZDT) mode, you can ignore this check.

Corrective action

The installer automatically brings the secondary AR System server(s) down while the primary AR Server is being upgraded.

Go to top

System Information Check

DescriptionThis check validates the configuration of the system on which BMC Remedy AR System is installed.
Type

Configuration check 

Check performed and expected result

This check displays the following information:

  • System configuration information such as OS, architecture, and OS version
  • BMC Remedy AR System database type, version, and character set
Corrective actionBecause this check provides information message, no corrective action is required.

Go to top

Corrupted Placeholder Schema Check 

Description

This check verifies that no database table exists for a placeholder form.

TypePre-upgrade check
Check performed and expected result
  • If no corresponding database table exists for any of the placeholder forms, the check is successful.
  • If database tables corresponding to any of the placeholder forms exist, the check fails and displays an error message with a list of corrupted placeholder form names.
Corrective actionDelete the database tables corresponding to the placeholder forms listed in the error message.

Go to top

DB Configuration Check

Description

This check validates the following attributes of the database server and produces a report of the actual and recommended values:

(For MS SQL)

  • READ_COMMITTED_SNAPSHOT is set to ON.
  • XACT_ABORT option is OFF.

(Oracle)

Note: In order to check the actual value of parameter, the AR DB user requires access of Oracle DB system objects.

Use the following query to grant access to the AR DB user:

 grant select any dictionary to aradmin

  • MEMORY_TARGET is set to 16 GB
  • SGA_TARGET is set to 10 GB
  • DB_CACHE_SIZE is set to 7 GB
  • SHARED_POOL_SIZE is set to 3 GB
  • PGA_AGGREGATE_TARGET is set to 6 GB
  • CURSOR_SHARING is set to EXACT
  • _B_TREE_BITMAP_PLANS is set to False

(AR DB Machine)

  • CPU Cores is set to 16
  • RAM Memory is set to 32 GB
  • Disk Space is set to 200 GB

Note: In some cases, a failure of upgrade is observed if the parameters are not set as per the recommendations.

TypePre-upgrade check
Check performed and expected result

If any of the sizing parameters are less than or different from their recommended setting, the check fails. Depending on the parameters that fail, either an error or a warning is displayed. You can compare the actual value with the recommended value in the report that is displayed.

Corrective action

Perform the following corrective steps:

  1. Stop the AR System server.
  2. Depending on which database you are using and which parameters need to be corrected, use the following examples to set the recommended values:

    Read Committed SnapshotSELECT is_read_committed_snapshot_on FROM sys.databases where name = 'ARSystem';   ALTER DATABASE ARSystem SET READ_COMMITTED_SNAPSHOT ON;
    XACT_ABORT is ONDBCC USEROPTIONS; SET XACT_ABORT OFF;
    SGA_TARGET

    SELECT value  from v$parameter where name='sga_target' 

    alter system set sga_target=10G

    DB_CACHE_SIZE

    SELECT value  from v$parameter where name='db_cache_size'" 

    alter system set db_cache_size=7G

    SHARED_POOL_SIZE

    SELECT value from v$parameter where name='shared_pool_size' 

    alter system set shared_pool_size=3G

    PGA_AGGREGATE_TARGET

    SELECT value  from v$parameter where name='pga_aggregate_target' 

    alter system set pga_aggregate_target=3G

    CURSOR_SHARING

    SELECT value  from v$parameter where name='cursor_sharing' 

    alter system set cursor_sharing='EXACT'

    _B_TREE_BITMAP_PLANS
    ALTER SYSTEM SET "_b_tree_bitmap_plans"=false SCOPE=SPFILE;
  3. Restart the AR System server.

Go to top

Database Compatibility Check

Description

This check validates the database compatibility with the lowest supported database version. The following databases are supported:

  • Microsoft SQL Server 2008 R2
  • Oracle 11gR2 (11.2.0.3.0)
TypePre-upgrade check
Check performed and expected result
  • If the lowest supported database version check is successful, the following message is displayed:
    Prechecker for Database version compatibility successful.
  • If the lowest supported database version check fails, the following message is displayed:
    Database version was detected as <your db version>.
    The installation program requires database vendor version <b>[arg1]</b> or later.
Corrective ActionUpgrade the database to the supported version. See Compatibility matrix.

Go to top

Database Transactional Space Availability Check

Description

This check verifies that the available transactional space that is configured for the AR Server Database is smaller than the available transactional space specified as an input parameter to the BMC Remedy Configuration Check utility.

Type Pre-upgrade check
Check performed and expected result
  • For SQL Server database:
    • If the available transactional space is more than the specified value, the check is successful.
    • If the available transactional space is smaller than the specified value, the check fails with an error, and displays an error message.
  • If the database is Oracle, the check fails and displays a warning message that notifies you to perform the check manually.
Corrective action

Ensure that the available transactional space that is configured for the AR Server Database is not smaller than the available transactional space specified as an input parameter. You can specify the value of available transactional space as an input to the BMC Remedy Configuration Check utility in the ars_check.xml file. The ars_check.xml file is bundled with the BMC Remedy Configuration Check utility, and exists in the config directory.

Note: This check verifies that the available transactional space is larger than the recommended minimum.

Go to top

DB-OS Unicode Lang Check

DescriptionThis check verifies that the BMC Remedy AR System and database character sets match. If the character sets do not match, when you install any Unicode languages, the installer may import language-specific definition files, but the Mid Tier may not be able to display them properly.
TypePre-upgrade check, configuration check
Check performed and expected result
  • If both the database and BMC Remedy AR System character sets match, the check is successful.
  • If the database and BMC Remedy AR System character sets do not match, the check fails and displays an error message.

For example, if the database character set is Unicode, the AR System locale must be set to include the UTF character set.

A DBA can run the following query for validation:

Corrective action

Set the BMC Remedy AR System locale to include a character set that matches the database character set. See Setting the Locale tab

Go to top

GetList Max Entries Check

DescriptionThis check verifies that the value of Max Entries returned by GetList exceeds 2000. The Max Entries returned by GetList parameter sets the maximum number of requests that a search can return. BMC recommends always setting this parameter because unqualified searches can yield enormous result sets. This leads to a large amount of memory allocated to each BMC Remedy AR System server thread that processes this type of search. Additionally, queries will take longer to execute and use more database resources.
Type

Configuration check 

Check performed and expected result
  • If Max Entries returned by GetList (Max-Entries-Per-Query) is set to greater than 0 and less than or equal to 2000, the check is successful.
  • If Max Entries returned by GetList (Max-Entries-Per-Query) is set to 0 or greater than 2000, the check fails and displays a warning.

Note: Starting in 9.1 SP2, the default value for Max-Entries-Per-Query is 2000. So, if this setting is missing from ar.cfg and Centralized Configuration, the value of 2000 is used.

Corrective actionOn the Configuration tab of the Server Information page in the AR System Administration Console, set the value of Max Entries returned by GetList to 2000.

Go to top

Meta-data Unique Values Check

Description

This check verifies that the metadata tables have unique key-value combinations prior to applying unique indexes in the upgrade. The check also considers overlays created over forms. 

Type

Pre-upgrade check, configuration check 

Check performed and expected result

This check provides a list of all metadata tables and indexes that contain nonunique values.

 List of tables and indexes that are verified for unique values
  • actlink_mapping
  • actlink_mapping_ind
  • actlink_group_ids
  • actlink_group_ids_ind
  • arctr_group_ids
  • arctr_group_ind
  • arctr_subadmin
  • arctr_subadmin_ind
  • cntnr_ownr_obj
  • cntnr_ownr_ind
  • schema_group_ids
  • schema_group_ids_ind
  • subadmin_group
  • subadmin_group_ind
  • schema_index
  • schema_index_ind
  • filter_mapping
  • filter_mapping_ind
  • escal_mapping
  • escal_mapping_ind
  • field_permissions
  • field_permissions_ind
Corrective action

If nonunique key values are found in the listed metadata tables, eliminate all duplicate records and retain only one. Perform the following corrective actions:

  1. Examine the records with duplicate keys.

  2. Select records to remove.

  3. Using the SQL tool, remove the extra records so that only one record remains for each key-value combination.

  4. Use database queries to identify duplicate entries.
Example — Database query for table actlink_mapping
SELECT
COUNT(*),schemaId,actlinkId FROM actlink_mapping GROUP BY schemaId,actlinkId
HAVING COUNT(*) > 1

Go to top

SQL Replication ON Check

DescriptionThis check validates that SQL replication is OFF for any of the tables.
TypePre-upgrade check
Check performed and expected result

If the SQL replication is ON for any of the tables, the check lists the names of all such tables.

Corrective action

Ensure that SQL replication is OFF for all tables.

Note: Replication can cause issues when importing definitions and altering DB views. So, replication cannot be enabled during the upgrade.

Go to top

CarteHeapSizeCheck

Description

This check verifies that the Carte heap size in Centralized Configuration is set to a minimum value of 1024 MB. If this is not done, you might face an out of memory error. In this case, the Carte server might not come up.

Type

Configuration check  

Check performed and expected result
  • If the Carte heap size is specified in the Centralized Configuration file and the value is not less than 1024 MB, the check is successful.
  • If the Carte heap size is not specified in the  Centralized Configuration file, or even if specified, but the value is less than 1024 MB, the check fails and displays a warning message.

You need to check the following entries from the server:

(Microsoft Windows) armonitor.cfg
(Linux) armonitor.conf
Corrective actionEnsure that the Carte heap size parameter is specified in the armonitor.cfg file or the armonitor.conf file and is set to a minimum value of 1024 MB.

Go to top

Collection Directory Space Availability Check for FTS Check

Description

This check verifies that the free space available in the FTS index collection directory is more than twice its current size. For example, if the current size of the FTS index collection directory is 1GB, at least 2GB of free space must be available in the directory. During upgrade, the usage of the FTS index collection directory might double and upgrade might fail if enough free space is not available.

The default location of the FTS index collection directory is <AR_INSTALL_DIR>/ftsconfiguration/collection, where <AR_INSTALL_DIR> is the directory where BMC Remedy AR System is installed.

TypePre-upgrade check, configuration check
Check performed and expected result
  • If the free space available in the FTS index collection directory is more than twice its current size, the check is successful.
  • If the free space available in the FTS index collection directory is smaller than twice its current size, the check fails and displays an error message.
Corrective actionEnsure that sufficient free space is available on the disk where the FTS index collection directory is located.

Go to top

AR Config Params Check

Description

This check verifies that the ar.cfg or ar.conf parameters for AR Server are specified according to the recommended values.

 Click here to expand the list of ar.cfg parameters
  • Plugin-ARDBC-Threads is checked only if the existing version is prior to 9.0.
  • Plugin-AREA-Threads is checked only if the existing version is prior to 9.0.
  • Plugin-Filter-API-Threads is checked only if the existing version is prior to 9.0.
  • Allow-Unequal-Queries
  • Allow-Guest-Users
  • Alternate-Approval-Reg
  • Approval-RPC-Socket
  • Authentication chaining mode
  • Cache-Mode
  • Debug-mode
  • Delay-Recache-Time
  • External-Authentication-Return-Data-Capabilities
  • Filter-Max-Total
  • Filter-Max-Stack
  • Large-Result-Logging-Threshold
  • Max-Entries-Per-Query
  • Max-Log-History
  • Max-Log-File-Size
  • Next-ID-Block-Size
  • Num-Preload-Threads
  • Num-Preload-Schema-Segments
  • Oracle-Clob-Storage-In-Row
  • Private-RPC-Socket
  • Plugin-Log-Level
  • Plugin-Loopback-RPC-Socket
  • Save-Login
  • Server-Side-Table-Chunk-Size
  • Server-Plugin-Default-Timeout
  • Server-Group-Signal-Option
  • Server-Group-Member
  • Server-Side-Table-Chunk-Size
  • Submitter-Mode
  • Version-Control-Object-Modification-Log-Mode
  • Version-Control-Object-Modification-Log-Save-Definition-Files

Note: The recommended values are the default values.

Type

Pre-upgrade check

Check performed and expected result
  • If the ar.cfg or ar.conf parameters are set to any value other than the recommended value, the check fails and displays the recommended values along with the description of the configuration parameter.
  • If the parameter values are according to the recommended values, the check is successful.
Corrective action
  • Specify the recommended values for the Private RPC Socket. You can obtain them from the table provided in Configuring private queue threads.
  • Specify the recommended values for the remaining parameters. You can obtain them from the Configuration Checker report.

Go to top

AR Configuration JAVA Parameters Check

Description

This check is run only if you are at BMC Remedy AR System server 9.0 or later. This check verifies that the JVM options set in the AR Server Config file are according to the following recommended values. If the parameter exists and is according to the recommendation, the HTML report does not notify the parameter.

The following values are specified for a medium-size environment.

  • -XX:+UseCompressedOops
  • -XX:+UseConcMarkSweepGC
  • -XX:+UseParNewGC
  • -XX:NewRatio=2
  • -XX:MaxMetaspaceSize=512m
  • jvm.minimum.heap.size=8589934592
  • jvm.maximum.heap.size=8589934592


Type

Pre-upgrade check, configuration check

Check performed and expected result
  • If any parameter value is less than the recommended value, a warning is displayed.
  • If any parameter value is missing, a warning is displayed.
  • If all the parameter values are present and are according to the recommended values, the check is successful.
Corrective action
  1. Stop BMC Remedy AR Server.
  2. Access the AR Server Config file:
    • (For Windows) <BMC_AR_SERVER_HOME>/arserver.config
    • (For UNIX) <BMC_AR_SERVER_HOME>/bin/arserverd.conf 
  3. Perform one of the following actions:

    • If the following parameters are not specified, add them to the AR server configuration file:   

      • -XX:+UseCompressedOops
      • -XX:+UseConcMarkSweepGC
      • -XX:+UseParNewGC
      • -XX:NewRatio=2
      • -XX:MaxMetaspaceSize=512m

      To add a parameter, check the JVM options section of the configuration file and add the option with the next number in sequence.

      # Sample - JVM options (number indicates option order)
      jvm.option.1=-javaagent:./lib/spring-instrument-4.1.2.RELEASE.jar
      .
      .
      .
      jvm.option.15=-XX:HeapDumpPath=./Logs
      jvm.option.16=-Djava.library.path=./lib/upgradeutils/sqlauth/x64

      In the sample above, the "next" number in sequence is 17. So, the next option is added as follows: 

      jvm.option.17=-XX:+UseCompressedOops

      The next jvm option will be as follows:

      jvm.option.18=-XX:+UseConcMarkSweepGC

      Note: Ensure there are no trailing spaces before or after the parameters. An option with whitespace is not recognized. For example, jvm.option.18=- XX:+UseConcMarkSweepGC  or jvm.option.18=-XX+UseConcMarkSweepGC(space) is not recognized.

    • If the parameter exists, but its value is not the recommended value, modify the value in the existing parameter.

  4. Start BMC Remedy AR Server.

For more details on Java heap dumps (and thread dumps) for AR Server, see https://bmcsites.force.com/casemgmt/sc_KnowledgeArticle?sfdcid=000101754 .

Go to top

AR Machine Parameter Check

Description

This check verifies that the BMC Remedy AR Server adheres to the recommended values for the following parameters:

  1. CPU Core
  2. RAM memory
  3. Disk space

Note: The preceding parameters are applicable per server.

Type

Pre-upgrade check, configuration check

Check performed and expected result
  • If any parameter value is less than the recommended value, a warning is displayed
  • If all the parameter values match or exceed the recommended value, the check is successful.
Corrective action

Use the minimum recommended hardware as suggested. BMC recommends that you must retain the free disk space until the upgrade is complete.

Go to top

Repeat Parameter Check

Description

This check verifies that no duplicate configuration parameters exist in the ar.cfg (ar.conf) file.

Type

Pre-upgrade check, configuration check  

Check performed and expected result
  • If duplicate configuration parameters do not exist in the ar.cfg (ar.conf) file, the check is successful.
  • If duplicate configuration parameters exist in the ar.cfg (ar.conf) file, the check fails and displays a warning message containing duplicate parameters.
Corrective actionRemove duplicate configuration parameters, if any, in the Centralized Configuration.

Go to top

Java Version Check

DescriptionThis check validates the version of Java on the machine on which you run the BMC Remedy Configuration Check utility. This is one of the system-requirements. For details, see System requirements.
TypePre-upgrade check, configuration check
Check performed and expected result
  • If Java 8 update 45 or later is installed on the computer, the check is successful.
  • If the version of Java is earlier than Java 8 update 45, the check fails and displays an error message. 

Corrective actionEnsure that Java 8 update 45 or later is installed on the machine on which you are running the BMC Remedy Configuration Check utility.

Go to top

Platform (AR System) Version Check

Description

This check verifies that the current version of the AR System server is supported by the installer for upgrade.

Note:

  • You can configure the minimum version of the AR System server in the ars_check.xml file.
    The ars_check.xml file is bundled with the BMC Remedy Configuration Check utility, and resides in the config directory.
Type Pre-upgrade check
Check performed and expected result
  • If the version of the current AR System server is the version supported by the installer, the check is successful.
  • If the version of the current AR System server version is earlier than the minimum version supported by the installer, the check fails and displays an error message.
Corrective actionEnsure that the version of the current AR System server is not earlier than the minimum version supported by the installer.

Go to top

Related topics

BMC Atrium Core 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

  1. Sirisha Dabiru

    Hi Subhashini Natarajan,

    Here is the response for the following comment:

    CommentResponse

    In AR Machine Parameter check, what is the path where the utility is checking for available disk space?

    We have 105GB free memory in /opt/bmc and 44GB free memory in /remedyapp. But, it shows 20GB as actual value.

    The utility checks the disc space available in the AR installation path.

    Regards,

    Sirisha

    Mar 20, 2019 04:27