For the most up-to-date version of the data replication scenario (Chapter 3) and other information, go to the DB2 DataPropagator Web page (http://www.software.ibm.com/data/dpropr), click the "Library" link, then go to the section titled "Hints, Tips, and Documentation Corrections."
Replication is not supported for DB2 Extenders for Text, Audio, Video and Image, or other extenders where additional control files associated with the extender's LOB column data are maintained outside of the database.
DB2 UDB EEE is supported for replication with the following restrictions:
In the case of NonCondensed, NonComplete CCD, a gap will be detected if you bring down the Capture program and cold start it again. It's not recommended that you bring down the Capture program and cold start again with this kind of target type. To recover, set SYNCHPOINT, SYNCHTIME, and LASTSUCCESS to NULL in the subscription set table. Then cold start the Capture program, and start the Apply program. Data integrity could be lost, in which case you would need to manually insert the missing rows into the target table.
A particular form of key update, using the syntax SET KEYCOL = KEYCOL + n, cannot be replicated correctly with respect to condensed copies. In such a case, a different column must be used as the subscription key. If no suitable alternate key exists in the source table, then, before defining the table as a replication source, the table needs to be altered to include a new column. Existing source table rows must have unique values assigned to the new column. Thereafter, unique key values must be assigned to the new column whenever rows are inserted into the source table. This new column must be included in the subscription of any condensed copy (user copy, point in time, condensed CCD, replica), all of which require a unique key.
It is recommended that you enable transaction logging for Informix databases involved in replication.
Replication is not supported for DB2 Extenders for Text, Audio, Video, Image, or other extenders where additional control files associated with the extender's LOB column data are maintained outside of the database.
The ERRWAIT(n) Apply program invocation parameter enables you to control the number of seconds that the Apply program waits before attempting to retry after an error condition occurs. The default wait period is 5 minutes (300 seconds). UNIX example:
asnapply aplqual1 errwait(600)
In this example, aplqual1 is the Apply qualifier, and 600 specifies that the Apply program wait 600 seconds (10 minutes) before retrying after it encounters an error condition.
Notes:
Before you begin:
To connect to an AS/400 server from DB2 for Windows NT:
Relational Remote
Option Database Location
MYDBOS2 9.112.14.67
RCHASDPD RCHASDPD
DB2400E *LOCAL
RCHASLJN RCHASLJN
db2 catalog tcpip node server_name remote server_name server 446
system server_name ostype OS400
db2 catalog dcs database rdb_name AS rdb_name
db2 catalog database rdb_name AS rdb_name at node server_name
authentication dcs
where server_name is the name of the AS/400 system, and rdb_name is the name of the AS/400 relational database that you found in step 1.
CHGUSRPRF USRPRF(SINN) CCSID(37)
where SINN is the user profile.
STRTCPSVR SERVER(*DDM)
DPROPR/400 allows 5769DP2 users to run Version 1 registration/subscription pairs concurrently with Version 5 replication source/target pairs. However, MAX_SYNCH_MINUTES support is not available in such an environment. Do not specify MAX_SYNCH_MINUTES in a subscription set if Version 1 and Version 5 pairs will coexist.
You must use the Create SQL Package (CRTSQLPKG) command to create the packages necessary to use Apply for AS/400 with remote systems on platforms other than AS/400. For example:
CRTSQLPKG PGM(QDPR/QZSNAPV2) RDB(remote_RDB_name) MODULE(QZSNICHG) CRTSQLPKG PGM(QDPR/QZSNAPV2) RDB(remote_RDB_name) MODULE(QZSNAPV2)
See "DB2 for AS/400 SQL Programming V4R3 (SC41-5611-02)" for more information about the CRTSQLPKG command.
AIX example:
export LIBPATH=db2instance_home_directory/sqllib/lib:/usr/lib:/lib export LANG=en_US
HP-UX example:
export SHLIB_PATH=db2instance_home_directory/sqllib/lib:/usr/lib:/lib export LANG=en_US
Solaris example:
export LD_LIBRARY_PATH=instanceowner/sqllib/lib:/usr/lib:/lib export LANG=en_US export NLS_PATH=~/usr/lib/locale/%L/%N:/instanceowner/sqllib/msg/en_US/%N
IBM has changed the default installation directory for DJRA: it is now SQLLIB\DJRA\djra.exe.
For CCD tables:
Apply program message ASN1069E:
The Apply program has detected a referential integrity violation and compensated the rejected transactions. See the unit-of-work table for details. The error code is %1. Explanation: A referential integrity violation was detected when replicating data from the replica to the user table. User Response: See the unit-of-work table for details.
Apply program message ASN1071:
The Apply program could not reposition the work file. The error code is %1. Explanation: The Apply program has detected an error while reading the temporary work file. User Response: Contact your IBM Service representative.
For late-breaking information that could not be included in the DB2 books:
Printing the PostScript books (on UNIX-based platforms):
Step 3: Decompress and print the manual you require using the following command for Linux: zcat <filename> | lpr -P PSPrinter_queue