Common problems checklist v7

Use the following checklist to verify that the proper configuration steps were followed. Omitting one or more of these steps is a common source of errors.

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 primary nodes (for multi-master replication systems) are all running.

2. When viewing information in the Replication Server console, select Refresh in the toolbar to ensure you are viewing the most current information, especially after making a configuration change to your replication system.

3. Verify that the publication server and the subscription server (for single-master replication systems) are running. If they aren't running and can't be started, see Starting the publication server or subscription server.

4. If you're using an Oracle publication or subscription database, verify that the Oracle JDBC driver file was copied to the XDB_HOME/lib/jdbc directory. XDB_HOME is the location where you installed Replication Server.

   See Enabling access to Oracle.

5. Verify that the necessary privileges were granted to the publication database user.

   For an Oracle publication database, verify that the publication database user has CONNECT, RESOURCE, and CREATE ANY TRIGGER privileges.

   See Oracle publication database.

   For a SQL Server publication database, verify the following:

   • 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.
   • In the publication database, verify that the database user mapped to the SQL Server login given in the publication database definition has its default schema set to the schema containing the Replication Server metadata database objects.
   • For the same database user, verify that this database user is either the owner of the schema containing the Replication Server metadata database objects or has the following privileges on this schema: ALTER, EXECUTE, SELECT, INSERT, UPDATE, and DELETE.
   • For the same database user, verify that this database user has CREATE TABLE and CREATE PROCEDURE privileges.
   • For the same database user, verify that this database user has ALTER privilege on the publication tables.
   • 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 Replication Server metadata database objects.

   See SQL Server publication database.

   For a Postgres publication database in a single-master replication system, verify that the publication database user is a superuser and has the privilege to modify pg_catalog tables. See Postgres publication database.

   For the primary definition node in a multi-master replication system, verify that the publication database user is a superuser and has the privilege to modify pg_catalog tables. See Preparing the primary definition node.

   For a primary node other than the primary definition node in a multi-master replication system, verify that the primary node database user is a superuser and has the privilege to modify pg_catalog tables. See Preparing more primary nodes.

6. Verify that the necessary privileges were granted to the subscription database user.

   For an Oracle subscription database, verify that the subscription database user has CONNECT and RESOURCE privileges.

   For a Postgres subscription database, verify that the subscription database user is a superuser and has the privilege to modify pg_catalog tables. See Preparing the Subscription Database.

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 Network IP addresses) or matches the IP address specified with the java.rmi.server.hostname configuration option in the publication and subscription server configuration files (see Assigning an IP address for remote method invocation).