Technical data

Transient Oracle errors reported by TimesTen
5-4 Oracle TimesTen In-Memory Database Troubleshooting Procedures Guide
Example 5–1 Cache violation occurs when update is propagated to Oracle
If a constraint violation occurs when a cache group update is propagated to Oracle, the
message in the AWT error file is similar to the following:
Error occurred 14:48:55 on 03-22-2007
Datastore: c:\temp\cgDSN
Oracle Id: system1
Transmitting name: cgDSN
Error message:
TT5210: Oracle unique constraint violation error in OCIStmtExecute():
ORA-00001: unique constraint (GUSER.SYS_C00357240) violated rc = -1 -- file
"bdbTblH.c", lineno 1205, procedure "ttBDbStmtForce()"
TT5025: Commit failure in Oracle. Transaction must be rolled back in TimesTen.
-- file "bdbConnect.c", lineno 885, procedure "ttBDbXact()"
Operation that caused the error:
Insert into table TESTUSER.T1 <9,1000>
Failed transaction:
Insert into table TESTUSER.T1 <9, 1000>
End of failed transaction
Example 5–2 An object that TimesTen has placed on Oracle is dropped
If an object that TimesTen has placed on Oracle is dropped, the message in the AWT
error file is similar to the following:
May 04 18:12:36 HOST1 TimesTen Replication 7.0[2136]:
[Err ] DEFAULT:meta.c(639):
TT16062: Failed to compile command:
select p.commit_timestamp, p.commit_seqnum, p.protocol from owner1.TT_03_REPPEERS
p where p.replication_name = :rname and p.replication_owner = :rowner and
p.tt_store_id = :oid and p.subscriber_id = :sid
May 04 18:12:36 HOST1 TimesTen Replication 7.0[2136]:
[Err ] DEFAULT:meta.c(639):
TT5221: TT5221: Oracle syntax error in OCIStmtExecute():
ORA-00942: table or view does not exist rc = -1 -- file "bdbStmt.c", lineno 1041,
procedure "getOraOutTypesNLengths()"
In this example, the TT_03_REPPEERS table does not exist. To recover from this error,
perform the following tasks:
1. Stop the replication agent.
2. Drop and re-create the cache group.
3. Restart the replication agent.
Transient Oracle errors reported by TimesTen
The support log for data stores with AWT cache groups may contain Oracle errors if
the replication agent encounters a problem on the Oracle database. If the replication
agent encounters one of these errors, AWT rolls back the transaction and retries it. If
the support log becomes full, the oldest messages are deleted and replaced by new
messages.
The Oracle errors in the support log are considered transient because AWT retries the
transaction.