Vault Verify Command-line Options

The following table presents the the command-line options for the Vault Verify utility.

In general, you can run Vault Verify from the command line as follows: VaultVerify [options] “configuration” .

Based on the default or given -check options, integrity checks are performed on the vault archive files for the specified StarTeam "server configuration". If you specify the -repair option, Vault Verify attempts to correct problems found. Vault Verify opens the database for the server configuration but does not modify it. Valid options for Vault Verify are described in the following table.

-check {missing | corrupt | stray | all}

Determines which integrity checks to perform:

missing Checks for missing files by comparing the database against archive files actually present.
corrupt Checks the integrity of existing archive files (MD5, name, folder, and .gz file format).
stray Checks for extraneous files based on the database. This option cannot be used if the server configuration is in use.
all Performs all integrity checks.

Multiple -check options can be specified. Also, see the -repair option.

–cf <folder path> Path name of the corrupt file folder, where problem files found by the corrupt check are moved when -repair is specified. The default corrupt file folder is C:\Temp\VVCorruptFiles.
–dbhost <host> Specifies the host name of the database for the specified <server configuration>. On Microsoft Windows, it is only meaningful when –dbinstance is also provided. On Microsoft Windows and Linux, use this option only when the database server executes on a different host than this one.
-dbname <name> Specifies the database name for the specified <configuration>. On Microsoft Windows, this parameter is only meaningful when –dbinstance is also specified, and it is only needed when the database name is different than the database server name. On Linux, use this option only if –dbinstance is not used and the Oracle service name is different than the server name or SID.
-dbinstance <name>

This option is only meaningful on Windows. When used, it causes VaultVerify to open the database directly instead of via the database server name specified in the configuration file. For SQL Server, the <name> must be the instance name (for example, 'SSE2005_ST').

Note: The default Instance name for SQL Server is 'MSSQLSERVER' and for SQL Server Express, it is 'SQLEXPRESS'. For Oracle, should be the service name, (for example, 'ORCL').

-dbinstance must be used with -dbhost when the database server executes on a different host. For SQL Server, -dbname should also be used if the database name is different than the Database Server Name. For Oracle, -dbname is ignored if -dbinstance is specified.

-dbpassword <password> Specifies the database logon password. If not specified, a blank password is used. (The password stored in the configuration is encrypted and cannot be used by VaultVerify.) On server configurations running against Oracle, this option must be specified since the Oracle password is never empty.
-dbport <port> Specifies the TCP/IP port to use to connect to the database server. This parameter is only used on non-Microsoft Windows platforms when a different port is used than the vendor's default database port (for example, 1521 for Oracle).
-dbuser <user> Specifies the logon ID used to connect to the database. If specified, this parameter overrides the user specified in the StarTeam <configuration>. The only valid user to use with this option is the user that owns the StarTeam tables.
-help (or -h or -?) Displays this usage information.
–path <folder path> Specifies the folder path of the starteam-server-configs.xml file. This file must exist and contain the specified <server configuration>. By default, this file is opened in the parent folder of the current working directory if it is not found in the current working directory.
-nosharereport Suppresses the reporting of share information. Normally, all share paths of each corrupt file is reported. This option suppresses the share path information, which can speed up application execution and substantially reduce the report size.
-repair

Specifies that an attempt should be made to correct archive file problems. 'Corrupt' archives are moved to the 'corrupt file folder' (see the -cf option). If they correspond to valid file revisions, they are then treated as missing. Missing archive recovery is attempted from other vault files and, if the -useca option is specified, from a Cache Agent. Stray archives are moved to the 'stray file folder' (see the -sf option).

Note:-repair is ignored if the StarTeam <configuration> is in use.

-sf <folder path> Path name of the 'stray file folder', where extraneous files found by the 'stray' check are moved when -repair is specified. The default 'stray file folder' is C:\Temp\VVStrayFiles.
–t Displays elapsed time information when the verification finishes.
-useca <host>:<port> If -repair is specified, this option enables attempts to recover missing files from the specified MPX Cache Agent. The <host> and <port> must designate a remote MPX Cache Agent because it maintains an independent cache.
-verbose Displays additional status information as the verification proceeds.
“configuration” Specifies the configuration name. The configuration name passed to VaultVerify is case-sensitive, and if it includes spaces, you must pass the configuration name to Vault Verify in quotation marks.