Please ensure Javascript is enabled for purposes of website accessibility
Powered by Zoomin Software. For more details please contactZoomin

AVEVA™ Engineering

DEALLOCATE (Global Project Administration - Hub only)

DEALLOCATE (Global Project Administration - Hub only)

  • Last UpdatedJan 30, 2025
  • 3 minute read

Function:

Removes Databases (DBs) from the list of DBs allocated to a Location.

Description:

A named DB or all DBs can be specified. The DBs must be Secondary at the Location.

If the administrator tries to deallocate a DB from a Location which has a descendant Location, and the DB is also allocated to the descendant Location, the administrator will be warned of the existence of the descendant allocation, and no action will be taken. The administrator must use the INCLUDING DESCENDANTS option to deallocate the DB from all descendant Locations as well.

When a deallocation 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 DBs have been deleted at the Location. The ALLOCATE command can still be executed, but will stall until the full deallocation is complete. Locking only applies to the Locations where DBs are being deallocated, and other Locations should not be affected.

The transaction DB for the Location is not deallocated when deallocating all DBs.

Occasionally, it is necessary to perform routine housekeeping and other maintenance on Satellite DBs and then it is advantageous to be able to deallocate them temporarily. To do this, use the KEEPMDBS option. When the DB 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 deallocated DB, it will be treated as a deferred DB. This may lead to unexpected errors since attributes in other DBs may still contain references to this DB.

For more information about deallocating DBs that have extracts, refer to Running Global Projects.

Examples:

DEALLOCATE PIPE/PIPE AT CAM

Removes the DB PIPE/PIPE from Location CAM. The DB must not exist at any Locations which are descendants of Location CAM.

DEALLOCATE HVAC/HVAC AT OXF INCLUDING DESCENDANTS

Removes the DB HVAC/HVAC from Location OXF and all descendants of OXF.

DEALLOCATE ALL AT LON

Removes all DBs which exist at Location LON.

Note:
The administrator cannot use the INCLUDING DESCENDANTS option with ALL.

DEALLOCATE PIPE/PIPE KEEPMDBS AT CAM

Temporarily deallocates and makes unavailable for use the DB PIPE/PIPE, which exists at Location CAM.

Command Syntax:

>- DEALLOC/ATE --- ALL ---+--- KEEPMDB/S --.
                          |                |
                          ‘----------------+--- AT ---- loc --->

>- DEALLOC/ATE - teamid - dbname -+- KEEPMDB/S -.
                                  |             |
                                  ‘-------------+- AT -- loc - cont.

cont.

-+- INC/LUDING -- DESCEND/ANTS->
  |
  ‘------ SORTAL/LOCATE --- loc --->

The KEEPMDBS option means that the DB will not be removed from MDBs at the Satellite, although its DB file will be deleted and the DB removed from the Location's allocation list. This option is useful when a DB is being deallocated temporarily for housekeeping procedures. A replacement DB with the same details will be available for use immediately it is reallocated without any need to modify MDBs.

This command sorts extract DBs in a Location's list of allocated DBs into master-child-grandchild order, so that extract owners precede extract children.

Note:
This command will have no effect until the relevant DBs have been allocated.

Related Commands:

ALLOCATE (Global Project Administration - Hub only)

CHANGE (Project definition)

Querying:

At a Location:

>--- Q DBALL

At a DB:

>--- Q DBLC --->

TitleResults for “How to create a CRG?”Also Available in