User Management

Replication Server Users
User/Login	Server	Client	Usage
rs_user	Replication Server	Replication Server administrators and users	Executes commands on the replication server. The commands executed depend on the security level of the user and include commands such as creating replication definitions, subscriptions, and creating other users.
Replication Server login username rs_username	Replication Server	Replication Server users and Replication Agent	Replication Agent uses the rs_user user to send commands to the Replication Server. For example, replication definition commands and LTL commands. This user must have the permissions to send LTL, create, and drop replication definitions.
Primary database maintenance user	Primary database	Replicate Server	Executes DML at the primary database in the case of bi-directional replication. Use the maintenance user if you do not want the operations at the primary database to the sent to the replicate database. This user cannot be the same as the pds_username user.
Replicate database maintenance user	Replicate database	Replication Server	Executes DDL, DML, and stored procedures at the replicate database. The transactions applied by the maintenance user are not replicated out of the replicate database. This user cannot be the same as the pds_username user.
RSSD primary user rssd_username	Replication Server	Replication Agent	Replication Agent uses this user to login to the Replication Server RSSD for replication definition information. Replication Server provides a gateway for access to the RSSD. Replication Server users other than the Replication Agent can access the RSSD using the rs_username login. This user cannot be the same as the pds_username user.
RSSD maintenance user	Replicate RSSD	Replicate, Replication Server	Applies modifications to replicate RSSDs to coordinate with route information in the primary RSSD.

Replication Agent Users
User/Login	Server	Client	Usage
pds_username	Primary database	Replication Agent	Replication Agent uses this user login name to access primary database objects and to create, remove, or manage the transaction log objects in the primary database. The login name cannot be the same as the Replication Agent user for RSSD or the maintenance user of the primary database. For Replication Agents for Oracle, IBM DB2 UDB, and Microsoft SQL Server, the login name selects the data if you use direct load materialization. For Replication Agent for IBM DB2 UDB, this user must have sysdba permission to read DB2 logs and these permissions: SELECT permissions for reading the log. SELECT permissions on the required system and user tables. pds_username cannot be the same as the primary database maintenance user or the RSSD primary user.
Replication Agent administrator ra_username	Replication Agent	Replication Agent user and administrator	Administers the Replication Agent instance.

Database Users
User/Login	Server	Client	Usage
Data server login	Primary database	Primary database user	Data server login names are used with a client application to connect to a data server. This is the login used by the application or user whose activities in the primary database (for example, DML, DDL, and stored procedures) are to be replicated.
Primary database administrative user	Primary database	Primary database user and Replication Agent	Creates other users in the primary database and performs configuration activities such as granting permissions to database objects. The Replication Agent for IBM DB2 UDB requires this user to read the DB2 log. The Replication Agent for Microsoft SQL Server required this user to add system stored procedures.
ASM username asm_username	Primary database	Replication Agent	(Oracle only) Replication Agent uses this user to access the Oracle ASM server.
ddl_username	Replicate database	Replication Server	The ddl_username user has the permissions to perform tasks on behalf of other users. This allows consistent object ownership across primary and replicate database.