TimesTen: Replication Stops Working After ttRestore in 11.2.2
(Doc ID 1539886.1)
Last updated on MARCH 12, 2021
Applies to:Oracle TimesTen In-Memory Database - Version 22.214.171.124.0 and later
Information in this document applies to any platform.
Customer reports the following behavior in a master:master replication configuration:
ttbackup Node A
stop replication Node A (but do not drop)
stop replication Node B (but do not drop)
ttDestroy Node A; ttDestroy Node B
ttRestore Node A
start repagent on Node A
copy NodeA datastore to HostB using ttRepAdmin -duplicate
start repagent Node B
>>> now possible to replicate from NodeA to Node B, but it is not possible to replicate from NodeB back to NodeA
Customer further states that this behavior is seen in V11.2.2, but was not encountered in V7 nor in 11.2.1.X; in these earlier releases the procedure given above would have resulted in fully restored master:master replication.
This problem and the difference in behavior relative to earlier versions - is easilly reproduced using any master:master replication pair.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document