Repository tools command to repair multiple versions of an artifact marked as current

Edit online

Use the repairMultipleVersionsMarkedAsCurrent command to repair multiple version of the same artifact marked as current in the configuration.

Purpose

In Engineering Requirements Management DOORS® Next and Engineering Test Management version 6.0.2 and earlier, if multiple users update an artifact in a configuration at the same time, inconsistent versions of the artifact might be displayed in the configuration. This problem occurs because multiple versions of the artifact are internally marked as the current version. For example, you might experience the following issues:
  • Different views show different versions of an artifact for the same configuration.
  • An artifact cannot be found.

This issue no longer occurs in version 6.0.3 and later, but might be present in those versions if you upgraded from an earlier release. You can run the following query to detect if a configuration has more than one current version of an artifact:

Db2® and SQL Server

SELECT DISTINCT CONFIGURATION_ITEM_ID FROM VVCMODEL.VERSION WHERE CURRENT_COL = 1 GROUP BY CONFIGURATION_ITEM_ID, CONCEPT HAVING COUNT(CONCEPT) > 1

Oracle

SELECT DISTINCT CONFIGURATION_ITEM_ID FROM VVCMODEL_VERSION WHERE CURRENT_COL = 1 GROUP BY CONFIGURATION_ITEM_ID, CONCEPT HAVING COUNT(CONCEPT) > 1

If the query finds more than one current version, use the repairMultipleVersionsMarkedAsCurrent command to fix the issue.

Depending on the size of your database, the utility might take a while to scan the entire database. The server must be running when you run the command and no restart is required after the command is complete.

If you are prompted for the following message, you can safely ignore it:
repair: YYYY-MM-DD HH:MM:SS,### [Number of configurations] Configurations Modified. Please shutdown the server and run the reindex command.

Parameters

Attribute Description Required Default
repositoryURL The connection URL for the server. No https://localhost:9443/application where application is rm or qm.
adminUserId Administrative user ID to login to the server. No ADMIN
adminPassword Administrative user password to login to the server. No ADMIN
credentialsFile The file containing the administrative user login credentials. No credentials.properties
certificateFile The file containing the administrative user login certificate. No none
smartCard The alias to login using a smart card, or ? to list available aliases. No none
logFile Path to the log file. No repotools-application_repairMultipleVersionsMarkedAsCurrent.log where application is rm, or qm.
kerberos Authenticate with Windows user credentials using Kerberos/SPNEGO by setting to true. Or authenticate with Windows Integrated Authentication by setting to windows. No None

Example

The example is for Engineering Requirements Management DOORS Next. Replace repotools-rm with repotools-qm for Engineering Test Management.

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

cd C:\Program Files\IBM\JazzTeamServer\server\
repotools-rm.bat -repairMultipleVersionsMarkedAsCurrent credentialsFile=credentials.properties kerberos=true

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

cd opt/IBM/JazzTeamServer/server/
./repotools-rm.sh -repairMultipleVersionsMarkedAsCurrent credentialsFile=credentials.properties