To use the SQL Replication programs, you need to ensure
that user IDs that operate the replication programs or use the replication
tools have the correct authorization on local and remote systems.
Authentication requirements on Linux, UNIX, and Windows
SQL Replication does not require you to use any specific
type of authentication. You should use the compatible authentication
type that best meets your business needs.
Authorization requirements for administration
To set up replication, you run generated SQL to create
objects, and bind plans and create SQL packages (System i®). Authorities required for these tasks vary by operating system.
Authorization requirements for the Capture program
The user ID that runs the Capture program must be able
to access the DB2® system catalog, access and update all replication
control tables on the Capture control server, and execute the Capture
program packages.
Authorization requirements for the Apply program
The user ID that runs the Apply program must be able to
access the DB2 system catalog, access and update all replication
control tables on the Capture control and target server, and execute
the Apply program packages.
Authorization requirements for Capture triggers on non-DB2 relational databases
If you are replicating from a non-DB2 database, Capture
triggers are used to capture changes from the source. Remote user
IDs (for example, from user applications) that change the remote source
tables need authority to make inserts into the CCD table.
SQL Replication