Replication Agent Connections

A Replication Agent sends data to Replication Server. Replication Agent logs in to the Replication Server, connects to the Replication Agent User thread of a Replication Server connection, and communicates with Replication Server over that connection.

The implications of the Replication Agent connections:

A valid user ID, which the Replication Agent uses to log in to the Replication Server, must be defined at the Replication Server.
The Replication Agent user ID must be granted connect source permission in Replication Server. connect source permission allows the Replication Agent to send commands that are valid only on a Replication Agent User thread.
The Replication Agent must record this user ID and associated password.
The Replication Agent must record the server and database portions of the Replication Server connection definition to identify and connect to the correct Replication Agent User thread.
The user_name and password defined in the Replication Server create connection command may be a valid user ID and password for the primary database.

Note: Replication Agent for Oracle, Microsoft SQL Server and IBM DB2 UDB for UNIX, requires the user_name and password to be valid and reports an error if the user is not found in the primary database.

The Replication Agent validates that the connection user_name exists in the primary database. However, Replication Server does not know if (or when) a DSI thread will be used. Therefore, the user ID and password must be valid in case the DSI thread is active.

Note: The requirement for a valid primary database user ID varies by Replication Agent. Some Replication Agents do not require (nor do they check for) a valid user ID on the Replication Server connection.