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 as well as information about providing end-user authentication at the source server.

Configuring the Capture program for UNIX platforms

Important: The Capture program is bound automatically during execution. Therefore, the following steps for binding the Capture program on UNIX are optional. If you want to specify options or check that all bind processes completed successfully, complete the following tasks:

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 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 backup database database_alias
```
or:
```
db2 update database configuration for database_alias using userexit on
db2 backup database database_alias
```
You might need to increase DBHEAP, APPLHEAPSZ, PCKCACHESZ, LOCKLIST, and LOGBUFSZ based on your installation requirements.
Change to the directory where the Capture program bind files are located, which is usually $HOME/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 are in the file CAPTURE.LST.

Configuring the Apply program for UNIX platforms

Important: The Apply package is bound automatically during execution. Therefore, the following steps for binding the Apply package on UNIX are optional. If you want to specify options or check that all bind processes completed successfully, complete the following tasks:

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 $HOME/sqllib/bnd.

Connect to the source server database by entering:

db2 connect to database

where database is the source server database.

Note:

If the source server database is catalogued as a remote database, you might need to specify a user ID and password on the db2 connect to command. For example:

db2 connect to database user userid using password

Create and bind the Apply program 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 specifies the list in cursor stability format, and ur specifies the list in uncommitted read format.
These commands create a list of packages, the names of which are in the files applycs.lst and applyur.lst.
Connect to the target server database by entering:
```
db2 connect to database
```
where database is the target server database.
Create and bind the Apply program package to the target server database by entering the following commands:
```
db2 bind @applycs.lst isolation cs blocking all grant public
```
```
db2 bind @applyur.lst isolation ur blocking all grant public
```
Because the Apply program control tables use static SQL calls for the control tables, the Apply bind process searches for the control tables at each server that the Apply program is bound to, regardless of whether these control tables are used at a server.
Repeat the connect and bind steps for each server that the Apply program connects to. You must bind the Apply program to all source, target, and control servers.

Other configuration considerations for UNIX-based components

Ensure that the user ID from which the Capture and Apply programs are running has write privilege on the directories where you invoke the programs. Write privilege is necessary because both the Capture and Apply programs create files in the invocation directory.

The Capture program creates the following files in addition to the spill files:

instnameSRCSRVR.ccp is a log file for the messages issued by the Capture program. These messages are also recorded in the trace table.
instnameSRCSRVR.tmp contains the process ID of this invocation of the Capture program (to prevent multiple Capture programs from being started in the same instance to the same source server).

The Apply program creates the following files:

APPLYQUAL.app is a log file for the messages issued by the Apply program. These messages are also recorded in the Apply trail table.
ASNAPPLYAPPLYQUAL.pid contains the process ID of this invocation of the Apply program (to prevent multiple Apply programs from being started with the same Apply qualifier).

For more information about configuration of UNIX-based components, see IBM DB2 Universal Database for UNIX Quick Beginnings.

Providing end-user authentication at the source server

In some cases you must provide a password file for end-user authentication to occur at the source server. The Apply program uses this file when connecting to the source server. Give read access only to the user ID that will run the Apply program. Following are environment-specific requirements:

If you installed Apply for HP-UX, Apply for Solaris, or Apply for UnixWare 7, you must use an AUTH=SERVER scheme and provide a password file.
If you installed Apply for AIX, you must provide a password file if you want to use an AUTHENTICATION=SERVER scheme at any server that the Apply program will connect to. If you use an AUTHENTICATION=CLIENT scheme for all servers, you do not need to provide a password file.

Creating a password file:

The password file must meet the following criteria:

Be named as shown:
```
applyqual.PWD
```
Where applyqual is a case-sensitive string that must match the case and value of the Apply qualifier (APPLY_QUAL) in the subscription set table exactly.
For example: DATADIR.PWD
This naming convention is the same as the log file name (.app) and the spill file name (.nnn), but with a file extension of .pwd.
Reside in the same directory from which you will start the Apply program.
Do not put blank lines or comment lines in this file. Only add the server-name, user ID, and password information. This information enables you to use different passwords or the same password at each server.
Have one or more records using the following format:
```
SERVER=server_name USER=userid PWD=password
```
Where:

server_name
The name of the source, target, or control server, exactly as it appears in the subscription set table.
userid
The user ID that you plan to use to administer that particular server. This value is case-sensitive.
password
The password that is associated with the userid. This value is case-sensitive.

If you do not create a password file:

The Apply program for UNIX must be able to issue an SQL CONNECT statement without specifying the user ID and password. If the Apply program needs to connect to an OS/390 database with SNA connectivity, these settings are necessary:

The DB2 for OS/390 database must be catalogued as AUTHENTICATION=CLIENT.
The login ID must belong to PRIMARY GROUP=SYSTEM.

When you copy from DB2 for OS/390 sources, these settings are necessary:

SECURITY=SAME for MVS CPI-C node.
You specify the following values when you define the LU name by using the VTAM APPL:
- VERIFY=NONE to indicate that any LU can request an LU-LU session
- SECACPT=ALREADYV to indicate user ID and password checking at the requester

For more information about authentication and security, refer to the IBM DB2 Universal Database Administration Guide.

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

[ DB2 List of Books | Search the DB2 Books ]