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

To view an earlier version, select the version from the Product version menu.

Running the database consistency checker

The following topics are provided:

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.

Correcting database inconsistencies by using the database consistency checker warning messages

When you upgrade the Remedy AR System, the database consistency checker identifies the data inconsistencies between the database and the AR System Server. BMC provides detailed warnings that help you fix the inconsistency easily. If you ignore the warnings given by the database inconsistency checker, you may encounter problems such as data truncation or invalid values after the upgrade. 

The following table describes the examples of some warnings displayed by the database consistency checker:

Example warningDescription
Invalid size for Column [name=name; type=VARCHAR]
in table actlink;
should be size 254 and scale 0 but is of size 100 and scale 0

In the actlink table, reset the name column size from 100 to 254.

Found non-matching input length - Input length for field: C536870915 on table: T586 is 255, while in field definition it is 100.

In the T586 table, reset the length of the C536870915 field from 255 to 100.

Found non-matching data type - field: C536870917 on table: T586 has size 3000 while in in field definition it is set to unlimited(0).

In the T586 table, reset the size of the C536870917 field from 3000 to unlimited (0).

Index T3162_900987211_1 on table T3162 is defined in database,
however, it is not defined on definition of form STG_ImpactAnalysisCircuits

Index T3162_900987211_1 on the STG_ImpactAnalysisCircuits form is created directly on the database.

BMC recommends creating an index using Remedy Developer Studio.

Related topic

Checking the database tables

Was this page helpful? Yes No Submitting... Thank you

Comments