You cannot use REFRESH on a GLOBAL cache group. Create a local cache group if you want to test this functionality. ie drop the GLOBAL attribute when you create it.
For the LOAD does that row already exists in TT? If so then nothing will be loaded.
LOAD CACHE GROUP only loads committed inserts on the cached Oracle tables into the TimesTen cache tables. New cache instances are loaded into the cache tables, but cache instances that already exist in the cache tables are not updated or deleted even if the corresponding rows in the cached Oracle tables have been updated or deleted. A load operation is primarily used to initially populate a cache group.
REFRESH CACHE GROUP replaces cache instances in the TimesTen cache tables with the most current data from the cached Oracle tables including cache instances that are already exist in the cache tables. A refresh operation is primarily used to update the contents of a cache group with committed updates on the cached Oracle tables after the cache group has been initially populated.
Load will load cache group with newly inserted rows, it will not delete/ update existing rows. refresh will refresh cache group with already existing rows be it update/ delete, but it will not insert new row(s).
One more thing one alternative for my problem (not able to see Oracle changes in TT) :)
UNLOAD cache group, then again load this time it will be having new data but,
my concern is: is this the feasible solution for my problem ????
that way you are connecting to both TimesTen and oraclw with the correct credentials.
Note that AUTOREFRESH operations from oracle to TT are executed as the 'cacheadm' user in both Oracle and TT. Propagation of updates via SWT or PROPAGATE are executed in Oracle as the same user as the one you use to connect to TimesTen (UID/PWD) but when we connect to Oracle to do these operations we connect as (UID/OraclePWD) so tjhat combination must be (a) correct for Oracle and (b) the user on Oracle must not be locked etc.
There are many queries asked in this thread like timesten examples, how to use client with timesten, timesten and Oracle version required, some issues with read only and AWT configuration solution for that, as well as alternative using USERMANAGED etc.
Hope this will provide some help to newbies like me,
What is the autocommit mode? If it is zero (disabled) then you need to commit in TimesTen; changes are only ptopagated to Oracle at commit time.
If you have autocommit enabled then the change must have made it to Oracle since if it did not you would have received an error on your ttIsql session...
With PROPAGATE, changes made in a transaction are not propagated to Oracle until you commit. Commits are synchronous between TmesTen and Oracle and any oracle errors encountered when applying the changes to oracle or when comitting are immediately reported by TimesTen.