This documentation supports the 9.0 version of Remedy Action Request System.

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

Running the database consistency checker

The database consistency checker utility compares the Remedy Action Request System metadata with the database structure inside a database. You can use this utility to check the consistency in a database with the data in the AR server. For example, if an AR System form contains ten fields and you delete those fields directly through the database, after you run the database consistency checker utility, you get a warning about the mismatch in records.

You must shut down the AR System before running the database consistency checker.

The database consistency checker uses the -checkdb start up option for arserver.exe (Windows) and arserverd (UNIX).


  • This utility does not start the AR System server for normal use, but instead generates a report about the database tables.
  • Run this utility if you have one or more BMC Remedy AR System servers running on the same computer. In either case, use the -i option to run the checkdb option against the correct server. Also, use the -s and the -l options to specify the name of the server and the path of the license directory, respectively. This enables the -checkdb option to locate the BMC Remedy AR System server, in case the installation directory is other than the default installation directory.
  • If you specify the log file path, use an absolute and not a relative log file path.
  • If a log file with the same name already exists, then the existing file is renamed to logFileName.bak, and a new file is created with the specified name.
  • If you do not specify a log file path, or if the path you specify is invalid, the AR System server creates the following log file:

To run the database consistency checker

  1. Start the AR System server executable using the -checkdb option.

    1. For a non-Unicode database:

      <ARServerInstallDir>/bin/arsystem env <ARServerInstallDir>/bin/arserverd -checkdb "<LogFileDir>" -s <ARSystemServerName> -i <ARSystemInstallDir> -l <ARSystemLicenseDir>

      For example:

      ./arsystem env ./arserverd -checkdb "/usr/tmp/checkdb.log" -s <ARSystemServerName>
      -i <ARSystemInstallDir> -l <ARSystemLicenseDir>
    2. For a Unicode database:

      ./arsystem env ./arserverd --unicode -checkdb "<LogFileDir>"
      -s <ARSystemServerName> -i <ARSystemInstallDir> -l <ARSystemLicenseDir>

      For example:

      /opt/bmc/ARSystem/bin/arsystem env /opt/bmc/ARSystem/bin/arserverd --unicode -checkdb "/usr/tmp/checkdb.log" -s <ARSystemServerName> -i /opt/bmc/ARSystem -l /etc/arsystem/<ARSystemServerName>
    3. For a Windows server:

      <ARServerInstallDir>arserver.exe --unicode -checkdb 
      "<LogfileDir>" -s <ARSystemServername> -i <ARServerInstallDir> -l <ARSystemLicenseDir>

      For example:

      C:\Program Files\Common Files\AR System\Licenses>arserver.exe --unicode -checkdb 
      "C:\Program Files\Common Files\AR System\Licenses\Arserver\Db\checkdb.log" -s <ARSystemServername> -i 
      "C:\Program Files\Common Files\AR System\Licenses" -l "C:\Program Files\Common Files\AR System\Licenses"


      ARSystemLicenseDir is the location of where the arsystem.lic file can be found.

  2. Check the generated log file for the inconsistencies.

Considerations for Microsoft SQL Server 2012 or above

If you are using Microsoft SQL Server 2012 or above database you will need to create synonyms for the trace_xe_action_map and trace_xe_event_map system procedure before running database consistency checker utility.

To create the synonyms

  1. Open SQL Server Management Studio (of relevant version).
  2. Open a new query window.
  3. Choose the "ARSystem" database.
  4. Execute the following SQL statements:
    create synonym trace_xe_action_map for sys.trace_xe_action_map;
    create synonym trace_xe_event_map for sys.trace_xe_event_map;
Was this page helpful? Yes No Submitting... Thank you