Skip to main content

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

100% helpful (1/1)
cancel
Showing results for 
Search instead for 
Did you mean: 
Melissa_Potvin
Community Manager
Community Manager

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

Last Update:

Feb 2, 2022 6:12:38 AM

Updated By:

Sonja_Bauernfeind

Created date:

Mar 26, 2020 10:33:46 AM

[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:

  • SYSADM or DBADM
  • DATAACCESS

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

  1. The db2ReadLog as specified in the IBM documentation required these permissions.
  2. 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.

 

Labels (1)
Version history
Last update:
‎2022-02-02 06:12 AM
Updated by: