MERGE CHANGES on Extracts

When a 'MERGE CHANGE' operation is performed on a 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 opposite is not needed (that is, MERGE CHANGES on a child does not require the parent extract to be merged).

The following restrictions apply to MERGE CHANGES:

1. Any sessions 'linked' to child extracts are preserved.

2. There may be no users on any lower extracts.

To minimize the sessions preserved in (1) it is suggested that a bottom up approach is followed when doing 'MERGE CHANGES'.