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.

  • 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 the Oracle database 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.