Repository tools command to verify the integrity of a database

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

Purpose

The verify command is used for contents verification in the database with verification levels set between number one and ten. Level ten is the maximum verification level. When the level is set to ten, it looks for the particular content of the component in all database tables and verifies their validity. Level one is the minimum verification level. Level one for example, verifies if the item can be fetched by simple fetch call at a very top level. Each component uses these levels with different verbose checks, but usually level five should be the base to start with, if verification is needed. If some components show major problems, then you can start with a higher level to get more verbose output. For information about the verify command error messages, see the Troubleshooting section of the Deployment wiki.
Important: You must shut down the server before you run the command.
Important: In versions of Rational® Team Concert® earlier than 3.0.0, it was possible for a change set to be displayed multiple times in the history of a workspace or a stream. When you run the verify command on databases that contain data that was created with versions of Rational Team Concert earlier than 3.0.0, messages similar to this one might be displayed:

History contains multiple references to change set _ifGCAfwOEdyMyflwGKMWgg

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, am, rm, qm, gc, dcc, dm, or relm.
logFile Path to the log file. No repotools-application_verify.log

where application is jts, ccm, am, rm, qm, gc, dcc, dm, 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:
  • Change and Configuration Management: repotools-ccm
  • Rhapsody Model Manager: repotools-am
  • Requirements Management: repotools-rm
  • Quality Management: repotools-qm
  • Global Configuration Management: repotools-gc
  • Data Collection Component: repotools-dcc
  • Design Management: repotools-dm
  • Rational Engineering Lifecycle Manager: repotools-relm

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

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