Recovering the Primary Location

This option can only be used if a change of primary location has failed: it cannot be used to reverse a successful change. It is only available at the Hub.

The Recover Primary Location window is displayed when you select Data > Recover > Database > Primary Location on the main Admin menu bar.

The Transient Databases list gadget contains a list of project databases that have their PRVRF (previous reference) attribute set. This attribute is only set when a change of primary location is in progress. The attribute is reset to null when the change of primary location is complete. Several databases can be selected.

Note:
If, after the window is displayed, the daemon completes a command that affects the list of databases, the list can become out of date. In this situation, an attempt to recover the primary location for the database will fail (because, for example, the change of primary location has been completed successfully).

Recovery of the primary location is normally done automatically if a change operation applied to a primary location Db fails - check the progress of the command in the transaction database. An explicit recover operation applied to a primary location Db should only be used as a last resort. It is normally only required when daemons are down or for offline locations. It is also required if a create extract operation fails before it has issued ALLOCATE commands. (Refer to Command Reference (CHANGE, RECOVER, CREATE EXTRACT and ALLOCATE commands)).