Running the database consistency checker
The database consistency checker utility compares the 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 System 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 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
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"
Important
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"
Important
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 System server is non-Unicode then remove --unicode from command line.
Check the generated log for any inconsistencies.
Correcting database inconsistencies by using the database consistency checker warning messages
When you upgrade the 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 warning | Description |
---|---|
Invalid size for Column [name=name; type=VARCHAR] | In the |
Found non-matching input length - Input length for field: C536870915 on table: T586 is 255, while in field definition it is 100. | In the |
| In the |
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. Best practice We recommend that you create an index using
Developer Studio
. |
Comments
Log in or register to comment.