DB2 Help

Authorities and privileges for replication sources tasks

Task Authorities and privileges
Before you view or change a replication source definition You must:

Have the required authority.
Define the source table as a replication source, either using the quick or custom method.

Before you begin defining a replication source, Complete the following tasks:

Check and modify, if necessary, the Replication page of the Tools Settings notebook for the default settings.

Both before and after-image columns are captured.
The change data table space is dropped when the table space is empty.

Ensure that the following default values are appropriate for your application:

All source columns are available for data capture.
Changed data for partitioned key columns is captured as updates.
The source table is available for replication read-only target tables.
If the table will be used for update anywhere replication, the conflict detection level is set to none.

If you need to change these defaults, you must define a custom replication source. If these defaults are appropriate, you can define a replication source using default values.
Ensure that you have valid DB2 authorization.

Before you can define a custom replication source You must:

Check "defaults" for Replication in the Tools Settings notebook to verify that they are correct for your application or site.
Ensure you have the necessary DB2 authorization:

For DB2 for MVS, you need the following:

The authority to grant update, select, insert, and delete privileges to other users for the control tables.
If the primary authorization ID of the administrator is ASN, this privilege is implied in the ownership of the above tables.
If the primary authorization ID is not ASN, the administrator must have either:

SYSADM level authority, held privately or publicly
DBADM authority.

The authority to create tables either in the DB2 forms default database, DSNDB04, or in a DB2 database that you can optionally specify. To do so, you must have at least one of the following authorities:

SYSADM or SYSCTRL authority, held privately or publicly
DBADM authority for the DB2 database specified.
DBADM authority for the DSNDB04 database
CREATETAB and CREATETS privileges on the DSNDB04 database
CREATETAB and CREATETS privileges on the DB2 database specified by the administrator in the DPCNR.SQL file.

The authority to access selected system catalog tables. To do so, you must have at least one of the following authorities:

SYSADM or SYSCTRL authority, held privately or publicly
DBADM authority for the DSNDB06 database
SELECT privileges for the following catalog tables:

SYSIBM.SYSCOLUMNS
SYSIBM.SYSDATABASE
SYSIBM.SYSINDEXES
SYSIBM.SYSINDEXPART
SYSIBM.SYSKEYS
SYSIBM.SYSTABLES
SYSIBM.SYSTABLESPACE

The authority to run Capture, which includes:

EXECUTE privilege on the Capture MVS program plan, ASNLPLAN
TRACE privilege
MONITOR1 and MONITOR2 privileges

For DB2 for common servers, you must have DBADM or SYSADM authority that meets all requirements for defining a replication source.

For DB2 for MVS,

You need the following authority:

The authority to grant update, select, insert, and delete privileges to other users for the control tables.
If your primary authorization ID is ASN, this privilege is implied in the ownership of the above tables.
If your primary authorization ID is not ASN, you must have, either:

SYSADM level authority, held privately or publicly
DBADM authority

The authority to create tables either in the DB2 forms default database, DSNDB04, or in a DB2 database that you can optionally specify in the DPCNTL.SQL control table file. For this authority, you must have at least one of the following privileges:

SYSADM or SYSCTRL authority, held privately or publicly
DBADM authority for the DB2 database specified
DBADM authority for the DSNDB04 database
CREATETAB and CREATETS privileges on the DSNDB04 database
CREATETAB and CREATETS privileges on the DB2 database specified by the administrator in the DPCNR.SQL file.

The authority to access selected system catalog tables. For this authority, you must have at least one of the following privileges:

SYSADM or SYSCTRL authority, held privately or publicly
DBADM authority for the DSNDB06 database
SELECT privileges for the following catalog tables:

SYSIBM.SYSCOLUMNS
SYSIBM.SYSDATABASE
SYSIBM.SYSINDEXES
SYSIBM.SYSINDEXPART
SYSIBM.SYSKEYS
SYSIBM.SYSTABLES
SYSIBM.SYSTABLESPACE

The authority to run Capture, which includes:

EXECUTE privilege on the Capture MVS program plan, ASNLPLAN
TRACE privilege
MONITOR1 and MONITOR2 privileges

For DB2 Universal Database

You need the following authority:

You must have DBADM or SYSADM authority which meets all requirements for defining a replication source.

Before you remove a replication source You must:

Suspend Capture.
Determine which subscriptions are based on this replication source and make sure that they are no longer required.

Before you define a join for one or more replication sources You must:

Define each table included in the join as a replication source.
Have the necessary authority to define joins for the replication source.
Understand which view scenarios are supported.

Before you run an SQL file: You must:

Save an SQL file while performing a replication task, such as, defining a replication source.
Optionally edit the SQL file for your application. See the Replication Guide and Reference for details.

Before you run the SQL file: You must:

Save an SQL file while performing a replication task, such as, defining a replication source.
Optionally edit the SQL file for your application. See the Replication Guide and Reference for details.

Task	Authorities and privileges
Before you view or change a replication source definition	You must: Have the required authority. Define the source table as a replication source, either using the quick or custom method.
Before you begin defining a replication source,	Complete the following tasks: Check and modify, if necessary, the Replication page of the Tools Settings notebook for the default settings. Both before and after-image columns are captured. The change data table space is dropped when the table space is empty. Ensure that the following default values are appropriate for your application: All source columns are available for data capture. Changed data for partitioned key columns is captured as updates. The source table is available for replication read-only target tables. If the table will be used for update anywhere replication, the conflict detection level is set to none. If you need to change these defaults, you must define a custom replication source. If these defaults are appropriate, you can define a replication source using default values. Ensure that you have valid DB2 authorization.
Before you can define a custom replication source	You must: Check "defaults" for Replication in the Tools Settings notebook to verify that they are correct for your application or site. Ensure you have the necessary DB2 authorization: For DB2 for MVS, you need the following: The authority to grant update, select, insert, and delete privileges to other users for the control tables. If the primary authorization ID of the administrator is ASN, this privilege is implied in the ownership of the above tables. If the primary authorization ID is not ASN, the administrator must have either: SYSADM level authority, held privately or publicly DBADM authority. The authority to create tables either in the DB2 forms default database, DSNDB04, or in a DB2 database that you can optionally specify. To do so, you must have at least one of the following authorities: SYSADM or SYSCTRL authority, held privately or publicly DBADM authority for the DB2 database specified. DBADM authority for the DSNDB04 database CREATETAB and CREATETS privileges on the DSNDB04 database CREATETAB and CREATETS privileges on the DB2 database specified by the administrator in the DPCNR.SQL file. The authority to access selected system catalog tables. To do so, you must have at least one of the following authorities: SYSADM or SYSCTRL authority, held privately or publicly DBADM authority for the DSNDB06 database SELECT privileges for the following catalog tables: SYSIBM.SYSCOLUMNS SYSIBM.SYSDATABASE SYSIBM.SYSINDEXES SYSIBM.SYSINDEXPART SYSIBM.SYSKEYS SYSIBM.SYSTABLES SYSIBM.SYSTABLESPACE The authority to run Capture, which includes: EXECUTE privilege on the Capture MVS program plan, ASNLPLAN TRACE privilege MONITOR1 and MONITOR2 privileges For DB2 for common servers, you must have DBADM or SYSADM authority that meets all requirements for defining a replication source.
For DB2 for MVS,	You need the following authority: The authority to grant update, select, insert, and delete privileges to other users for the control tables. If your primary authorization ID is ASN, this privilege is implied in the ownership of the above tables. If your primary authorization ID is not ASN, you must have, either: SYSADM level authority, held privately or publicly DBADM authority The authority to create tables either in the DB2 forms default database, DSNDB04, or in a DB2 database that you can optionally specify in the DPCNTL.SQL control table file. For this authority, you must have at least one of the following privileges: SYSADM or SYSCTRL authority, held privately or publicly DBADM authority for the DB2 database specified DBADM authority for the DSNDB04 database CREATETAB and CREATETS privileges on the DSNDB04 database CREATETAB and CREATETS privileges on the DB2 database specified by the administrator in the DPCNR.SQL file. The authority to access selected system catalog tables. For this authority, you must have at least one of the following privileges: SYSADM or SYSCTRL authority, held privately or publicly DBADM authority for the DSNDB06 database SELECT privileges for the following catalog tables: SYSIBM.SYSCOLUMNS SYSIBM.SYSDATABASE SYSIBM.SYSINDEXES SYSIBM.SYSINDEXPART SYSIBM.SYSKEYS SYSIBM.SYSTABLES SYSIBM.SYSTABLESPACE The authority to run Capture, which includes: EXECUTE privilege on the Capture MVS program plan, ASNLPLAN TRACE privilege MONITOR1 and MONITOR2 privileges
For DB2 Universal Database	You need the following authority: You must have DBADM or SYSADM authority which meets all requirements for defining a replication source.
Before you remove a replication source	You must: Suspend Capture. Determine which subscriptions are based on this replication source and make sure that they are no longer required.
Before you define a join for one or more replication sources	You must: Define each table included in the join as a replication source. Have the necessary authority to define joins for the replication source. Understand which view scenarios are supported.
Before you run an SQL file:	You must: Save an SQL file while performing a replication task, such as, defining a replication source. Optionally edit the SQL file for your application. See the Replication Guide and Reference for details.
Before you run the SQL file:	You must: Save an SQL file while performing a replication task, such as, defining a replication source. Optionally edit the SQL file for your application. See the Replication Guide and Reference for details.