This documentation supports the 9.1 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).

Notes

  • This utility does not start the AR System server for normal use, but instead generates a report about the database tables.
  • 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:
    ARSystemInstallDir
    \db\ardbcheck.log

Steps to perform before running database consistency checker

(For Windows server)

When you run the database consistency checker using -checkdb start up option for arserver.exe, it fails and generates error because the port 12444 for dt_socket is already utilized by AR System server.

To avoid this error, perform the following steps before running the database consistency checker:

  1. From ARSystemServerInstallDir, open the arserver.config file for Windows and the arserverd.conf file for UNIX .
  2. Change the port 12444 for the dt_socket in the following jvm.option command:

    jvm.option.<number>=-agentlib:jdwp=transport=dt_socket,server=y,suspend=n,address=12444

    to

     jvm.option.<number>=-agentlib:jdwp=transport=dt_socket,server=y,suspend=n,address=12445
  3. Save the arserver.config file or the arserverd.conf file.
  4. Run the database consistency checker. 

  5. Revert the changes applied to the port number from the following jvm.option command:

     jvm.option.<number>=-agentlib:jdwp=transport=dt_socket,server=y,suspend=n,address=12445

    to

    jvm.option.<number>=-agentlib:jdwp=transport=dt_socket,server=y,suspend=n,address=12444
  6. Save the arserver.config file or the arserverd.conf file.

To run the database consistency checker

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

    • For UNIX:

      <JAVA_HOME>/bin/java
      -jar <ARSystemInstallDir>/bin/arserver.jar --unicode -checkdb
      "<Full Path to log file>" -s "<ARSystemServerName>" -i
      "<ARSystemInstallDir>" -l "<ARSystemLicenseDir>"

      Example:

      /opt/jre/bin/java -jar
      "/opt/bmc/ARSystem/bin/arserver.jar" --unicode -checkdb
      "/usr/tmp/mycheckdb.log" -s "artest" -i "/opt/bmc/ARSystem" -l
      "/etc/arsystem/artest"

      Note

      Full path to log file location is optional. If you do not provide the full path, the AR System server creates the ardbcheck.log file in the <ARSystemInstallDir>/db directory.

    • For Windows:

      <JAVA_HOME>\bin\java.exe
      -jar <ARSystemInstallDir>\arserver.jar --unicode -checkdb "<Full
      Path to log file>" -s "<ARSystemServerName>" -i
      "<ARSystemInstallDir>" -l "<ARSystemLicenseDir>"

      Example:

      "C:\Program
      Files\java\jre\bin\java.exe" -jar "C:\Program Files\BMC
      Software\ARSystem\arserver.jar" --unicode -checkdb "C:\temp\mycheckdb.log" -s
      "artest" -i "C:\Program Files\Common Files\AR System" -l "C:\Program
      Files\Common Files\AR System\Licenses"

      Full path to log file location is optional. If you do not provide the full path, the AR System server creates the ardbcheck.log file in the <ARSystemInstallDir>\Arserver\db directory.

      The AR System server overwrites an existing log file. If your AR Server is non-Unicode then remove --unicode  from command line.

  2. Check the generated log for any 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 the 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

Comments

  1. Andreas Mitterdorfer

    Please can you update the To run the database consistency checker section for a 9.1 system? There is no arserver.exe/arserverd binary anymore.

    Aug 18, 2017 08:38
    1. Anagha Deshpande

       Hello Andreas,

      The arserver.exe/arserverd binaries still exist with 9.x servers. The binaries are appropriately modified to perform exactly the same function as earlier.

      Regards,

      Anagha

      Aug 23, 2017 10:30
  2. Brad Taylor

    Note that the license directory is typically C:\Program Files\Common Files\AR System\Licenses - note the different path, compared to the examples ("C:\Program Files\BMC Software\ARSystem").

    Aug 30, 2018 01:20
    1. Anagha Deshpande

      Hello Brad,

      Our team is working on this. We will update the topic soon.

      Regards,

      Anagha

      Aug 30, 2018 10:28
      1. Onkar Telkikar

        Hello Brad,

        Thank you for pointing this out. We have updated this topic.

        Regards,

        Onkar

        Sep 12, 2018 01:01
  3. Brian Gillock

    What is the database consistency checker? What does it do? Why would one use it? Does ARS have to be shutdown before running this?

    Jun 11, 2019 10:04
    1. Onkar Telkikar

      Hello Brian,

      Apologies for the delayed response.

      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.

      I have updated this topic with the preceding information.

      For information about the database consistency checker utility, see Checking the database tables and Required privileges for database consistency checks.

      Regards,
      Onkar

      Sep 27, 2019 05:03