Allocating Databases to Locations

Before allocating databases, make sure that both daemons are running by selecting Query > Global States > Communications or by issuing a Ping command.

ALLOCATE commands can be given in sequence without waiting for the first allocate to finish. However, the same Allocate command should not be done twice, unless confident that the allocation has failed and that there is no entry in the transaction databases at either of the locations affected by the allocation.

When databases have been allocated to a location, databases cannot be added to MDBs until all allocations have been completed, so it is advisable to check the progress of allocations first.

It is advisable to use macro input for long lists of database allocations; for example:

ALLOCATE  <db name> PRIMARY at /Satellite

ALLOCATE  <db name> at /Satellite

and so on for each allocation.

This will most likely be the case when the Global project is initially created.

Note:
Once all allocations have been committed, it is worth checking that all commands are complete, whether the command has been executed through the GUI, or as a manual command. This is described in the next section.

If a de-allocation is in progress (see the DEALLOCATION command), then the allocation will stall until the de-allocation is complete before commencing.