Checking the database tables
The database consistency checker is a separate process that runs in the background during server startup and terminates when it is complete. It reports the results of the consistency check to a log file that you specify. It checks the following database information:
- Data dictionary consistency — Verifies whether all the system tables accessed during server startup are available in the database, and reports errors for any inconsistencies found.
- Metadata consistency — Verifies whether the BMC Remedy AR System metadata (system data that is necessary for an AR System server to load) is intact.
- Index consistency — Verifies whether all necessary indexes are intact, and reports warnings or errors for any inconsistencies found. A missing or damaged index can cause unexpected performance issues if the AR System server cannot automatically re-create the index.
- Workflow assignment or qualification and display properties consistency — Verifies the consistency of workflow actions and their qualifications during server cache loading on AR System server startup.
Run this report if an error indicates that there could be a problem with the database tables. Always work with BMC technical support to resolve database errors.
If the LD_LIBRARY_PATH is not set, the DB Consistency Checker will fail because the necessary shared libraries are not accessible. To learn about setting the LD_LIBRARY_PATH variable, see in BMC Remedy ITSM Deployment documentation.
The -checkdb option is a standalone option. When you use this option, the process checks the consistency of the AR System server database, reports the results in the checkdb log file, and then quits. Therefore, do not include the -checkdb option with arserver/arserverd in the armonitor.conf file.
Required privileges for database consistency checks
The database consistency checker utility uses the same user ID and password as that of AR System to connect to the database.
To use the database consistency checker, the AR System database user (ARAdmin) must have correct privileges to the system view, stored procedures, or table that is used to get table information. If the BMC Remedy AR System database user does not have sufficient privileges, checkdb cannot fetch table information from the database to validate it.