Technical data

Replication unresponsive, appears hung
6-10 Oracle TimesTen In-Memory Database Troubleshooting Procedures Guide
Check consistency between replicated tables
Replicated tables on both master and subscriber data stores must be exactly the same.
Example 6–12 Check consistency between replicated tables
This output from the user error log shows a mismatch on the number of columns for
the subscriber table TTUSER.MYDSN.
11:37:58.00 Info: REP: 9430: REP1:transmitter.c(4936): TT16136: Sending
definition for table TTUSER.MYDSN (1 columns)
11:37:58.00 Info: REP: 9412: REP2:receiver.c(5928): TT16193: Adding definition
for table: TTUSER.MYDSN
11:37:58.00 Info: REP: 9412: REP2:meta.c(5580):TTUSER.MYDSN ptn 0: srcoff 0,
destoff 0, length 8
11:37:58.00 Info: REP: 9412: REP2:meta.c(5580):TTUSER.MYDSN ptn 1: srcoff 8,
destoff 12, length 12
11:37:58.00 Err : REP: 9412: REP2:receiver.c(6203): TT16198: Table definition
mismatch on number of columns for table TTUSER.MYDSN. Local definition: 2;
transmitting peer: 1
11:37:58.00 Err : REP: 9412: REP2:receiver.c(6380): TT16204: Table TTUSER.MYDSN
marked invalid. Will not apply transactions received for it until a valid
definition is received
11:37:58.00 Err : REP: 9412: REP2:receiver.c(7200): TT16078: Table definition
for ID 637068 is invalid (Original failure 11:37:58
REP2:receiver.c(6203): TT16198: Table definition mismatch on number of columns
for table TTUSER.MYDSN. Local definition: 2; transmitting peer: 1)
11:37:58.00 Err : REP: 9412: REP2:receiver.c(5002): TT16187: Transaction
1173958671/2; Error: transient 0, permanent 1
Replication unresponsive, appears hung
Table summary is in the first heading cell.
Check replication state
Use the ttReplicationStatus procedure to check state of the subscriber data store
with respect to its master. If the subscriber is in the Failed state, see "Managing data
store failover and recovery" in the Oracle TimesTen In-Memory Database TimesTen to
TimesTen Replication Guide for information on how to deal with failed data stores.
Example 6–13 Check replication state
Use ttReplicationStatus to obtain the status of the subscriberds data store
from its master data store, masterDSN, enter:
> ttIsql masterDSN
TTREP.REPTABLES TTREP.REPTABLES
TTREP.TTSTORES TTREP.TTSTORES
Possible cause See...
Failed subscriber "Check replication state" on page 6-10
Return-receipt timeout period too
long
"Check return receipt timeout setting" on
page 6-11
Output for SYSTEM1 Output for SYSTEM2