Why does Qlik Replicate require SYSADM user privilege to access DB2 records and transaction logs?

Melissa_Potvin — Wed, 02 Feb 2022 11:12:38 GMT

[publishing on behalf of Global Support]

The question is also relevant when using the SAPApp/DB Endpoint with DB2LUW backend.

The DB2 for LUW documentation in the Qlik Replicates User's Guide lists the following permission related prerequisites:

The Replicate DB2 for LUW endpoint uses several APIs and tables that require these permissions, here are few examples:

The db2ReadLog as specified in the IBM documentation required these permissions.
The MON_GET_LOCKS which is needed for the transaction consistency mechanism, also requires either SYSADM or SYSMON authority, this is documented here.

In addition Replicate calls and uses these tables:

Catalog tables (e.g. SYSCAT.TABLES , SYSCAT.DATAPARTITIONS, SYSCAT.COLUMNS, SYSCAT.DATAPARTITIONEXPRESSION..).
Functions that require DATAACCESS authority (e.g. MON_FORMAT_LOCK_NAME, MON_GET_TRANSACTION_LOG, ENV_SYS_INFO..).
Tables used in the Task.

article Why does Qlik Replicate require SYSADM user privilege to access DB2 records and transaction logs? in Official Support Articles