DB2 Replication Guide and Reference

Setting Up the Capture and Apply Programs

Setting up consists of configuring the source, target, and control servers. The following sections provide instructions for configuring each server.

Configuring the Capture Program for OS/2

Ensure that the user ID under which the Capture program is running has the required privileges:
- Execute privilege on the Capture packages
- DBADM or SYSADM privileges for the source, control, and target servers
Log on with the user ID that has sufficient privileges.
Connect to the source server database by entering:
```
DB2 CONNECT TO database
```
where database is the source server database.
Prepare the source server database (source database) for roll-forward recovery by issuing the update database configuration command and the backup database command. For example:
```
DB2 UPDATE DATABASE CONFIGURATION FOR database_alias USING LOGRETAIN ON
DB2 UPDATE DATABASE CONFIGURATION FOR database_alias USING USEREXIT ON
DB2 BACKUP DATABASE database_alias
```
Note: You might need to increase DBHEAP, APPLHEAPSZ, and LOGBUFSZ based on your installation requirements.
Change to the directory where the Capture program bind files are located, which is usually drive:\SQLLIB\BND.
Create and bind the Capture program package to the source server database by entering the following command:
```
DB2 BIND @CAPTURE.LST ISOLATION UR BLOCKING ALL
```
where UR specifies the list in uncommitted read format for greater performance.
These commands create a list of packages, the names of which can be found in the CAPTURE.LST file.

Configuring the Apply Program for OS/2

Ensure that the user ID under which Apply is running has the required privileges:
- Execute privilege for Apply packages
- DBADM or SYSADM privileges for the database(s)
Log on with the user ID that has sufficient privileges.
Change to the directory where the Apply program bind files are located, which is usually in drive:\SQLLIB\BND.
Connect to the source server database by entering:
```
DB2 CONNECT TO database
```
where database is the source server database.
Create and bind the Apply package to the source server database by entering both of the following commands:
```
DB2 BIND @APPLYCS.LST ISOLATION CS BLOCKING ALL
```
```
DB2 BIND @APPLYUR.LST ISOLATION UR BLOCKING ALL
```
Where:

CS
The list in cursor stability format.
UR
The list in uncommitted read format.

These commands create a list of packages, the names of which can be found in the APPLYCS.LST and APPLYUR.LST files.
Connect to the target server database by entering:
```
DB2 CONNECT TO database
```
where database is the target server database.

Create and bind the Apply package to the target server database by entering both of the following commands:

DB2 BIND @APPLYCS.LST ISOLATION CS BLOCKING ALL GRANT PUBLIC

DB2 BIND @APPLYUR.LST ISOLATION UR BLOCKING ALL GRANT PUBLIC

Note: Because the Apply control tables use static SQL calls, the Apply bind process searches for nearly all of the control tables at each server that it is bound to, regardless of whether these control tables have any use or meaning at each server.

Repeat the connect and bind steps for each server that the Apply program connects to. You must bind the Apply program to the source, target, and control servers.

[ Top of Page | Previous Page | Next Page | Table of Contents | Index ]

[ DB2 List of Books | Search the DB2 Books ]