Risk of data loss in with unmapped class and split replication
When replicating an object whose class is not yet mapped, and the
object ends up being split into two or more traversal buffers,
only the data in the first traversal buffer is used, resulting in
lost data in the replicated object.
This can only happen if the object split across buffers is the
first replication of an instance of a given class that is replicated
in a session. The first replication maps the class (whether or not
it is split), so any subsequent replications of instances of that
class are immune from the problem.
Workaround:
Add a class connector for the affected class. If the class is
mapped at login, subsequent replication will not need class mapping,
avoiding this problem.
Last updated: 9/10/07