This documentation supports the 18.08 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. To run the database consistency checker without stopping the AR System service, see the Alternative method to run the database consistency checker on Windows in this topic.

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:

      <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"

      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>\Arserver\db directory.

      • You must be connected to the Internet to run the preceding command for Windows.

      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.

Alternative method to run the database consistency checker in Windows

Use this method to run the database consistency checker without stopping the Remedy AR System services.

  1. Open command prompt (cmd.exe) as "Run as administrator".
  2. Navigate to ARSystemServerInstallDir using the command prompt.
  3. Run the command:

    ardbutils.bat -dbCheckOnly
  4. The ardbcheck.log file is generated in the <ARSystemInstallDir>\Arserver\db directory. Check the generated log for any inconsistencies.
Was this page helpful? Yes No Submitting... Thank you

Comments