ALLOCATE (Global Project Administration - Hub only)
- Last UpdatedMar 25, 2022
- 3 minute read
Function:
Allocates Databases (DBs) and copies them to a Location.
Description:
Each Location has a list of DBs that are allocated to it. The ALLOCATE command adds a DB to this list. A named DB or all DBs can be specified. The allocation can be deferred until a given time. The DBs must already exist at the Hub.
The Hub sends its own copy of the DB, or that of the Location’s parent, to the Location. This is not necessarily the most up-to-date copy.
Note:
The DB will also be allocated to all ancestors of the Location, if it is not already
allocated to them.
When a Draft DB is allocated, the picture files are not automatically copied with it. They will arrive with the next update.
By default, the allocated DBs will be Secondary, but the administrator can specify that they will be Primary. If a DB already exists at a Location, the administrator can change its Primary/Secondary status using the CHANGE command.
Several DBs can be allocated in the same operation using the ALLOCATE command.
In order for an extract DB to be used at a Satellite, all owning extracts must also have been allocated there.
Offline Locations
The ALLOCATE PRIMARY option cannot be used. Use ALLOCATE followed by CHANGE PRIMARY. The date option is not allowed.
Note:
ALLOCATE should be followed by a TRANSFER command to copy the DB to the Location. The CHANGE PRIMARY command should not be issued until this has been done.
Using Macros to Allocate Databases
The administrator will probably use a macro for long lists of DB allocations, for example, when a Project is first set up.
The allocation process may take some time if there is a slow link between Hub and Satellite and/or if DB sizes are large.
Note:
If a deallocation is in progress, then the allocation will stall until the deallocation
is complete before commencing.
Make sure that the administrator does not try to allocate a DB to the same Location twice. If the allocation appears to have failed, check the transaction DBs at both the Hub and the Satellite before attempting to repeat the command.
To check that the allocation has been successful, GETWORK and then navigate to the LOC element. Navigate to its DBALL (allocation list) member, and query its members. Wait until the DBALL element at both the Hub and the Satellite lists all the allocated DBs before continuing.
Note:
If the transaction DB for a Location is being allocated, this command is not recorded
in the transaction DB. It is not normally necessary to allocate it or change its Primary
Location explicitly.
Note:
The OVERRIDE PROPG option cannot be used with a deferred time.
Examples:
|
ALLOCATE PIPE/PIPE PRIMARY AT CAM Copies DB PIPE/PIPE from the current Location to Location CAM, making it Primary. ALLOCATE ALL AT LON AT 23:30 Copies all DBs which exist at the current Location but do not exist at Location LON, from the current Location to Location LON, at 2330 hours. The Primary/Secondary status will not be changed. ALLOCATE ALL AT OXF OVERRIDE PROPG Copies all DBs, including non-propagating DBs, which exist at the current Location but do not exist at Location OXF, from the current Location to Location OXF. The Primary/Secondary status will not be changed. Transaction DBs will not actually be copied, but empty DB files will be created at Secondary Locations. This command is useful when changing the Hub Location, since it makes sure that the DB allocation lists of the old and new Hub Locations match. |
Command Syntax:
|
>-ALLOCate -+- teamid -. |
Related Commands:
DEALLOCATE (Global Project Administration - Hub only)
HUBLOCATION (Global Project Administration - Hub only)
Querying:
|
>--- Q DBALL ---> |
At a Location, shows the list of allocated DBs. |
|
>--- Q DBLC ---> |
At a DB, shows the list of Locations that have the DBs allocated. |