Running Global Projects
Using Extracts with Global Projects : Using Extracts in MODEL : Flushing Changes
Flushing Changes
When an extract user makes changes and saves them, they are stored in the extract. These changes can be made available to users in other extracts using the EXTRACT FLUSH command.
The FLUSH command operates on a single element or a database or a collection of elements. The changes to these elements will be made available in the parent extract.
If changes need to be made available in the master database, it will be necessary to flush the changes up through each level of extracts. Users accessing extracts in other branches of the extract tree will need to use EXTRACT REFRESH to see the changes (or EXTRACT FULLREFRESH, if the user’s extract is part of a multi-level extract hierarchy and is itself owned by another extract).
The following diagram illustrates the sequence of commands that need to be given so that a user working on extract B2 will be able to see the changes made by a user working on extract A2.
The Global daemon will only be involved in the flush process if the user is flushing changes to a secondary database / extract from their current primary extract.
Note:
If a flush fails, the database needs to be reset to allow subsequent Flushes and Refreshes to work. This is normally done automatically as part of the Global Flush command. In exceptional circumstances, the EXTRACT FLUSH RESET command may be used to undo the failed flush. However this will not normally be necessary.
This situation can arise when more than one user is issuing the same database extract. Flush and release commands might then be processed in the wrong order, causing a flush to fail and preventing subsequent refreshes of the extract.
1974 to current year. AVEVA Solutions Limited and its subsidiaries. All rights reserved.
AVEVA Logo