Problems with Parallel Replication

If you have configured parallel replication, then you have additional TimesTen replication threads running on your system. Be sure that you have enough CPU cores to accommodate the increased number of replication threads.

If you have configured user-defined track based parallel replication (ReplicationApplyOrdering = 1 and ReplicationParallelism > = 2), and you are seeing permanent errors on the receiver side that include constraint violations or row lookup failures, then possible causes include:

• Application defined dependencies are incorrect

• Operations for the same keys or keys of tables in a constraint relationship are written to different tracks.

Check the value of the general connection attribute, ReplicationTrack. All transactions executed by the connection are assigned to the track as defined in the ReplicationTrack attribute setting. Make sure the workload for each track is suitable. Use the ALTER SESSION statement to change the replication track. For more information, see ALTER SESSION in the Oracle TimesTen In-Memory Database SQL Reference. For more information on configuring parallel replication, see Configuring Parallel Replication in the Oracle TimesTen In-Memory Database Replication Guide.