BACKTRACK (Project Administration)

Administrator Command Reference Manual

Command Details : Detailed Descriptions of Commands : BACKTRACK (Project Administration)

BACKTRACK (Project Administration)

Allows you to backtrack a database to a previous session.

Sessions are defined as the work done between SAVEWORK commands. You can backtrack to the date or session number required, or, if the required session has been stamped, you can backtrack to the stamp. The current state of the database will be lost.

In a Global Project, this command can only be used when the databases are Primary at your administering Location.

In a Global project, use the REMOTE <loc> BACKTRACK command to backtrack a constructor database that is Primary at a remote Location, where <loc> is the Location identifier. See the REMOTE command for examples.

If you try to backtrack over any stamped sessions to a previous session, you will receive an error message. Backtracking over stamped sessions is not allowed. You must remove the stamp from the intervening sessions before you backtrack.

BACKTRACK removes the sessions permanently. The related command REVERT adds a session containing the data for the specified old session.

The backtracked database is written to a new file. This is done to avoid the situation where secondary database files in a Global project could still contain removed sessions. This situation would cause propagation failures if further sessions were added to the backtracked file.

Note:

For extracts, the REVERT command is used instead of BACKTRACK.


BACKTRACK HANGERS/PADD TO SESSION 4 Backtracks the HANGERS/PADD database to Session 4. The team id (HANGERS) and TO can be omitted. BACKTRACK HANGERS/PADD TO STAMP /stamp_007 Backtracks the HANGERS/PADD database to the session that has the stamp stamp_007. The team id (HANGERS) and TO can be omitted. BACKTRACK /HVAC 10:30 31 / 8 / 96 BACKTRACK /HVAC 10:30 31 AUGUST 1999 Backtracks the HVAC database to 10.30 am on the 31 August 1999. If the time is omitted, 11.59 p.m. is assumed. If the month is not given, the current month is assumed. If the year is not given, the current year is assumed. This example assumes that the team name has been specified using the SET command.BACKTRACK (continued) BACKTRACK PIPE/PIPE-A AT OXF TO SESSION 4 In a Global project, backtracks the PIPE/PIPE-A database at Location OXF to Session 4. The team id (PIPE) and TO can be omitted. (The database PIPE/PIPE-A must be Primary at the Location OXF,) and the System Database for OXF must be Primary at the current Location. See the ADMINISTER SYSTEM command.

Command Syntax:


>- BACKTrack -+- teamid -. \| \| ‘----------+- dbname TO <when> --->

Related Commands:

REVERT, MERGE CHANGES, REMOTE BACKTRACK, REMOTE REVERT - Global only

1974 to current year. AVEVA Solutions Limited and its subsidiaries. All rights reserved.