Administrator Command Reference Manual
Command Details : Detailed Descriptions of Commands : MERGE CHANGES (Project Administration)
MERGE CHANGES (Project Administration)
Function:
Merges the changes made to a database over several sessions.
In a Global Project, this command can only be carried out when you are administering the Primary Location of a Database.
Description:
Sessions are defined as the work done between SAVEWORK commands. They allow you to track the changes made to a database. If you are not interested in the history, or you want to save disk space, you can merge the changes made in several sessions.
In a Global project, you can issue REMOTE MERGE commands if you are at the Hub or are administering the Primary location of a database, even if that is not your current location. See the REMOTE command for more examples.
After you merge changes, some session data is deleted. The sessions remaining are those that you have either kept deliberately, or stamped sessions, as these cannot be merged.
Note:
If a database owns an extract database, you 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 database 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 database 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 database 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 database 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 databases 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 database. A date, session number or stamp cannot be specified. In a Global project, you must be administering the System database 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 database. 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:
>- MERGE CHANGES -+- team --.
                  |         |
                  |---------+- db -.
                  |                |
                  |--- PROJECT ----+- AFTER -.
                  |                |         |
                  |                ‘---------+-- when -.
                  |                          |         |
                  |                          ‘---------+- BEFORE -.
                  |                                    |          |
                  |                                    ‘----------+- when -.
                  |                                                        |
                  |--- SYSTEM ---------------------------------------------|
                  |                                                        |
                  ‘--- GLOBAL ---------------------------------------------+-->
where 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. See 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 database.

See the REMOTE command for examples.
Related Commands:
BACKTRACK, REVERT, REMOTE
Querying:
Q SESSION
1974 to current year. AVEVA Solutions Limited and its subsidiaries. All rights reserved.
AVEVA Logo