Technical data

Changes not visible after updating object in cache group
4-10 Oracle TimesTen In-Memory Database Troubleshooting Procedures Guide
and when it was executed are each written to a TimesTen table in the cache
administrator user schema on Oracle.
For more information on how to create the DDL tracking objects and how to enable
DDL tracking for the base table within Oracle, see "Monitoring DDL operations on
Oracle tables" in the Oracle In-Memory Database Cache User's Guide. For details on the
built-in procedures used for initializing and enabling DDL tracking, see the Oracle
TimesTen In-Memory Database Reference.
Changes not visible after updating object in cache group
If you modify an object in a cache group and then the changes do not appear on a
subsequent SQL statement, then one of the following may have occurred:
■ The object was dropped from the Oracle database or was somehow damaged.
■ The Oracle database was restored or recovered to a time before the object was
created.
■ The Oracle database was down.
■ The user modified the OracleNetServiceName DSN or connection attribute
after creating the cache group, which points to an Oracle database other than the
one that the cache group was created upon.
For example, if the user creates an AWT cache group. Then, the user added rows to a
table. When the user performs a SELECT * FROM the table, the rows did not appear.
The ttmesg.log error file does not display an error that Oracle is not available.
Instead, it displays the following messages:
12:09:02.10 Err : REP: 29934: CACHE1:meta.c(904): TT5221: TT5221: Oracle syntax
error in OCIStmtExecute(): ORA-00942: table or view does not exist rc = -1 --
file "bdbStmt.c", lineno 1535, procedure "getOraOutTypesNLengths()"
12:09:02.27 Err : REP: 29934: CACHE1:receiver.c(1978): TT5250: Awt Initialization
Failure. Could not compile meta data sql.
12:09:02.27 Warn: REP: 29934: CACHE1:transmitter.c(6505): TT16060: Failed to read
data from the network. select() timed out
To recover, perform the following:
1. Stop all updates to the cache group.
2. If you are using an AWT cache group, then flush the cache group.
3. Recreate the cache group with the drop and create.
Loading or refreshing fails
If the LOAD CACHE GROUP or REFRESH CACHE GROUP statement fails when you
specify COMMIT EVERY n ROWS and n is greater than 0, the contents of the target
cache group could be in an inconsistent state. Some cache instances may be partially
loaded.
Unload the cache group and then load it again. In some situations, it may be easier to
drop and re-create the cache group.
Monitoring autorefresh cache groups
This section includes the following topics:
■ Using the ttCacheAutorefreshStatsGet procedure