HOWTO : Resolve TimesTen Errors TT0907 & TT16187 With Replication Agent Core Dump
(Doc ID 782680.1)
Last updated on MARCH 12, 2021
Applies to:Oracle TimesTen In-Memory Database - Version 18.104.22.168.0 to 22.214.171.124.0 [Release 7.0]
Information in this document applies to any platform.
***Checked for relevance on 31-Jan-2011***
***Checked for relevance on 26-Nov-2013***
-- Problem Statement:
Data divergence between two replicated data stores, meant that when the replication agent tried to apply replicated transactions against the subscriber, it encountered foreign key violations.
This caused them to encounter <bug:6415652> where the replication agent can core dump when handling a FK violation.
The agent would core dump, then on restart, it would core dump again. (as it tried to handle the same transaction). This cycle continued until the subscriber datastore was re-created (duplicated) from the master.
These two issues a) data divergence and b) replication agent core dumping can be seen in the message log as follows:
04:42:47.10 Err : REP: 27049: XXX:receiver.c(9371): TT16084: Table: TT.TAB1. Failed to insert row for 'insert'
04:42:47.10 Err : REP: 27049: XXX:receiver.c(9371): TT907: TT0907: Unique constraint(T_CONST_1) violated at Rowid <0x00000000024ae478> -- file "ttree.c", lineno 4134, procedure "sbTtInsert"
04:42:47.10 Err : REP: 27049: XXX:receiver.c(5016): TT16187: Transaction 1215848204/556399; Error: transient 0, permanent 1
b) Replication agent exits:
05:05:36.63 Info: : 383: New process (#367) has connected
05:05:36.63 Info: : 383: Repagent id 367 started for /opt/jnetx/TT/XXX
05:05:36.63 Info: : 383: Repagent restarted.
Stack traces taken from the core dumps written by the replication thread have appeared as follows:
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