Table of Contents Previous Next


10 Appendix : 10.3 Resolving Problems

Resolution: Occurs when registering a publication server or subscription server. Verify the user name and password you enter matches the admin user name and password in the xDB Replication Configuration file on the host you are running the publication server or subscription server. See Section 2.3.1.3.
Resolution: Only one publication database definition can be created for any given database. (Oracle is the exception whereby more than one publication database definition can be created for the same Oracle database if different Oracle user names are specified in each publication database definition.)
Resolution: Occurs whenever a Java RMI connection cannot be made to the publication server, the subscription server, or a database server. Can occur when registering a publication or subscription server, adding a publication database or a subscription database, or identifying the publication server for a new subscription. Verify you have entered the correct host IP address and port number of the server. Verify the server is running (see Section 10.3.4.2). If the server is running on Linux, verify that in the /etc/hosts file, the host name is mapped to the correct network IP address, which matches the IP address returned by the Linux /sbin/ifconfig command, and also matches the IP address you entered in the Host field of the dialog box. Alternatively, instead of modifying the /etc/hosts file, set configuration option java.rmi.server.hostname to the IP address of the publication or subscription server (see Section 10.4.1.7). Do not use the loopback address 127.x.x.x for this entry.
Resolution: Occurs when attempting to save a publication database definition. The publication server cannot connect to the database server network location given in the Add Database dialog box. Verify that the correct IP address and port for the database server are given. Verify that the database server is running and is accessible from the host running the publication server.
Resolution: Occurs when attempting a snapshot replication from a publication database configured with the log-based method of synchronization replication (that is, WAL based logical replication), and the additional concurrent connection for logical replication exceeds the current setting, n, of the max_wal_senders configuration parameter in the postgresql.conf file. Increase the value of max_wal_senders in the postgresql.conf file of the database server running the publication database. Restart the database server containing the publication database. See Section 2.2.10.
Resolution: Occurs when attempting to create a subscription. If there are no publications in the specified publication server, then this error message is displayed.
Resolution: The metadata database objects from a prior publication already exist in the schema under which the publication server is attempting to create new metadata database objects. Perform the operation described in Section 10.3.4.3.
Resolution: Make sure all publications subordinate to the publication database definition have been removed. If no publications appear under the Publication Database node in the xDB Replication Console replication tree and the error persists, there may be a problem with the control schema objects. Perform the operation described in Section 10.3.4.3.
Resolution: The control schema objects under the Oracle publication database user schema or under the Postgres or SQL Server schemas _edb_replicator_pub, _edb_replicator_sub, or _edb_scheduler cannot be deleted by the publication server. The control schema objects or schemas may have already been deleted. The publication database definition cannot be removed using the xDB Replication Console. Perform the operation described in Section 10.3.4.3.
Resolution: Occurs when attempting to remove the publication database currently set as the controller database. Select another publication database to be used as the controller database. Use the Set As Controller option in the publication databases’ context menu to set this database as the controller database. You can then remove the original publication database. See Section 7.7.
Resolution: Occurs when attempting to set a publication database as the controller database and the database is not accessible by the publication server. Verify that the correct IP address and port has been defined in the publication database definition. Verify that the database server is running and is accessible from the host running the publication server.
Resolution: Occurs when attempting to save a subscription database definition. The subscription server cannot connect to the database server network location given in the Add Database dialog box. Verify that the correct IP address and port for the database server are given. Verify that the database server is running and is accessible from the host running the subscription server.
Database connection cannot be added. FATAL: no pg_hba.conf entry for host "xxx.xxx.xx.xxx", user "user_name", database "db_name", SSL off
Resolution: Occurs when attempting to save a subscription database definition. The subscription server is not permitted to connect to the database at the network location given in the Add Database dialog box. Verify that the database host IP address, port number, database user name, password, and database identifier are correct. Verify there is an entry in the pg_hba.conf file permitting access to the database by the given user name originating from the IP address where the subscription server is running.
Resolution: Occurs when attempting to add a subscription database. Verify that the xDB Replication Configuration file on the host running the subscription server contains an entry for a valid controller database. Verify that a publication database has been defined under the publication server as the controller database and its connection information is recorded in the xDB Replication Configuration file. See Section 2.3.1.3.
Resolution: All database servers in a multi-master replication system must be of the same type – either all PostgreSQL (or Advanced Server installed in PostgreSQL compatible configuration mode); or all Advanced Server installed in Oracle compatible configuration mode. This error message is displayed when attempting to add a master node and the database server type differs from the database server type of the master definition node. See Section 10.1.3.3.
Resolution: When a master node of a multi-master replication system is deleted using the xDB Replication Console or the xDB Replication Server CLI, the control schema objects that were created in the master node are also dropped. These include schemas _edb_replicator_pub, _edb_replicator_sub, and _edb_scheduler. For the log-based method of synchronization replication there are shadow tables and triggers on the publication tables as well. If any of these control schema objects fail to be dropped, this error message is displayed. See Section 10.3.4.3 for directions on how to remove these control schema objects.
FATAL: no pg_hba.conf entry for host "xxx.xxx.xx.xxx", user "user_name", database "db_name", SSL off
Resolution: Occurs when attempting to save a publication database definition. The publication server is not permitted to connect to the database at the network location given in the Add Database dialog box. Verify that the database host IP address, port number, database user name, password, and database identifier are correct. Verify there is an entry in the pg_hba.conf file permitting access to the database by the given user name originating from the IP address where the publication server is running.
Resolution: Occurs when attempting to define a filter rule on a column with a binary data type in a publication table. Filter rules are not permitted on such columns. See Section 2.2.11.3.
Resolution: When adding a filter rule on a publication table, the same filter name or the same filter clause (WHERE clause) cannot be used more than once on a given table. Modify the duplicate filter name or filter clause so it is unique for the table.
Resolution: A snapshot replication must be performed before the first synchronization replication. Perform an on demand snapshot replication.
Resolution: This warning is given when localhost or 127.0.0.1 is specified as the host address of a replication system component. If is strongly recommended that all replication system components are identified by their specific IP address on the network.
Resolution: Either the user does not have the trigger creation privilege or there is a database server problem. The database server message is displayed as part of the error.
Resolution: A database server of type database_type cannot be used in a multi-master replication system. Only Advanced Server or PostgreSQL database servers may be used as master nodes in a multi-master replication system.
Resolution: When creating a subscription in a single-master replication system or creating a master node other than the master definition node in a multi-master replication system, only one filter may be selected for a given table. Uncheck the additional boxes in the Apply column under the Filter Rules tab if more than one box is selected.
Resolution: Occurs when creating an Oracle publication or subscription database definition. Copy the Oracle JDBC driver file ojdbcx.jar to subdirectory lib/jdbc of where the publication server or subscription server is installed on the host running the publication server or subscription server. Restart the publication server or subscription server.
Resolution: Occurs when attempting to add a second master node to a multi-master replication system, but no publication has been defined under the master definition node. Create a publication under the master definition node, then add the additional master nodes. See Section 6.2.3.
Resolution: Synchronization replication failed due to the unavailability of a target database. See the publication server log file for details. See Section 10.3.2.
Resolution: Master nodes are still defined in a multi-master replication system in which an attempt is being made to delete the publication from the master definition node. All master nodes (other than the master definition node) must be deleted first before deleting the publication from the master definition node. Perform this deletion process with the xDB Replication Console or xDB Replication Server CLI.
Resolution: Warning issued when you attempt to remove a publication with subscriptions associated with it. You can remove the publication, but the subscriptions are no longer usable and should be removed as well.
Resolution: Only one publication is supported in a multi-master replication system and only one such multi-master replication system can exist for an xDB Replication Server installation.
Resolution: You cannot perform synchronization replication on a snapshot-only publication. Perform snapshot replication instead.
operation_type operation is not allowed in restricted mode.
Resolution: The specified multi-master operation_type is not permitted in restricted mode. Restricted mode is applicable when the license evaluation period expires. See Section 10.4.7.
Resolution: Occurs when creating an Oracle or SQL Server publication database definition and the current controller database is not a Postgres database (that is, the controller database is an Oracle or SQL Server database). In order to create an Oracle or SQL Server publication database, create and designate a Postgres publication database as the controller database. See Section 7.7.
Parent table table_name is not selected when its child tables are part of the publication list.
Resolution: Table selected for a publication has a foreign key referencing a parent table that has not been chosen for the publication. This is only a warning that the parent table will not be part of the subscription.
Resolution: Occurs when attempting synchronization replication and the controller database is not accessible by the publication server. Verify that the correct IP address and port has been defined in the publication database definition of the controller database. Verify that the database server is running and is accessible from the host running the publication server.
Resolution: For a Postgres publication, verify that the publication database user has CREATE ON DATABASE privilege on the publication database, or the database user is a superuser.
Resolution: In Postgres, it is possible to create a table with no columns. A publication is not allowed to include a Postgres table with no columns since the corresponding subscription table cannot be created in Oracle.
Publication cannot be created. Publication publication_name already exists on the publisher server. Please choose a different name and then proceed.
Resolution: Publication names must be unique within a publication server. Enter a different publication name.
Publication cannot be created. Table schema.table_name replica identity is set to replica_identity_setting. To define a Filter, the table replica identity should be set to FULL.
Resolution: Occurs when a table filter is attempted to be defined on a publication table used in a log-based replication system. Use the ALTER TABLE statement to change REPLICA IDENTITY to FULL. See Section 2.2.11.3.
Publication cannot be created. Table table_name does not contain a primary key. Transactional replication is not supported for a non-pk table.
Resolution: All tables used for synchronization replication must have primary keys. Create a primary key on the table or add the table to a snapshot-only publication.
Resolution: For a Postgres publication that is not for snapshot-only, the publication database user must be able to create triggers on the publication tables. In order to do this, the publication database user must have the privilege to execute the ALTER TABLE statement on the publication tables and the publication database user must have CREATE and USAGE privileges on the schema containing the publication tables. Verify that one of the following is true: 1) All the tables in the publication are owned by the publication database user and the user has CREATE and USAGE privileges on the publication tables’ schemas, or 2) the publication database user is a superuser.
Publication cannot be removed. Reason: Publication publication_name cannot be removed. Reason: Error: cannot drop table _edb_replicator_pub.rrst_schema_table_name because other objects depend on it.
Resolution: PL/pgSQL custom conflict handler functions may exist in the master definition node that are dependent upon the publication’s shadow tables. Drop the custom conflict handler functions before deleting the publication.
Publication cannot be updated. Reason: The parent table schema.table_name is selected for removal while it has one or more child tables in the publication list. Make sure that parent-child dependency holds in the publication tables.
Resolution: Choose the child tables for removal as well as the parent table.
Resolution: A given publication cannot be used in both a multi-master replication system and a single-master replication system.
Resolution: The publication does not exist for a given subscription. The subscription is no longer usable and must be removed.
Resolution: Remove the subscription, remove tables from the publication, then add the subscription.
Resolution: Occurs when attempting to create the publication database definition and the specified publication database user does not have the privilege to create a schema in database db_name. Grant the CREATE privilege on the database to the publication database user
Resolution: Verify that the publication server is running. See Section 10.3.4.2. Verify that the database server hosting the controller database specified in the xDB Replication Configuration file is running and the publication server is connected to it. See Section 2.3.1.3.
Resolution: May be caused by characters in the publication data that are illegal for the character set of the subscription database. Check the snapshot replication failure log file or the database server log file. See Section 10.4.1.2.
Resolution: See Section 10.1.3 for supported database server configurations. Use Oracle products for Oracle to Oracle replication.
Resolution: Occurs when attempting to add a publication database definition with the log-based method of synchronization replication, and the max_replication_slots configuration parameter in the postgresql.conf file is not set to a large enough value to accommodate the additional database. Increase the value of the max_replication_slots parameter and restart the database server. See Section 2.2.10 for additional information.
Subscription subscription_name already exists on the subscriber server. Please choose a different name and then proceed.
Resolution: Subscription names must be unique within a subscription server. Enter a different subscription name.
Subscription subscription_name cannot be removed. Reason: Publication does not exist on the publication server.
Resolution: Warning issued if the subscription you are attempting to remove does not have an associated publication. You can still remove the subscription.
Resolution: You cannot remove a subscription database definition if there are subordinate subscriptions. Remove the subscriptions first.
Resolution: The Subscription node you are trying to select no longer represents an existing subscription. The subscription may have been removed by a concurrent xDB Replication Console or xDB Replication Server CLI session. Click the Refresh icon in the xDB Replication Console toolbar to display the current replication tree.
Resolution: Verify that the subscription server is running. See Section 10.3.4.2
Resolution: Synchronization replication failed to complete for all target databases in the multi-master replication system due to the unavailability of some target database. See the publication server log file for details. See Section 10.3.2.
Resolution: Oracle doesn’t log changes for a large object column. Such a column cannot be referenced in the triggers that log changes to the shadow tables. Use snapshot-only replication instead.
Resolution: Occurs when testing the connection of a publication or subscription database definition. The publication or subscription server cannot connect to the database server network location given in the Add Database dialog box. Verify that the correct IP address and port for the database server are given. Verify that the database server is running and is accessible from the host running the publication or subscription server.
Database connection information test failed. FATAL: no pg_hba.conf entry for host "xxx.xxx.xx.xxx", user "user_name", database "db_name", SSL off
Resolution: Occurs when testing the connection of a publication or subscription database definition. The publication or subscription server is not permitted to connect to the database at the network location given in the Add Database dialog box. Verify that the database host IP address, port number, database user name, password, and database identifier are correct. Verify there is an entry in the pg_hba.conf file permitting access to the database by the given user name originating from the IP address where the publication or subscription server is running.
Resolution: Verify that the database server is running. For Oracle, verify that the Oracle listener program lsnrctl is running.
Resolution: Occurs when attempting to add a publication database definition with the log-based method of synchronization replication (that is, WAL based logical replication), and the publication database user is not a superuser or does not have REPLICATION privilege. Grant the publication database user the appropriate privilege or specify a different database user who has the appropriate privilege for logical replication as the publication database user. See Section 2.2.10.
Resolution: Occurs when attempting to add a publication database definition with the log-based method of synchronization replication (that is, WAL based logical replication), and there is no entry in the pg_hba.conf file where the DATABASE field is set to replication for user_name. The pg_hba.conf file of the target database server must contain a replication entry for the publication database user name specified when creating the publication database definition. See Section 2.2.10.
Resolution: Occurs when attempting to add a publication database definition with the log-based method of synchronization replication (that is, WAL based logical replication), and the additional concurrent connection for logical replication exceeds the current setting, n, of the max_wal_senders configuration parameter in the postgresql.conf file. Increase the value of max_wal_senders in the postgresql.conf file of the database server running the publication database. Restart the database server containing the publication database. See Section 2.2.10.
Resolution: Occurs when attempting to create a publication database definition with the log-based method of synchronization replication (that is, WAL based logical replication), and the Postgres database server is not version 9.4 or later. Only Postgres database servers of version 9.4 or later support the log-based method of synchronization replication. See Section 2.2.10.
Resolution: The DDL statements in the text file specified for the DDL change replication feature contain syntax errors or are not supported by the DDL change replication feature. See Section 7.8.
Resolution: Occurs when attempting an operation such as performing synchronization replication or creating a schedule on a publication or subscription database that cannot be accessed by the xDB Replication Console. Verify that the publication and/or subscription servers are running. Verify that the database servers of the publication and/or subscription databases are running.
Resolution: Occurs when attempting to create an MMR publication database definition and the publication server is unable to create the control schema objects in the new publication database. This typically results when creating a second publication database definition and the publication server is unable to copy by snapshot the control schema objects from the controller database to the new publication database. The publication database user of the new publication database must be a superuser. In addition, in system catalog table pg_catalog.pg_authid, column rolcatupdate must be set to true for this superuser. See Section 10.4.4.
Unable to create Subscription subscription_name. Reason: Connection rejected: FATAL: no pg_hba.conf entry for host "xxx.xxx.xx.xxx" user "user_name", database "db_name", SSL off
Resolution: Occurs when creating a subscription. The subscription server running on host xxx.xxx.xx.xxx could not access the controller database. Verify that the pg_hba.conf file on the controller database server permits access from the subscription server host
Resolution: Occurs when creating a subscription. The subscription server running on host xxx.xxx.xx.xxx could not access the publication database. Verify that the pg_hba.conf file on the publication database server permits access from the subscription server host.
Resolution: The subscription database type is not supported for the intended publication database type. See Section 10.1.3.2 for a list of permitted source and target database server configurations.
Resolution: The subscription server was unable to create a subscription table definition in the intended target schema. Typically, the reason is that a table with the same name already exists in the target schema of the subscription database. This can occur if you create a subscription, then remove it, but fail to drop the table definitions created under the target schema, then try to create the subscription a second time.
Resolution: Occurs when attempting to create an SMR publication database definition and the publication server is unable to create the control schema objects in the new publication database. This typically results when creating a second publication database definition and the publication server is unable to copy by snapshot the control schema objects from the controller database to the new publication database. The publication database user of the new publication database must be a superuser. In addition, in system catalog table pg_catalog.pg_authid, column rolcatupdate must be set to true for this superuser. See Section 10.4.4.
Unable to perform snapshot for subscription subscription_name. Reason: DB-42501: com.edb.util.PSQLException: ERROR: permission denied for relation pg_class.
Resolution: Occurs when attempting a snapshot replication. The database user of the database receiving the snapshot must be a superuser. In addition, in system catalog table pg_catalog.pg_authid, column rolcatupdate must be set to true for this superuser. See Section 10.4.4.
Unable to perform snapshot for subscription subscription_name. Reason: org.postgresql.util.PSQLException: FATAL: no pg_hba.conf entry for host "xxx.xxx.xx.xxx", user "user_name", database "db_name", SSL off
Resolution: Occurs when attempting a snapshot replication. The publication server running on host xxx.xxx.xx.xxx could not access the subscription database. Verify that the pg_hba.conf file on the subscription database server permits access from the publication server host.
Unable to synchronize. Reason: FATAL: no pg_hba.conf entry for host "xxx.xxx.xx.xxx", user "user_name", database "db_name", SSL off
Reason: Occurs during an implicit synchronization following snapshot replication. The publication server running on host xxx.xxx.xx.xxx could not access the subscription server’s controller database. Verify that the pg_hba.conf file on the subscription server permits access from the publication server host using network address xxx.xxx.xx.xxx.
Resolution: The control schema objects in the publication database may have been deleted or corrupted. For an Oracle publication database the control schema objects are located in the publication database user’s schema. For a Postgres or SQL Server publication database the metadata database objects are located in schemas _edb_replicator_pub, _edb_replicator_sub, and _edb_scheduler. See Section 10.3.4.3.
Resolution: An Oracle publication database user must have CONNECT, RESOURCE, and CREATE ANY TRIGGER privileges.
Resolution: A new license key is required for multi-master replication operation. See Section 3.5
Resolution: A new license key is required for multi-master replication operation. See Section 3.5.
/var/log/xdb-x.x/mtk.log
POSTGRES_HOME\.enterprisedb\xdb\x.x\mtk.log
POSTGRES_HOME is the home directory of the Windows postgres account (enterprisedb account for Advanced Server installed in Oracle compatible configuration mode). The specific location of POSTGRES_HOME is dependent upon your version of Windows. The xDB Replication Server version number is represented by x.x.
See Section 10.4.1.1 for more information on setting log file options.
View the publication server and subscription server log files pubserver.log[.n] and subserver.log[.n] in the following directory:
POSTGRES_HOME\.enterprisedb\xdb\x.x
[.n] is an optional, integer suffix whose presence depends upon the logging.file.count configuration option described in Section 10.4.1.1.
POSTGRES_HOME is the home directory of the Windows postgres account (enterprisedb account for Advanced Server installed in Oracle compatible configuration mode). The specific location of POSTGRES_HOME is dependent upon your version of Windows. The xDB Replication Server version number is represented by x.x.
Note: The severity level of messages logged in these files can be controlled by a configuration option. See Section 10.4.1.1.
For Linux only: View the publication service and subscription service startup log files edb-xdbpubserver.log and edb-xdbsubserver.log as well as the service script log files edb-xdbpubserver_script.log and edb-xdbsubserver_script.log in directories /var/log/edb/xdbpubserver and /var/log/edb/xdbsubserver. These log files contain the output from the scripts used to start the publication server and subscription server, and can typically be used to confirm the port number on which the publication and subscription servers were started.
Note: The publication service and subscription service startup log files are not generated for Windows and Mac OS X operating systems.
See Section 2.3.1.3 for information on the xDB Replication Configuration file.
10.3.2.6 Oracle Errors
The directory given by parameter USER_DUMP_DEST contains errors given by user processes.
The directory given by parameter BACKGROUND_DUMP_DEST contains errors given by the Oracle background processes.
Step 1: Verify that the database server of the publication database, the database server of the subscription database (for single-master replication systems), and the database servers of the master nodes (for multi-master replication systems) are all running.
Step 2: When viewing information in the xDB Replication Console, click the Refresh icon in the toolbar to ensure you are viewing the most current information, especially after making a configuration change to your replication system.
Step 3: Verify that the publication server and the subscription server (for single-master replication systems) are running. If they are not running and cannot be started see Section 10.3.4.2.
Step 4: If you are using an Oracle publication or subscription database, verify that the Oracle JDBC driver file has been copied to the XDB_HOME/lib/jdbc directory. XDB_HOME is the location where you installed xDB Replication Server.
Step 5: Verify that the necessary privileges have been granted to the publication database user.
In the msdb database, verify that the database user mapped to the SQL Server login given in the publication database definition has EXECUTE and SELECT privileges on schema dbo.
For any database user that will be updating the publication tables, verify that these database users have EXECUTE, SELECT, and INSERT privileges on the schema containing the xDB Replication Server metadata database objects.
Step 6: Verify that the necessary privileges have been granted to the subscription database user.
Step 7 (For Linux only): Verify that the network IP address returned by the /sbin/ifconfig command either matches the IP address associated with the host name in the /etc/hosts file (see Section 5.1.6.2), or matches the IP address specified with the java.rmi.server.hostname configuration option in the publication and subscription server configuration files (see Section 10.4.1.7).
Note: The subscription server only applies to single-master replication systems.
Step 1: Check the pubserver.log and subserver.log files for errors.
Step 2: Check the log file of the database server running the controller database for errors.
Step 3: Verify that the user name and password in the xDB Replication Configuration file on the hosts running the publication server and subscription server match a database user name and password in the database server running the controller database that the publication server and subscription server are attempting to access.
Step 4: If the controller database is a Postgres database, verify that the pg_hba.conf file of its Postgres database server has entries that allow access to the controller database from the IP addresses of the hosts running the publication server and subscription server by the user name in the xDB Replication Configuration file.
In the following example, the SMR publication database edb as well as the three MMR master node databases mdnnode, mmrnode_a, and mmrnode_b are all managed by the same publication server, which connects to the controller database designated in the xDB Replication Configuration file. Thus, all publication databases edb, mdnnode, mmrnode_a, and mmrnode_b contain what should be the same control schema information.
shared_controller_repconsole
In the preceding example, subscription database subdb contains a control schema object that may have to be deleted if control schema deletion is performed on the publication database.
After you have performed this deletion process, single-master replication systems must then be recreated following the directions in sections 5.2 onward. A multi-master replication system must be recreated following the directions in sections 6.2 onward.
Step 1: Stop the publication server.
Step 2: Stop the subscription server.
Step 3: Look for the control schema objects contained within a publication database. In the example used in this section, pubuser is the publication database user name. The publication consists of two tables – dept and emp.
For Oracle only: See Section 5.2.4.1 for a list of Oracle control schema objects.
For SQL Server only: See Section 5.2.4.2 for a list of SQL Server control schema objects.
For Postgres only: See Section 5.2.4.3 for a list of Postgres control schema objects.
Step 4: If the schema that is supposed to contain the control schema objects (the publication database user name for Oracle, or the control schema you created or selected when configuring a SQL Server publication database along with _edb_replicator_pub, _edb_replicator_sub, and _edb_scheduler, or _edb_replicator_pub, _edb_replicator_sub, and _edb_scheduler for Postgres) is missing, or there are missing database objects under the control schema, then you may need to complete the process of removing all remaining control schema objects.
Step 5: For single-master replication systems, the subscription database contains a single control schema object in the form of a table named rrep_txset_health. See Section 5.3.4 for a listing of this control schema object for each type of subscription database.
Step 6: If at this point, all control schemas and control schema objects appear intact in all publication databases and all subscription databases, then chances are that the problem lies elsewhere. Do not go proceed with any further steps in this section. Instead, recheck the checklist in Section 10.3.3.
Step 7: Repeat this step for every publication database to delete its control schema and control schema objects.
For Oracle only: If the publication user name still exists, then log onto SQL*Plus or any other Oracle database administration utility and drop all control schema objects owned by the publication user. Alternatively, you can drop the publication database user along with its database objects using the cascade option, but the publication database user must be recreated and privileges reassigned if you intend to rebuild your replication systems. See Section 5.1.4 for directions on creating the publication database user. The following example illustrates use of the cascade option:
For SQL Server only: If any of the control schema objects listed in Step 3 still exist, then log onto the SQL Server command line program, sqlcmd, or SQL Server Management Studio and drop these objects. The following example assumes some of the control schema objects were created under schema pubuser. The other control schema objects are created under _edb_replicator_pub, _edb_replicator_sub, and _edb_scheduler. The publication tables are dept and emp located in schema edb.
The control schema objects under the _edb_replicator_pub schema as well as the schema itself are dropped as shown by the following:
The control schema objects under the _edb_replicator_sub schema as well as the schema itself are dropped as shown by the following:
The control schema objects under the _edb_scheduler schema as well as the schema itself are dropped as shown by the following:
The control schema objects under the pubuser schema are dropped as shown by the following:
For Postgres only: If any of the schemas _edb_replicator_pub, _edb_replicator_sub, or _edb_scheduler still exist in the publication database, drop the schema and all of its database objects. The following example shows a connection established in psql to the publication database edb. The DROP SCHEMA CASCADE statement is then used to drop the schemas.
Step 8: Repeat this step for every subscription database to delete its control schema and control schema object.
Delete this table in all subscription databases. For SQL Server and Postgres subscription databases, delete the parent schema _edb_replicator_sub as well. For Oracle subscription databases, the parent schema is not generated by xDB Replication Server, so it your decision as to whether to keep or delete the parent schema.
For Oracle only: The RREP_TXSET_HEALTH table is created in the subscription database user’s schema. Drop this table.
For SQL Server only: The rrep_txset_health table is created in the schema named _edb_replicator_sub. Drop this table and schema.
For Postgres only: The rrep_txset_health table is created in the schema named _edb_replicator_sub. Drop this table and schema.
Step 9: In the xDB Replication Configuration file, delete the lines containing the following parameters: user, password, host, port, database, and type.
Keep the lines with the following parameters: admin_user, admin_password, and license_key (if already present).
See Section 2.3.1.3 for information on the xDB Replication Configuration file. See Section 3.4 for the file system location of the xDB Replication Configuration file.
Step 10: Start the publication server.
Step 11: Start the subscription server.
Step 12: In the replication tree you should see the following:
Step 13: You will need to recreate the replication system as described in sections 5.2 onward for a single-master replication system. See sections 6.2 onward for a multi-master replication system.
As described in Section 2.2.10.2 logical replication slots are used for the log-based method of synchronization replication. While a log-based replication system is in use, these replication slots remain connected to the Postgres databases. When the replication system is removed, these replication slots are also deleted.
The active column indicates whether or not the replication slot is active.
To deactivate an active replication slot, first stop the publication server. If the active column of the replication slot now displays f for false then you can remove the replication slot.
The following now shows that replication slot xdb_79910_5 for database mmrnode has been deactivated:
Now, the dropped replication slot does not appear when the pg_replication_slots directory is queried:

10 Appendix : 10.3 Resolving Problems

Table of Contents Previous Next