More Notes on Allocation

Several databases can be allocated in the same operation using the Allocate windows. However, it is advisable to use a macro for long lists of database allocations; for example, when a project is first set up. Refer to the ALLOCATE command in Command Reference for further information.

Check that the allocation has completed successfully. If you select Database (DB) & Extracts from the Admin Elements window, a list of all the allocated databases is visible.

Alternatively, check that the allocation has completed successfully from the command line as described below, by listing the elements under the DBALL member (the allocation list) of the LOC (location) element at both the Hub and the Satellite.

A GETWORK must be done before listing the DBALL element, even at the Hub, as the Global daemon must write the updated DBALL element to the Global database, and the Global daemon is another ADMIN user.

For example, at location Cambridge:

Alternatively query the DBLC attribute of the Database.

The allocation process may take some time if there is a slow link between Hub and Satellite, if databases sizes are large, or if the daemon is busy with other operations (such as updates).

If the newly-allocated databases do not appear in the allocation list, wait a few minutes, GETWORK and repeat the Query. Allocation is successful when the DBALL list contains all the databases allocated.

Note:
Do not attempt to re-allocate a database unless you are sure that the allocation has failed ‑ check that there is no entry in the transaction databases (by selecting Utilities > Transactions to display the Command Transactions window) at either of the locations affected by the allocation.