This content has been marked as final. Show 1 reply
The 'replication' to Oracle (actually AWT cache group) works by capturing the changes from the TimesTen transaction logs. Once a change reaches the TT transaction logs on disk it is safe and once the TT machine, TimesTen and the replication agent are back up replication will resume from where it left off.
More generally, data stored in TimesTen is persisted and protected using the checkpointing and transaction logging mechanism within TimesTen. By default, TimesTen uses asynchronous write to the logs (DurableCommits=0). This gives very high performance but in the event of a failure you will lose the last few committed transactions. If this is not acceptabel you can tell TimesTen to use synchronous commit to disk (DurableCommits=1). This is much (and I mean hugely) slower but ensures that all committed transactions are safe (unless the disk itself fails). TimesTen also provides TimesTen to TimesTen replication (both asynchronous and synchronous) as an additional / alternative method of data protection.