EXTRACT (Project Administration)

Administrator Command Reference Manual

Command Details : Detailed Descriptions of Commands : EXTRACT (Project Administration)

This command allows you to release, issue, drop and refresh extract databases.


FLUSH	Writes the changes back to the parent extract. The Extract claim is maintained. The extract is refreshed with changes that have been made to its owning database.
FLUSH RESET	A flush reset command will completely clear the flush stack for the extract. In most cases the system will resolve any dependencies between issued flush commands, including any resets required after failed flush commands. Only as a last resort should the user consider issuing a Flush Reset command.
FLUSHW	(Flush without refresh) Writes the changes back to the parent extract. The Extract claim is maintained. The extract is not refreshed. Ordinary Flush should be used in preference.
REFRESH	Refreshes any extract in the database hierarchy with changes that have been made to its parent extract.
FULLREFRESH	Refreshes an extract and all its parent extracts ‑ its ancestors. A full refresh takes place from the top of the database hierarchy downwards, ending with a refresh of the extract itself. Each extract is refreshed with changes that have been made to its parent extract.
ISSUE	Writes the changes back to the parent extract, and releases the extract claim.
RELEASE	Releases the extract claim: this command can only be used to release changes that have already been flushed.
DROP	Drops changes that have not been flushed or issued. The user claim must have been unclaimed before this command can be given.

Note:

That unlike the constructor modules, you can only perform these operations on a complete database in ADMIN, and so extract claiming has no meaning in ADMIN. For general information about using extracts in projects, see the Administrator User Guide. For information about using extracts in Global projects, see Running Global Projects.

In a Global project, Flush, release and issue may be executed remotely if the parent extract is not primary at the current location. In this case, FlushW is used and the database must be explicitly refreshed after completion of the flush.

Offline locations:

Extracts cannot be used which are primary at an offline location unless the entire extract hierarchy is primary at the offline location. This is because claim, flush and release commands can only be issued locally. There is no mechanism at an offline location to claim (etc.) from an online location.

Examples:


EXTRACT FULLREFRESH DB PIPE/PIPE-X1 Refreshes all parent extracts in the database hierarchy above PIPE/PIPE-X1, ending by refreshing PIPE/PIPE-X1 itself with changes to its parent extract. EXTRACT REFRESH DB PIPE/PIPE-X1 Refreshes database PIPE/PIPE-X1 with changes to its parent extract.
EXTRACT RELEASE DB PIPE/PIPE-X1 Releases all extract claims in database PIPE/PIPE-X1. EXTRACT ISSUE DB PIPE/PIPE-X1 Issues all changes to database PIPE/PIPE-X1 and releases the extract claim.
EXTRACT FLUSH DB PIPE/PIPE-X1 Writes the changes to database PIPE/PIPE-X1 back to its parent extract, but keeps the elements claimed to the extract. Also, PIPE/PIPE-X1 is refreshed with changes to its owning database. EXTRACT FLUSHW DB PIPE/PIPE-X1 Writes the changes to database PIPE/PIPE-X1 back to its parent extract, but keeps the elements claimed to the extract. PIPE/PIPE-X1 is not refreshed.
EXTRACT DROP DB PIPE/PIPE-X1 Drops all changes to database PIPE/PIPE-X1. EXTRACT FLUSH RESET DB PIPE/PIPE-X1 Undo any failed or incomplete flushes on this database.

Command Syntax:


>-- EXTRACT -+- FLUSH --+------------. \| \| \| \| ‘--- RESET --\| \|- FLUSHWithoutrefresh -\| \| \| \|- RELEASE -------------\| \| \| \|- ISSUE ---------------\| \| \| \|- DROP ----------------\| \| \| \|- FULLREFRESH ---------\| \| \| ‘- REFRESH -------------+- DB - dbname -->

Note:

In ADMIN, you cannot carry out partial operations as you can in the constructor modules. The commands can only be applied to entire DBs.