Most problems that cause replication to fail are related to changes in the environment, either intentional changes (such as changing the schema of a table) or unintentional changes (such as failures of software, hardware, or network infrastructure).
Some problems with datatypes, constraints, and column properties might cause replication to fail, or in some cases, prevent replication from starting:
Under some conditions, approximate numeric datatypes float, double precision, and real can cause ASE Replicator errors, and the timestamp datatype cannot be replicated at all.
Replicating columns with the IDENTITY property can cause ASE Replicator errors.
Datatype, primary key constraint, and null-handling inconsistencies between primary and replicate tables can cause ASE Replicator errors.
Another possible cause of replication failure is a Java environment problem, such as inadequate memory allocated for the Java virtual machine.
The following sections describe the most common causes of and solutions for replication failure problems:
| Copyright © 2005. Sybase Inc. All rights reserved. |
|
|
