Using the Replicator Server

The Replicator Server propagates replications from the local distribution queue to the target database.

This chapter describes:

• Parameters that determine Replicator Server behavior
• Monitoring replication
• How to configure and use the Replicator Server

This chapter assumes that you have configured the propagation scheme using either Visual DBA or the Replicator Manager.

Tools for Performing Replicator Server Tasks

Procedures pertaining to the Replicator Server can be performed using these tools or methods:

• Visual Performance Monitor
• The Performance Monitor in Visual DBA
• The Replication Monitor in Replicator Manager
• Commands entered at the command line

Tools for Monitoring Replicator

Ingres Replicator monitoring tasks can be performed using either Visual DBA or Visual Performance Monitor. As the smaller and simpler tool, Visual Performance Monitor is preferred.

For a discussion of the role of the Replicator Server, see Replicator Components.

Install Replicator Service on Windows

If you are configuring Ingres Replicator on Windows using the repmgr utility, you must install the Replicator service using the following procedure. The DBA who is the owner of one or more of the replicated databases must perform this procedure.

If you are configuring Ingres Replicator using Visual DBA, you are prompted to install the Replicator service and Visual DBA performs the install task for you.

To install the replicator service using command line, follow these steps:

1. Type the following command:

   repinst n

   where n is the number of servers.

   Repinst creates up to n Windows services to support an equal number of Replicator Servers.

2. Click Administrative Tools in the Control Panel, and then click Services.

   The Services dialog appears.

3. Highlight Ingres Replicator (XX) # , where (XX) is the installation identifier, and click Start.
4. Enter the Windows logon password of the DBA.

   If there are three DBAs, nyc_dba, sfo_dba, and rep_dba. The nyc_dba and rep_dba are in the same New York machine. Each of the three performs the replication startup procedure independently because the rep_dba cannot complete the procedure for the nyc_dba, and, of course, the sfo_dba must complete the procedure separately.

   Further, if there are three Replicator Servers in the New York machine—two run from the nyc_dba account and the third from the rep_dba account—either nyc_dba or rep_dba can run repinst 3; or nyc_dba can run repinst 2, and rep_dba runs repinst 3, creating an additional Replicator Server service. The nyc_dba must go to the Services Control Panel and enter the username and password for servers 1 and 2, and rep_dba must do the same for server 3.

For more information about the repinst command, see the Command Reference Guide.

How You Start Replicator Server

The Replicator Server allows replication to begin. You are ready to configure and start the Replicator Server after you have installed the Ingres Replicator software and configured your replication scheme.

You must configure and start the server for each database individually through the Performance Monitor in Visual DBA or the Replicator Monitor in Replicator Manager.

Note: Before you start a server, Change Recording must have been activated. If Change Recording is not active, there are no transactions for the server to propagate. For more information, see How Replication Is Activated or Activate Change Recording Window.

Visual DBA and Performance Monitor: To start the server, follow these steps:

1. Complete the Server Startup Worksheet.

   For details, see Server Startup Settings Worksheet.

2. Configure startup settings.

   For details, see Startup Settings Page (in online help).

3. Start the server.

   For details, see Starting a Replicator Server (in online help).

Replicator Manager: To start the server, follow these steps:

1. Complete the Server Startup Worksheet.

   For details, see Server Startup Settings Worksheet.

2. Configure startup settings.

   For details, see Edit the Configuration File.

3. Start the server.

   For details, see Start a Server.