Running Global Projects
Using Extracts with Global Projects : Deleting a Database that owns Extracts
Deleting a Database that owns Extracts
Deleting Databases, describes how to delete a database in a Global project, but the procedure is different if the database owns extracts. The conditions required to de-allocate and delete a database are quite complicated:
•
To create, delete or modify a working extract at a satellite:
•
the parent database of the working extract must be primary at the satellite
•
To de-allocate a database from a satellite:
•
The database must not be primary at the satellite
•
The database must not own working extracts at the satellite
•
To delete a database:
•
The database must not be allocated to any locations other than the Hub
•
The database must not own any extracts, either working or standard ones
Thus to delete a database that owns extracts (and may own working extracts) may involve doing a number of CHANGE PRIMARY commands to get rid of any working extracts at satellites where the database is secondary.
The procedure for deleting a database that owns extracts is summarised in the diagram below.
Note:
A DB does not need to be primary at the HUB, just as long as it is not primary at the location where it is being de-allocated
1974 to current year. AVEVA Solutions Limited and its subsidiaries. All rights reserved.
AVEVA Logo