Merging Changes

When a MERGE CHANGES command is given on a Database (DB) with extracts, all the lower extracts have to be changed to take account of this. Thus doing a MERGE CHANGE on a DB with extracts should not be undertaken lightly.

The following restrictions apply:

• Any sessions linked to owned extracts must be preserved.

• There may be no users on any lower extracts.

  We recommend that the user should MERGE CHANGES at the lowest level of extracts first, and then work up the tree.

In a Global project, MERGE CHANGES can only be carried out at the location at which the database and all its descendant extracts are primary. The REMOTE MERGE command currently only handles leaf extracts and databases which do not own extracts.

See Merging Extract Databases for more information on merging extract databases.

Note:
BACKTRACK is not allowed for extract databases. REVERT must be used instead.