Repository tools command to verify the integrity of a database

Edit online

Use the verify command to verify the integrity of a database.

Purpose

The verify command is used to verify the structural integrity of the data in the database, identify any issues, and provide resolution for those issues. The command uses verification levels set between number one and ten. Level ten is the maximum verification level and level one is the minimum verification level. Level one, for example, verifies whether the item can be fetched by simple fetch call at a high level. If the command identifies a major issue, you can use a higher level to get more detailed output. When the level is set to ten, it looks for the particular content of the component in all database tables and verifies their validity. When the command identifies an issue, you must run the suggested repotool command to fix those issues. If an unknown issue is identified, you must contact IBM Support.
Each component uses these levels with different verbose checks. If verification is required and you do not have any reason to select another level, you can start with level five. If the verify command reports issues with a component, you can start with a higher level to get more detailed output. The higher the level of verification, the more detailed output is generated and takes longer time to complete the verification process. For information about the verify command error messages, see the Repotools Verify command - additional guidance document in the Deployment wiki.
Important: You must shut down the server before you run the command.

It is recommended that you run this command monthly and before an upgrade. You must run the command at level four before an upgrade. After you run the command, you must share the repotools-app.log file with IBM Support.

The log4j2 update changed the way the verify command logs output. It now summarizes the main sections of the output and generates a summary of the issues identified. You can update the C:\IBM\JazzTeamServer_7.0.3\server\conf\repotools_log4j2.xml file to change the logging level to the debug mode.

<Logger name="com.ibm.rdm.repotools.verifiers.RepositoryHealthService" level="DEBUG" />
        <Logger name="com.ibm.rdm.repotools.verifiers.RepositoryHealthVerifier" level="DEBUG" />

Parameters

Attribute Description Required Default
teamserver.properties The file system path to the teamserver.properties file. No conf/application/teamserver.properties

where application is jts, ccm, rm, qm, gc, dcc, or relm.
logFile Path to the log file. No repotools-application_verify.log

where application is jts, ccm, rm, qm, gc, dcc, or relm.
level The verification level. A number between 1 to 10 can be used. 1 is the minimum level and 10 is the maximum level. Level 1 uses less verification, but it runs faster. Level 10 uses more verification, but it runs slower. No 1

Example

The following example is for Jazz® Team Server. To use this command for other applications, run these options from the server directory:
  • IBM® Engineering Workflow Management (Change and Configuration Management application): repotools-ccm
  • IBM Engineering Requirements Management DOORS® Next (Requirements Management application): repotools-rm
  • IBM Engineering Test Management (Quality Management application): repotools-qm
  • Global Configuration Management: repotools-gc
  • Data Collection Component: repotools-dcc
  • IBM Engineering Lifecycle Optimization - Engineering Insights: repotools-relm

For Windows operating system Open a command prompt and enter this command:

cd C:\Program Files\IBM\JazzTeamServer\server\
repotools-jts.bat -verify teamserver.properties=conf\jts\teamserver.properties level=5

For Unix operating systems Open a command line and enter this command:

cd /opt/IBM/JazzTeamServer/server/
./repotools-jts.sh -verify teamserver.properties=conf/jts/teamserver.properties level=5