Skip to main content

Connection and startup issues

Troubleshoot common problems with data replication connection and startup

Abstract

Fixing common problems with data replication connection and startup

  1. Use the ctinfo utility to check if replication is enabled for the file.

    ctinfo yourreplicatedfile.dat  ADMIN ADMIN FAIRCOMS

  2. Look for the ctREPLICATE.

    Extended File Mode Details:

	ctREPLICATE      : file is replicated

    1. If replication is not enabled for the file:

      1. Check that the REPLICATE option is properly specified in ctsrvr.cfg.

      2. Add DIAGNOSTICS REPLICATE to ctsrvr.cfg.

        Note

        When opening a file, a message is logged if replication cannot be enabled for the file.

    2. If replication is enabled for the file:

      1. Check that the Replication Agent is running and is properly connected to source and target.

      2. Use the ctrepd utility and/or Replication Agent change log to check source server transaction log entries.

      3. Enable the log_change_details option in ctreplagent.cfg.

      4. Check the replication exception log for errors:

        1. Ensure that the Replication Agent opened the file on the target server.

        2. Check for any failures when applying adds/deletes/updates.

  3. If you are using two-way replication or multiple Replication Agents connected to a server, set the unique_id option in the Replication Agent configuration file so that each Replication Agent has its own unique ID.

  4. If you are doing two-way replication between servers on the same machine, use the REPL_NODEID option in both servers' configuration files to set unique node IDs for the servers.

  5. If you use localhost or the DNS name for source_server or target_server in ctreplagent.cfg, you will need to use REPL_NODEID.