Switching the controller database v7

Suggest edits

The controller database is designated in the Replication Server Configuration file and determines the publication database to which the publication server and subscription server first connect on startup. See Controller database and Replication Server configuration file for more information.

You can't remove the current controller database from a replication system unless it's the last publication database remaining subordinate to the publication server. In other words, no other publication databases are managed by the publication server.

With more than one publication databases, if you want to remove the publication database currently designated as the controller database, you must first set another publication database as the controller. Then you can remove the publication database previously designated as the controller.

The publication database used as the controller can be the primary database of any single-master replication system or any primary node of a multi-master replication system. Any database type (Oracle, SQL Server, or Postgres) is acceptable as the controller database.

Note

If the controller database is an Oracle or a SQL Server publication database, you can't add a second Oracle or SQL Server publication database to create a second single-master replication system. For Replication Server to run more than one single-master replication systems consisting of Oracle or SQL Server publication databases, you must designate a Postgres publication database as the controller database.

Once you have multiple Oracle or SQL Server publication databases set up in single-master replication systems with a Postgres controller database, don't switch the controller database to an Oracle or SQL Server publication database.

Upon switching the controller database, the publication server updates the Replication Server configuration file so the parameters user, password, host, port, database, and type are set to the connection and authentication settings for the selected publication database.

To set another publication database as the controller database:

  1. Make sure the publication server whose node is the parent of the publication databases is running and registered in the Replication Server console you're using. See Registering a publication server to learn how to start and register a publication server.

  2. Select the Publication Database node corresponding to the publication database that you want to set as the controller database.

  3. From the context menu, select Set as Controller Database.

  4. In the Set as Controller Database confirmation box, select Yes.

    The selected publication database is now set as the controller database.

    The value Yes in the Controller Database field of the Property window indicates this database is the controller database.

The following shows the Replication Server configuration file after the controller database was switched to the primary node database MMRnode_b.

#xDB Replication Server Configuration Properties
#Thu Oct 15 14:42:35 GMT-05:00 2015
port=5444
admin_password=ygJ9AxoJEX854elcVIJPTw\=\=
user=MMRuser
admin_user=admin
type=enterprisedb
database=MMRnode_b
password=ygJ9AxoJEX854elcVIJPTw\=\=
host=192.168.2.22
← Prev

Managing a publication

Next →

Replicating DDL changes