Technical data

Poor replication or XLA performance
Troubleshooting Replication 6-11
Command> CALL ttReplicationStatus ('subscriberds');
< SUBSCRIBERDS, MYHOST, 0, failed, 1, 10, REPSCHEME, REPL >
1 row found.
Check return receipt timeout setting
Use the ttRepSyncGet procedure to check the return receipt timeout setting. A value
of -1 indicates the application is to wait until it receives an acknowledgement from the
subscriber. Network latency or other issues might delay receipt of the subscriber
acknowledgment. You either address these issues or use the ttRepSyncGet
procedure to reset the return receipt timeout period.
See "Checking the status of return service transactions" in the Oracle TimesTen
In-Memory Database TimesTen to TimesTen Replication Guide for more information.
Poor replication or XLA performance
Most of this section addresses issues that may impact replication performance. Some
issues, such as log buffer too small and reading from the transaction log files on disk,
can impact the performance of both replication and XLA applications.
Check network bandwidth
Replication agents typically communicate over some type of network connection. If
replicating over a network slower than 10 MB per second (such as common with a 100
Base-T Ethernet typical in a LAN), you must be careful to match the transaction load
to the available bandwidth of the network. see "Network bandwidth requirements" in
the Oracle TimesTen In-Memory Database TimesTen to TimesTen Replication Guide for
details.
Check use of return receipt blocking
Unless you need receipt confirmation for all your transactions, disable RETURN
RECEIPT BLOCKING. If you require receipt confirmation for some transactions, then
set RETURN RECEIPT BY REQUEST and call the ttRepSyncSet procedure to enable
the return receipt service for specific transactions. See "RETURN RECEIPT BY
REQUEST" in the Oracle TimesTen In-Memory Database TimesTen to TimesTen Replication
Guide for details.
Possible cause See...
Slow network "Check network bandwidth" on page 6-11
Using RETURN RECEIPT "Check use of return receipt blocking" on page 11
Inefficient replication scheme "Check replication configuration" on page 12
Log buffer too small "Check size of log buffer" on page 6-12
Frequent or inefficient disk
writes
"Check durability settings" on page 6-12
Reading from transaction log
files on disk rather than the log
buffer
"Check for reads from transaction log files" on page 6-12
High rate of conflicts "Conflict reporting slows down replication" on page 6-16