This documentation applies to the 8.1 version of Remedy Action Request System, which is in "End of Version Support."

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.
  • 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:
    ARSystemInstallDir
    \db\ardbcheck.log

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\BMC Software\ARSystem>arserver.exe --unicode -checkdb 
      "C:\Program Files\BMC Software\ARSystem\Arserver\Db\checkdb.log" -s <ARSystemServername> -i 
      "C:\Program Files\BMC Software\ARSystem" -l "C:\Program Files\BMC Software\ARSystem"

      Note

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

  2. Check the generated log file for the inconsistencies.

Related topics

This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

Comments

  1. Andreas Mitterdorfer

    Example for unicode database is listed twice.

    Mar 31, 2014 05:58
    1. Aparna Saxena

      Hi Andreas, thank you for your comment. This page has 2 examples: one for a unicode database and one for a non-unicode database.

      The second example (for unicode database) has  --unicode in it. This is the only difference between the two.

      Thanks,

      Aparna

      Apr 01, 2014 06:49
  2. Andreas Mitterdorfer

    Ah sorry, thanks my fault. (sad)

    Apr 01, 2014 06:55
  3. Kelly Logan

    I think it would be useful to have a more complete explanation of this command. Are all parameters after "-checkdb" optional for instance? If you are running on the server you want to check and their is only one server instance, is there any reason not to simply type "arserver -checkdb"?

    Aug 20, 2014 03:15
    1. Bhakti Paranjpe

      Hello Kelly,

      Thank you for your comment. I will consult the concerned SME and get back to you soon.

      Thanks,
      Bhakti.

      Aug 22, 2014 03:39
    1. Bhakti Paranjpe

      Hello Kelly,

      I have updated the content to include some additional explanation. Even if there is just one server instance, it is advisable to include all the parameters after the -checkdb command. This is to make sure that the -checkdb option locates the BMC Remedy AR System server, in case the installation directory is different from the default installation directory.

      Thank you for your patience,
      Bhakti

       

      Sep 12, 2014 06:42
  4. Piotr Sadowski

    Example given for Windows server is for Unix server.

    For Windows it could be:

    arsystem .arserver.exe --unicode -checkdb "<LogFileDir>"
    -s <ARSystemServerName> -i <ARSystemInstallDir> -l <ARSystemLicenseDir>
    Nov 30, 2014 09:51
    1. Prachi Kalyani

      Hello Piotr,

      Thank you for your comment. I have updated the topic.

      Thanks,

      Prachi

      Nov 30, 2014 10:02
  5. Milan Franzkowski

    The consistency checker seems to be useful on first sight, but I honestly ask myself what to do with the result.

    First of all even after a fresh installation of AR / ITSM 8.1 the check already finds quite some stuff and the log is long (many "..Cannot open catalog; Message number = ...").

    Also when I know (like we do in our DB) that there are errors with the "schema_sort" and fields in the sort are not available on the form, the DevStudio hangs with a null pointer exception when I open the form and go to the sort properties to try to fix it.

    I found very little on how to fix those findings properly and the log doesn't really give much information on that, too.

    Wouldn't it be nice to have the checker automatically fix at least some of the findings? Perhaps with another parameter on the call or even interactively in the shell?

     

    Another thing bothering me is that I can't run that in the background on Solaris. Even with a call utilizing the "&" or if it's already running using CTRL+Z doesn't work.

    So I can't "bg" and "disown" the running process. So when I close my shell, the checker stops running.

    Dec 03, 2015 08:16
    1. Poonam Morti

      Hi Milan,

      I will check this with the SME and get back to you.

      Thanks,

      Poonam 

      Dec 04, 2015 12:35
    1. Poonam Morti

      Hi Milan,

      There are few warnings displayed on OOTB setup, we have logged a defect for this to fix them. Regarding automatic fixing of errors, the consistency checker utility finds the database corruption or inconsistency, it cannot correct the values.

      To run the program in background you can use the following command:

      nohup "<Command>" &

       This command runs in background even if you close the command prompt.

      Thanks,

      Poonam

       

      Dec 22, 2015 01:20
      1. Milan Franzkowski

        Hi Poonam,

        thanks for logging the defect.

        About the command line, I tried and it didn't work on our setup (Solaris 10). I used PuTTY and MobaXterm and the checker ran always in the foreground despite nohup and &.

        Best,

        Milan

        Dec 22, 2015 02:12
        1. Poonam Morti

          Hi Milan,

          I am verifying this with the SME and will get back to you.

          Thanks,

          Poonam

          Dec 27, 2015 11:04
        1. Poonam Morti

          Hi Milan,

          I have verified this with the SME. The command is working for the Solaris setup.

          When you set the LD_Library_Path and run the command, the command works properly. 

          To get more details, you can contact BMC Customer Support.

          To contact BMC Customer Support, click here.

          Thanks,

          Poonam

          Jan 05, 2016 02:30
          1. Milan Franzkowski

            Hi Poonam,

            I didn't say the command wasn't working. The LD_Library_Path is set on our system. I only meant that running the command in the background using "&", "nohup" and "bg" doesn't work, so the command always runs in the foreground and the terminal needs to stay open while it's running.

            Other commands are able to run in the background on our system. Anyway, this isn't that much of a deal to open a case for it.

            Best,

            Milan

            Jan 06, 2016 06:12
  6. Axel Kluener

    Hey, I´m able to leave a comment, though the top of this page says:

    "This documentation applies to the 8.1 version of Remedy Action Request System, which is in "End of Version Support." You will not be able to leave comments."

    Feb 25, 2019 05:16
    1. Anagha Deshpande

      Hello Axel,

      You can leave a comment on version 8.1.

      Regards,

      Anagha

      Mar 05, 2019 12:24
  7. Axel Kluener

    Hallo Anagha,

    that's what I demonstrated successfully.

    So why does text at the top of the page say :

    "This documentation applies to the 8.1 version of Remedy Action Request System, which is in "End of Version Support." You will not be able to leave comments.

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

    ?

    Regards, Axel

    Mar 12, 2019 09:10
    1. Anagha Deshpande

      Hello Axel,

      BMC no more supports version 8.1 of BMC Remedy AR System. The documentation of version 8.1 is still available for reference.

      Click here to refer to the latest documentation of Remedy AR System version 19.02.

      Regards,

      Anagha



      Mar 12, 2019 09:58