User ID requirements

The replication programs must run under a dedicated user ID with database administrator privileges. The apply program runs under this user ID, which also allows the capture program to identify the changes that are applied by the apply program and not replicate them back to the originating system. This user ID should not be used by any user applications.

The user ID requires Db2® DBADM privileges so that the capture program can read the Db2 recovery log at the source and the apply program can update all replicated user tables at the target.

You can use the following GRANT statements:

GRANT DBADM ON DATABASE TO USER repl_user;
GRANT EXECUTE ON PROCEDURE SYSPROC.ADMIN_SET_MAINT_MODE TO USER repluser;

If you are using Windows Active Directory or LDAP, replication also requires that the bluadmin user ID exists.

You can use the following curl command to validate the replication user ID:

curl --user 'repluser_ID:repluser_password'--insecure -X GET "https://localhost:8443/dbapi/v3/users/bluadmin"
Note:

On Db2 Warehouse SaaS, the user ID QREPADMIN is reserved for replication purposes and should not be altered or restricted in any way to ensure correct and continuous working operation.