DEALLOCATE (Global Project Administration - Hub only)

Administrator Command Reference Manual

Command Details : Detailed Descriptions of Commands : DEALLOCATE (Global Project Administration - Hub only)

DEALLOCATE (Global Project Administration - Hub only)

Function:

Removes databases from the list of databases allocated to a Location.

A named database or all databases can be specified. The databases must be Secondary at the Location.

If you try to de-allocate a database from a Location which has a Descendant Location, and the database is also allocated to the Descendant, you will be warned of the existence of the Descendent allocation, and no action will be taken. You must use the INCLUDING DESCENDANTS option to de-allocate the database from all Descendant Locations as well.

When a de-allocation command is in progress, the location is locked against Allocate commands. This lock is set when the Deallocate command is issued, and released by the daemon once the database(s) have been deleted at the location. The Allocate command can still be executed, but will stall until the full de-allocation is complete. Locking only applies to the locations where dBs are being deallocated, and other locations should not be affected.

The transaction database for the location is not de-allocated when de-allocating all databases.

Occasionally it is necessary to perform routine housekeeping and other maintenance on satellite databases and then it is advantageous to be able to deallocate them temporarily. To do this we can use the KEEPMDBS option. When the database is reallocated, it becomes available once more after the MDB is reselected.

Note:

When a user at a satellite accesses an MDB which contains a de-allocated database it will be treated as a deferred database. This may lead to unexpected errors since attributes in other databases may still contain references to this database.

See the guide Running Global Projects for more information about de-allocating databases that have extracts.


DEALLOCATE PIPE/PIPE AT CAM Removes the database PIPE/PIPE from Location CAM. The database must not exist at any Locations which are descendants of CAM. DEALLOCATE HVAC/HVAC AT OXF INCLUDING DESCENDANTS Removes the database HVAC/HVAC from Location OXF and all descendants of OXF.
DEALLOCATE ALL AT LON Removes all databases which exist at Location LON. Note that you cannot use the INCLUDING DESCENDANTS option with ALL. DEALLOCATE PIPE/PIPE KEEPMDBS AT CAM Temporarily deallocates and makes unavailable for use database PIPE/PIPE, which exists at Location CAM.

Command Syntax:


>- DEALLOC/ATE --- ALL ---+--- KEEPMDB/S --. \| \| ‘----------------+--- AT --- loc ---> >- DEALLOC/ATE - teamid - dbname -+- KEEPMDB/S -. \| \| ‘------------+- AT - loc -+-INC/LUDING - DESCEND/ANTS-> \| ‘------

The KEEPMDBS option means that the database will not be removed from MDBs at the satellite although its database file will be deleted and the database removed from the location's allocation list. This option is useful when a database is being de-allocated temporarily for housekeeping procedures. A replacement database with the same details will be available for use immediately it is re-allocated without any need to modify MDBs.

SORTAL/LOCATE --- loc --->

This command sorts extract databases in a location's list of allocated databases into master-child-grandchild order, so that extract owners precede extract children. Note that this command will have no effect until the relevant databases have been allocated.

Related Commands:

ALLOCATE, CHANGE


At a location:	>--- Q DBALL
At a Database:	>--- Q DBLC --->

1974 to current year. AVEVA Solutions Limited and its subsidiaries. All rights reserved.