Restrictions
The following restrictions apply to both Windows and UNIX platforms:
- Do not create a DataPropagator subscription on tables that have
referential-integrity constraints or triggers. Otherwise, replication
would fail and would be unrecoverable.
- For z/OS and iSeries source systems, you must issue a bind Capture job to
start the Capture program on the source system. For more information on
how to bind the Capture program, see the Replication topics in the DB2
Universal Database Information Center.
- The mirror database must be located on the same server as the replication
engine. The DataPropagator Capture program is not able to capture any
remote databases.
- By default, DataPropagator will create the mirror tables in their own,
non-system managed, tablespaces. If you want the DB2 Everyplace control
tables associated with the mirror tables to be created in the same
tablespaces, you will need to either override the tablespace creation to
specify that the tablespace is system-managed, or increase the tablespace
container size to accomodate these control tables (a general recommendation is
to increase the container to 5 times the Data Propagator-generated
size). If you do not specify a tablespace in the XML to generate the
DB2 Everyplace Subscription, the default tablespace USERSPACE1 will be used
for the DB2 Everyplace control tables.
- If "Replicate FALSE" is not specified as an attribute in the
AddDProprSubscription tag, then the mirror database must be local to the
machine on which the XML Scripting Tool is executing, and the source capture
process must be running.
Zadania pokrewne