maintain chpasswd <user> <new-password>Changes the password stored in the AccuRev repository for an existing principal-name (named AccuRev user). To remove a user’s password, use two consecutive double-quote characters as the <new-password> parameter:maintain chslice <slice-number> <new-location>Changes the location of an existing slice in the repository. Use the show slices command to get a listing of slice numbers and their current locations.Note: this command does not physically move the slice. See the chslice command in the AccuRev CLI User’s Guide for more information.maintain chuser <user-ID> <new-username>Changes the principal-name (AccuRev username) of an existing user. You specify the user by the unique numeric user-ID, which is immutable. This command is similar to the accurev chuser command.maintain concheck [ site | diag ] <db-admin>When site is specified, the command verifies the existence of the AccuRev database as well.When diag is specified, the command performs a series of diagnostics (server initialization, database connection, query execution, and database creation) and displays timing information for each one.maintain dbcheck [<depot-name>]
--auto_commit option again; dbupgrade will skip the depots that have already been upgraded and resume the upgrade process with the remainder. If you are unable to resolve the problem that lead to the failure, you can return to your pre-upgrade state by reinstalling your previous AccuRev release and then restoring from the backup you created prior to running dbupgrade.See “Using the ‘maintain dbupgrade’ Command” in the current AccuRev Installation and Release Notes for the most up-to-date information about using dbupgrade. Also see Specifying a Database Admin Username and Password on page 115.maintain mkdbuser <db-admin>Makes a database user using the DB_USER and DB_PASS values from the acserver.cnf file in the AccuRev bin directory. The AccuRev Server uses this username to communicate with the database.maintain mksite <db-admin>maintain restore <backup-file-spec> <db-admin>Provides a facility for restoring AccuRev metadata from backup (see Backup/Restore of the AccuRev Repository on page 119).The <backup-file-spec> can be either a file name (if the backup was saved to $BACKUP_LOC) or the full path and name of the backup file.maintain rmdepot <depot-name>Removes a depot from the AccuRev repository. All streams, snapshots, and workspace streams are also removed from the repository. (Workspace trees are not removed.) For details, see Removing a Depot from the AccuRev Repository on page 119.maintain rmsite <db-admin>Writes the <parameter> and <value> specified to the acserver.cnf file in the AccuRev bin directory in the form PARAMETER=value. If the <parameter> is DB_PASS, this command encrypts the plain-text password given as well.maintain server_properties [ update <db-admin> ]Displays the following server properties from both the acserver.cnf file and the AccuRev database: SITE_SLICE_LOC, MASTER_SERVER, and PORT. In addition, the values from each location are compared and the command displays whether or not they match.When the update option is specified, the values that do not match are written from the acserver.cnf file into the database.Important! Whenever you edit the values for SITE_SLICE_LOC, MASTER_SERVER, or PORT in the acserver.cnf file, you must also run the maintain server_properties update command before the new values will take effect.For each AccuRev depot, displays the slice number (Slice#) and the full pathname to the directory within the repository that stores the data for that depot (Location). Use the all parameter to include deactivated (removed) slices in the listing. Use the chslice command to change the location of a slice.maintain su [ { -a | -r } <accountname> ]Add or remove a superuser account for working with element-level security (“EACL”s). If run with no arguments, maintain su displays a list of any superusers. See Element-Level Security (EACLs) on page 60 for details.Checks the storage containers in the specified depot’s data directory tree to verify that a storage container file (.sto) exists for each file version recorded in the depot database. It also reports CRC mismatches, which occur when the calculated checksum (CRC) of a .sto file does not match the checksum recorded in the corresponding version record.
| Borland |