Master Site Maintenance and Propagation
Thesite at which you create a replication group is automatically the master definition site for that replication group. Of course, for replication to have any meaning, you will need to add at least one master site. The DBMS_REPCAT package includes procedures for adding and removing master sites. You also need to control how DML changes propagate between sites; the DBMS_DEFER_SYS package contains the procedures for configuring the properties of propagation.
The following procedures manipulate master sites:
- DBMS_REPCAT. ADD_MASTER_DATABASE
Adds a master database to the specified replication group. The call can create the objects if they do not already exist at the master site, populate replicated tables if they do not contain any data, or utilize the tables and data that are already at the new master site.
- DBMS_REPCAT. RELOCATE_MASTERDEF
Changes the location of a replication group’s master definition site. This procedure is useful if the existing master definition site becomes unavailable or otherwise irrelevant.
- DBMS_REPCAT. REMOVE_MASTER_DATABASES
Removes a master site from a replication group.
Refer to Appendix A for the complete API reference to these procedures.
Adding a Master Site
If you are creating a brand new replication group, your primary tasks are to instantiate the data at all master sites, generate replication support for all objects, and add all sites to the environment. There are a number of ways to accomplish these tasks, ...