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

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

BMC Remedy AR System checks

This topic provides information about the checks performed by the BMC Remedy Configuration Check utility for BMC Remedy Action Request System. 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. Some of the AR System checks are initiated by the installer.

The following checks are described:

Admin Operations Check

Description

(Version 9.0) In a server group environment, this check verifies whether administrator rights are enabled on the primary server being upgraded, and disabled on all other secondary servers.

Note: If you run the BMC Remedy Configuration Check utility on the secondary servers before upgrading, this check might display an error message asking you to enable administrator rights on the secondary servers. Ignore this message and proceed with the upgrade. See SW00487530.

Type(Version 9.0) pre-upgrade check
Check performed and expected result
  • For primary server, this check performs the following checks:
    • If administrator rights are enabled, the check is successful.
    • If administrator rights are disabled, the check fails and displays an error message.
  • For secondary servers, this check performs the following checks:
    • If administrator rights are disabled, the check is successful.
    • If administrator rights are enabled, the check fails and displays an error message.
Corrective action

In a server group environment, ensure that administrator rights are enabled only on the primary server, which is upgraded first. For all secondary servers, ensure that the administrator rights are disabled.

To enable administrator rights on the primary server:

  1. Go to the Server Administration console > Server Information form > Configuration tab.
  2. Clear the Disable Admin Operations check box.

To disable administrator rights on the secondary servers:

  1. Go to the Server Administration console > Server Information form > Configuration tab.
  2. Select the Disable Admin Operations check box.

Go to top

Approval Socket Test

Description

(Version 9.0 or later) This check verifies whether the Approval-RPC-Socket and Plugin-Loopback-RPC-Socket parameters in the ar.cfg (ar.conf) file are configured to different RPC program values.

Type

(Version 9.0) pre-upgrade check

(Version 9.0 SP1) configuration check 

Check performed and expected result
  • If only the Approval-RPC-Socket or the Plugin-Loopback-RPC-Socket parameter is configured in the ar.cfg (ar.conf) file, the check is successful
  • If both the Approval-RPC-Socket and Plugin-Loopback-RPC-Socket parameters are configured in the ar.cfg (ar.conf) file, and both the parameters are configured to different RPC program values, the check is successful.
  • If both Approval-RPC-Socket and Plugin-Loopback-RPC-Socket parameters in the ar.cfg (ar.conf) 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 ar.cfg (ar.conf) file are configured to different RPC program values.

Go to top

AR System Email Engine Service Name Check

Description

(Version 9.0 or later) This check verifies the following:

  • The value of BMC_EMAIL_SERVICE_NAME parameter from 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 location of the AREmail directory matches with the value of the Current Directory parameter from the Microsoft Windows registry entry.
    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 Current Directory parameter.

Note: This check is specific to Microsoft Windows. For Linux, this check is not run.

Type

(Version 9.0) pre-upgrade check

(Version 9.0 SP1) 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 with 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 either of the conditions are 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.
  • If the location of the AREmail directory does not match with the Current Directory parameter from Microsoft Windows registry entry, there is no corrective action. The installer ensures that the location of AREmail directory is valid, and this is an additional validation.

Go to top

ASJ Thread count test

Description

(Version 9.0 or later) This check verifies whether the ASJ-Thread-Count parameter is configured to a non-zero value in the ar.cfg (ar.conf) file.

Type

(Version 9.0) pre-upgrade check

(Version 9.0 SP1) configuration check 

Check performed and expected result
  • If the value of ASJ-Thread-Count parameter is configured to a non-zero value, the check is successful. 
  • If the value of ASJ-Thread-Count parameter is configured as 0, the check fails with an error and displays an error message.
Corrective actionEnsure that the value of ASJ-Thread-Count parameter is configured to a non-zero value in the ar.cfg (ar.conf) file.

Go to top

Attachment Extension Security Exemption Check

Description

(Version 9.0 or later) This check verifies whether 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.

Notes:

  • 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.
  • 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(Version 9.0 or later) 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 either 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

CacheTest

Description

(Version 9.0) This check verifies whether the Cache mode of AR System server is set to Production.

Type(Version 9.0) pre-upgrade check
Check performed and expected result
  • If the Cache Mode is set to Production mode, the check is successful.
  • If the Cache Mode is set to Development mode, the check fails and displays a warning message.
Corrective action

Ensure that the Cache Mode is not set to Development.

To set the Cache mode to Production, perform the following steps:

  1. Go to the AR System Administration > Server Information > Configuration tab.
  2. Clear the Development Cache Mode check box.

 Go to top

CarteHeapSizeCheck

Description

(Version 9.0 or later) This check verifies whether the Carte heap size in armonitor.cfg is set to a minimum value of 1024 MB.

Type

(Version 9.0) pre-upgrade check

(Version 9.0 SP1) configuration check 

Check performed and expected result
  • If the Carte heap size is specified in the armonitor.cfg file and the value is not less than 1024 MB, the check is successful.
  • If the Carte heap size is not specified in the armonitor.cfg file, or even if specified, but the value is less than 1024 MB, the check fails and displays a warning message.
Corrective actionEnsure that the Carte heap size parameter is specified in the armonitor.cfg file and is set to a minimum value of 1024 MB.

 Go to top

Collection directory Space Availability Check for FTS Check

Description

(Version 9.0 or later) This check verifies whether the free space available in the FTS index collection directory is more than twice its current size. For example, if 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 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.

Type(Version 9.0 or later) pre-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 less 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.

Corrupted Placeholder Schema Check 

Info: This check is initiated by the installer.

  

Description

(Version 9.0 or later) This check verifies whether a database table exists for a placeholder form.

Type(Version 9.0 or later) pre-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 action Delete the database tables corresponding to the placeholder forms listed in the error message.

Go to top

Database Compatibility Check

Info: This check is initiated by the installer.

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)
Type(Version 9.0 or later) pre-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.

Go to top

Database Transactional Space Availability Check

Info: This check is initiated by the installer.

Description

(Version 9.0 or later) This check verifies whether the transactional space that is configured for the AR Server Database is less than the transactional space specified as an input parameter to the BMC Remedy Configuration Check utility. 

Notes: You can specify the value if 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.

Type (Version 9.0 or later) pre-upgrade check
Check performed and expected result
  • For SQL Server database:
    • If the transactional space is not less than the specified value, the check is successful.
    • If the transactional space is less 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 actionEnsure that the transactional space that is configured for the AR Server Database is not less than the transactional space specified as an input parameter.

Go to top

DB-OS Unicode Lang Check

DescriptionThis check verifies whether the BMC Remedy AR System and database character sets match.
Type(Version 9.0 or later) pre-upgrade check, configuration check
Check performed and expected resultDepending on the character sets defined for the database and BMC Remedy AR System, this check performs the following checks:
  • If both the database and 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.

Corrective actionSet the AR System locale to include a character set that matches the database character set.

Go to top

Dependent Library Check for Linux

Info: This check is initiated by the installer.

Description

(Version 9.0 or later) This check verifies whether the mandatory file (for example, libstdc++.so.6) required for running the AR System server on a computer with Linux operating system exists in the \lib or \usr\lib directory.

Notes:

  • This check is valid only for Linux operating system.
  • 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 is present in the config directory.
Type(Version 9.0 or later) pre-upgrade check
Check performed and expected result
  • If the mandatory file is present in the \lib or \usr\lib directory, the check is successful.
  • If the mandatory file is not present in the \lib or \usr\lib directory, the check fails with an error and displays an error message.
Corrective actionEnsure that the mandatory file required for running the AR System server on a computer with Linux operating system exists in the \lib or \usr\lib directory.

Go to top

FT index queue Check

Description

(Version 9.0 or later) This check validates whether the Private-RPC-Socket parameter for full text indexer is configured in the ar.cfg (ar.conf) file to 390602.

Type

(Version 9.0) pre-upgrade check

(Version 9.0 SP1) configuration check 

Check performed and expected result
  • If the Private-RPC-Socket parameter in the ar.cfg (ar.conf) file is configured to port 390602, the check is successful.
  • If the Private-RPC-Socket parameter in the ar.cfg (ar.conf) file is not configured to port 390602, the check fails and displays a warning message.
Corrective actionEnsure that the Private-RPC-Socket parameter in the ar.cfg (ar.conf) file is configured to port 390602 (for example, Private-RPC-Socket: 390602 2 2).

Go to top

FTS Indexes Check

Description

(Version 9.0 or later) This check verifies that the Lucene indexes used for search operations are not corrupted or inconsistent.

Type

(Version 9.0) pre-upgrade check

(Version 9.0 SP1) 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. When the upgrade completes, perform the global re-index. (On AR System Administration Console, navigate to System > General > Server Information. On the FTS tab, select the Reindex checkbox.)

Go to top

Incorrect Overlay Field Mapping Check

Description(Version 9.0 or later) This check validates that if the field or view is in overlay mode, the corresponding form must be in the overlay mode.
Type(Version 9.0 or later) pre-upgrade check
Check performed and expected result
  • If the field or view is overlay and the corresponding form is also in the overlay mode, the check is successful.
  • If the field or view is 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.

GetList Max Entries Check

DescriptionThis check verifies whether the value of Max Entries returned by GetList exceeds 2000.
Type

(Version 9.0) pre-upgrade check, configuration check

(Version 9.0 SP1) 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 an error message.
Corrective actionOn the Server Configuration page of the AR System Server Administration Console, set the Max Entries returned by GetList to 2000.

Go to top

Java Version Check

Info: This check is initiated by the installer.

DescriptionThis check validates the version of Java on the machine on which you run the BMC Remedy Configuration Check utility.
Type(Version 9.0 or later) pre-upgrade check, configuration check
Check performed and expected result
  • If Java 7 update 55 or later is installed on the computer, the check is successful.
  • If the version of Java is earlier than Java 7 update 55, the check fails and displays an error message.

Note: For Version 9.0 SP 1, the check verifies whether Java 8 update 45 or later is installed is on the computer. 

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

Go to top

Join Form Validation Check 

Description

(Version 9.0 or later) This check verifies whether join forms with invalid customizations exist in the system, where the primary and secondary forms are different in Base and Overlay.

Type (Version 9.0 or later) pre-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 actionDelete the overlays of the join forms that contain the invalid customizations.

Go to top

Meta-data Unique Values Check

Description

This check verifies whether the metadata tables have unique key value combinations prior to applying unique indexes in the upgrade. From Version 9.0 SP1 onwards, the check also considers overlays created over forms. 

Type

(Version 9.0) pre-upgrade check

(Version 9.0 SP1) 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 which 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 present in any of the listed metadata tables, reduce the number of records with the duplicate key values to 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.

Go to top

Network Address Check for Server

Description

This check verifies whether 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). 

Note: This check is specific to Linux system and was introduced in Version 9.0 SP1.

Type

(Version 9.0 SP 1) 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 Action Configure the IP address to a physical IP address identifiable over the network.

Go to top

Next Request ID Block Size Check

DescriptionThis check verifies whether the value of Next-Request-ID-Block-Size is greater than or equal to 25.
Type

(Version 9.0) pre-upgrade check, configuration check

(Version 9.0 SP1) configuration check 

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

Go to top

Object Reservation Check

Info: This check is initiated by the installer.

DescriptionThis check verifies whether the BMC Remedy AR System object reservation on the target system is ON or OFF.
Type(Version 9.0 or later) pre-upgrade check
Check performed and expected result
  • If object reservation is OFF, the check is successful.
  • If object reservation is ON, the check verifies whether 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 actionRelease all reserved objects. From the AR System Server Administration Console, set object reservation to OFF.

Go to top

Oracle Cursor Sharing Check

Description

This check verifies whether Oracle-Cursor-Sharing is set to FORCE or EXACT.

Note:
This check is specific to the Oracle Database. For other databases, the status of the check remains Not Run.

Type(Version 9.0) pre-upgrade check, configuration check
Check performed and expected result
  • If the configuration value of Oracle-Cursor-Sharing is set to FORCE or EXACT, the check is successful.
  • If the configuration value of Oracle-Cursor-Sharing is missing or set to any other value, the check fails and displays an error message.

    Note: The cursor_sharing=similar option has been deprecated in Oracle 11g and will be removed in version 12 per MOSC Note 1169017.1. BMC Remedy AR System support Oracle 11g and later.
Corrective action

Ensure that the value of CURSOR_SHARING in the database is set to EXACT.

Note: The value FORCE is used if the initARS.ora file includes the following line:CURSOR_SHARING=FORCE. It is  recommended that you set the initARS.ora setting to EXACT and set Oracle-Cursor-Sharing to EXACT.

To get the current value of CURSOR_SHARING, use the following SQL command:

SHOW PARAMETER CURSOR_SHARING;

If the returned value of CURSOR_SHARING is not EXACT, perform the following tasks:

  1. With the help of the database administrator, set the value of CURSOR_SHARING to EXACT.
  2. Manually set the value of Oracle-Cursor-Sharing in ar.conf (or ar.cfg) to one of the following values (so that it matches the value of CURSOR_SHARING):
    • Oracle-Cursor-Sharing: exact
  3. Restart the BMC Remedy AR System Server.

Go to top

OS Compatibility Check

Info: This check is initiated by the installer.

Description

This check validates all platforms supported by the installer. It checks for OS compatibility as per the OS Supportability Matrix document. No specific user input is required to run this check. 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 are the minimum supported versions of the supported operating systems:

  • Microsoft Windows server 2008 R2 x64 version 6.1 or higher
  • RedHat Enterprise Linux 6.5 x64
  • CentOS 6.5 (x64) (validated from Version 9.0 SP 1)
  • SUSE Enterprise Linux Server 11 SP3 (validated from Version 9.0 SP 1)
  • Oracle Solaris 10 (validated from Version 9.0 SP 1)
Type(Version 9.0 or later) pre-upgrade check, configuration check
Check performed and expected resultDepending 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 as per the OS Supportability Matrix document.
Corrective actionEnsure that the operating system of the computer on which BMC Remedy AR System is installed is equal to, or higher than the minimum supported version. BMC Solution And Product Availability And Compatibility Utility (SPAC)  

Go to top

Platform Version Check

Info: This check is initiated by the installer.

Description

(Version 9.0 or later) This check verifies whether the version of the current AR System server is not less than the minimum version for supported by the installer.

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 is present in the config directory.
Type(Version 9.0 or later) pre-upgrade check
Check performed and expected result
  • If the version of the current AR System server is not less than the minimum version supported by the installer, the check is successful.
  • If the version of the current AR System server version is less 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 less than the minimum version supported by the installer.

Go to top

Read-Only-Tran Check

Description

(Version 9.0 or later) This check verifies whether  the Read-Only-Tran-Off parameter in ar.cfg (ar.conf) is configured to T.

Type

(Version 9.0) pre-upgrade check

(Version 9.0 SP1) 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 ar.cfg (ar.conf) file, and the value is set to T.

Go to top

Repeat Parameter Check

Description

(Version 9.0 or later) This check verifies whether duplicate configuration parameters exist in the ar.cfg (ar.conf) file.

Type

(Version 9.0) pre-upgrade check

(Version 9.0 SP1) 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 the duplicate parameters.
Corrective actionEnsure that there are no duplicate configuration parameters present in the ar.cfg (ar.conf) file. Remove the duplicate parameters.

Go to top

RPC Check

Description

(Version 9.0 or later) This check verifies whether the RPC-Non-Blocking-IO parameter in the ar.cfg (ar.conf) is set to F.

Type

(Version 9.0) pre-upgrade check

(Version 9.0 SP1) configuration check 

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

Go to top

Secondary Server Down Check

Description

(Version 9.0 or later) This is an additional validation to ensure that the secondary AR System server(s) is 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. After the upgrade of primary AR System server is completed, the installer brings the secondary AR System server up again.

Type(Version 9.0 or later) pre-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.
Corrective action

No corrective action.

Go to top

Server Information Gathering Check

Description

This check collects configuration properties from the AR System Administration: Server Information form or the ar.cfg (or ar.conf) file. These properties are displayed with their recommended values.

 List of configuration properties
  • Allow-Guest-Users
  • Allow-Unqual-Queries
  • Alternate-Approval-Reg
  • Approval-RPC-Socket
  • Debug-mode
  • Delay-Recache-Time
  • Filter-Max-Stack
  • Filter-Max-Total
  • Max-Entries-Per-Query
  • Max-Log-File-Size
  • Num-Preload-Schema-Segments
  • Num-Preload-Threads
  • Oracle-Clob-Storage-In-Row
  • Plugin-Loopback-RPC-Socket
  • Save-Login
  • Server-Group-Member
  • Server-Plugin-Default-Timeout
  • Server-Side-Table-Chunk-Size
  • Next-ID-Block-Size
  • Plugin-ARDBC-Threads
  • Plugin-AREA-Threads
  • Plugin-Filter-API-Threads
  • Private-RPC-Socket
  • RE-RPC-Socket
  • Server-Group-Signal-Option
  • External-Authentication-Return-Data-Capabilities
  • Submitter-Mode
  • Plugin-Log-Level
  • Max-Log-History
  • Authentication-Chaining-Mode
  • Large-Result-Logging-Threshold
Type

(Version 9.0) pre-upgrade check, configuration check

(Version 9.0 SP1) configuration check 

Check performed and expected resultA message about the configuration properties is displayed.
Corrective actionNo corrective action is required.

Go to top

SQL DB Configuration Check

Description

This check validates the following attributes of the MS SQL server:

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

Note:

This check is specific to Microsoft Windows OS and the MS SQL database.
For other combination of OS and database, the status of the check remains Not run.

Type(Version 9.0 or later) pre-upgrade check
Check performed and expected result
  • If READ_COMMITTED_SNAPSHOT is ON and XACT_ABORT is OFF, the check is successful.
  • If READ_COMMITTED_SNAPSHOT is OFF and XACT_ABORT is ON, the check fails and displays an error message.
Corrective action Perform the following corrective actions:
  • To find the current setting of Read Committed Snapshot, use the following command:
    SELECT is_read_committed_snapshot_on FROM sys.databases
    where name = 'ARSystem';
  • If the current setting of Read Committed Snapshot is OFF, turn ON the Read Committed Snapshotsetting on the target MSSQL server:
    1. Stop the AR System server.
    2. Run the following SQL command:
      ALTER DATABASE ARSystem SET READ_COMMITTED_SNAPSHOT ON;
    3. Restart the AR System server.

  • To get the current setting of the XACT_ABORT option, use the following command:
    DBCC USEROPTIONS;
  • If the current setting of XACT_ABORT is ON, set this option to OFF on the target MS SQL server:
    1. Stop the AR System server.
    2. Run the following SQL command:
      SETXACT_ABORT OFF;
    3. Restart the AR System server.

Go to top

SQL Replication ON Check

DescriptionThis check validates whether SQL replication is OFF for any of the tables.
Type(Version 9.0 or later) pre-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.

Go to top

SynAttackFlagTest

Description

(Version 9.0 or later) This check verifies whether the registry entry synattackprotect exists at the location HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\Tcpip\Parameters, and is set to 0.

Type

(Version 9.0) pre-upgrade check

(Version 9.0 SP1) configuration check 

Check performed and expected result
  • If the registry entry synattackprotect is present at the specified location, and is set to 0, the check is successful.
  • If the registry entry synattackprotect is present at the specified location, but is set to 1, the check fails with a warning, and displays a warning message.
  • If the registry entry synattackprotect is not present at the specified location, or if the registry entry synattackprotect is present, but configured to value other than 1 or 0, the check fails with an error and displays an error message.
Corrective action

Ensure that the registry entry synattackprotect exists at the location HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\Tcpip\Parameters, and it is set to 0.

Go to top

Verify Select Query Hint Check

DescriptionThis check validates whether the Select-Query-Hint property is configured in the ar.cfg (or ar.conf) file, and the value set to NOLOCK.
Type

(Version 9.0) pre-upgrade check, configuration check

(Version 9.0 SP1) configuration check 

Check performed and expected result
  • If the Select-Query-Hint property is not configured in the ar.cfg (ar.conf) file, the check displays the following error message:
    Please configure 'Select-Query-Hint: NOLOCK' for better concurrency.
  • If the value of Select-Query-Hint is set to any value other than NOLOCK, the check displays the following error message:
    Please set 'Select-Query-Hint' value to 'NOLOCK' for better concurrency.
Corrective action

Configure the Select-Query-Hint property in the ar.cfg (or ar.conf) file, and set the value to NOLOCK.

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