Administrator Command Reference Manual
Command Details : Detailed Descriptions of Commands : ALLOCATE (Global Project Administration - Hub only)
ALLOCATE (Global Project Administration - Hub only)
Function:
Allocates databases and copies them to a Location.
Description:
Each Location has a list of databases that are allocated to it. The ALLOCATE command adds a database to this list. A named database or all databases can be specified. The allocation can be deferred until a given time. The databases must already exist at the Hub.
The Hub sends its own copy of the database, or that of the Location’s parent, to the Location. This is not necessarily the most up-to-date copy. Note that the Database will also be allocated to all ancestors of the Location, if it is not already allocated to them.
When a DRAFT Database is allocated, the picture files are not automatically copied with it. They will arrive with the next update.
By default, the allocated databases will be Secondary, but you can specify that they will be Primary. If a database already exists at a location, you can change its Primary/Secondary status using the CHANGE command.
Several Databases can be allocated in the same operation using the ALLOCATE command.
In order for an extract database 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 that ALLOCATE should be followed by a TRANSFER command to copy the database to the location. The CHANGE PRIMARY command should not be issued until this has been done.
Using Macros to Allocate Databases
You will probably use a macro for long lists of databases 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 databases sizes are large. Note that if a de-allocation is in progress, then the allocation will stall until the de-allocation is complete before commencing.
Make sure that you do not try to allocate a database to the same location twice. If the allocation appears to have failed, check the transaction databases 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 databases before continuing.
Note:
If the transaction database for a location is being allocated, this command is not recorded in the transaction database. 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 database PIPE/PIPE from the current Location to Location CAM, making it Primary.
ALLOCATE ALL AT LON AT 23:30
Copies all databases which exist at the current Location but do not exist at Location LON, from the current Location to Location LON, at 2330 hrs. The Primary/Secondary status will not be changed.
ALLOCATE ALL AT OXF OVERRIDE PROPG
Copies all databases, including non-propagating databases, which exist at the current Location but do not exist at Location XF, from the current Location to Location OXF. The Primary/Secondary status will not be changed. Transaction databases will not actually be copied, but empty database 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 -.
            |          |
            |----------+- dbname -+-------------.
            |                     |             |
            |                     |- PRIMary ---|
            |                     |             |
            |                     ‘- SECOndary -+-AT loc-+-AT <time>----.
            |                                            |              |
            |                                            ‘--------------+->
            |
            ‘- ALL ---------------------------AT loc-+-AT <time>-------.
                                                     |                 |
                                                      ‘-OVERride PROPG -+->
Related Commands:
DEALLOCATE, CHANGE dbname PRIMARY, HUBLOC, TRANSFER
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
1974 to current year. AVEVA Solutions Limited and its subsidiaries. All rights reserved.
AVEVA Logo