Please ensure Javascript is enabled for purposes of website accessibility
Powered by Zoomin Software. For more details please contactZoomin

AVEVA™ Administration

MERGE CHANGES (Project Administration)

  • Last UpdatedFeb 20, 2024
  • 4 minute read

Function:

Merges the changes made to a Database (DB) over several sessions.

In a Global Project, this command can only be carried out when the administrator is administering the Primary Location of a DB.

Description:

Sessions are defined as the work done between SAVEWORK commands. They allow the administrator to track the changes made to a DB. If the administrator is not interested in the history, or they want to save disk space, they can merge the changes made in several sessions.

In a Global Project, the administrator can issue REMOTE MERGE commands if they are at the Hub or are administering the Primary Location of a DB, even if that is not their current Location. Refer to the REMOTE command for more examples.

After the administrator merges changes, some session data is deleted. The sessions remaining are those that the administrator has either kept deliberately, or stamped sessions, as these cannot be merged.

If an AVEVA Engineering session is merged, drawing revisions are not merged. The drawing revision data is not deleted.

With the FILEPURGE option all .SDB and .PIC files that become obsolete as of a session merge operation will be deleted as part of the operation. This is relevant only for PADD DBs.

Note:
If a DB owns an extract DB, the administrator cannot merge the linked session, that is the session which was current when the extract was created.

Note:
In a Global Project, spurious ‘lost bucket’ errors may be reported on the master DB if there are working extracts at other Locations.

Examples:

MERGE CHANGES HVAC/PADD AFTER SESSION 4 BEFORE SESSION 10

Merges all the changes to the HVAC/PADD DB after session 4 and before session 10, that is all changes made in sessions 5 to 9 will be combined. If there are any stamped sessions in sessions 5 to 9, they will be kept. The Team ID (HVAC) can be omitted if a current Team is set.

MERGE CHANGES HVAC/PADD AFTER STAMP/stamp_012 BEFORE STAMP /stamp_016

Merges all the changes to the HVAC/PADD DB for sessions that are after the session stamped with stamp_012 and before the session stamped with stamp_016. All changes made in stamped sessions that are between the sessions stamped with stamp_012 and stamp_016 will be combined. If there are any other stamped sessions, they will be kept. The Team ID (HVAC) can be omitted if a current Team is set.

MERGE CHANGES /HVAC BEFORE 10:30 31 / 8 / 01
MERGE CHANGES /HVAC BEFORE 10:30 31 AUGUST 2001

Merges all the changes to the HVAC DB before 10.30 am on the 31 August 2001. If the time is omitted, 11.59 is assumed. If the month is not given, the current month is assumed. If the year is not given, the current year is assumed. If there are any stamped sessions, they will be kept.

MERGE CHANGES PROJECT

Merges all the changes to all DBs in the Project, except stamped sessions. A range of dates may be specified, but not a session number.

MERGE CHANGES SYSTEM

Merges all the changes to the System DB. A date, session number or stamp cannot be specified. In a Global Project, the administrator must be administering the System DB and be at its Primary Location.

MERGE CHANGES GLOBAL

This command is only available in a Global Project, at the Hub. Merges all the changes to the Global DB. A date, session number or stamp cannot be specified.

Command Syntax for Standard (Non-Global) Project:

>- MERGE CHANGES -+- team -.
                  |        |
                  |--------+- db -.
                  |               |
                  |--- PROJECT ---AFTER ----.
                  |               |         |
                  |               ‘---------+-- <when> -.
                  |                         |           |
                  |                         ‘-----------+- BEFORE -.
                  |                                     |          |
                  |                                     ‘----------+- <when> ->
                  |                                                |
                  |--- SYSTEM -------------------------------------|

Note:
<BEFORE/AFTER> do not apply to the System or Global DB.

Command Syntax for GLOBAL Project:

When can be given in the form of a date or a session number, or, if the required sessions have been stamped, a stamp, as shown in the examples. Refer to Notes on Syntax Graphs, for the full syntax of <when>.

Note:
All the MERGE CHANGES syntax except MERGE CHANGES GLOBAL can be applied to a remote Location in a Global Project by prefixing the command by REMOTE <loc>, where <loc> is the Location identifier. MERGE CHANGES SYSTEM applies to the currently administered System DB.

Refer to the REMOTE command for examples.

Querying:

Q SESSION

Related Commands:

BACKTRACK (Project Administration)

REVERT (Project Administration)

REMOTE (Global Project Administration)

TitleResults for “How to create a CRG?”Also Available in