Loading and Refreshing a Static Cache Group with Autorefresh
If the autorefresh state of a static cache group is PAUSED
, the
autorefresh state is changed to ON
after a LOAD CACHE
GROUP
or REFRESH CACHE GROUP
statement issued on the cache
group completes.
The following restrictions apply when manually loading or refreshing a static cache group with autorefresh:
-
A
LOAD CACHE GROUP
statement can only be issued if the cache tables are empty. -
The autorefresh state must be
PAUSED
before you can issue aLOAD CACHE GROUP
statement. -
The autorefresh state must be
PAUSED
before you can issue aREFRESH CACHE GROUP
statement. -
A
LOAD CACHE GROUP
statement cannot contain aWHERE
clause. -
A
LOAD CACHE GROUP
orREFRESH CACHE GROUP
statement cannot contain aWITH ID
clause. -
A
REFRESH CACHE GROUP
statement cannot contain aWHERE
clause. -
All tables and columns referenced in a
WHERE
clause when loading the cache group must be fully qualified. For example:owner
.
table_name
andowner
.
table_name
.
column_name
When an autorefresh operation occurs on a static cache group, all committed inserts, updates and deletes on the cached Oracle Database tables since the last autorefresh cycle are refreshed into the cache tables. New cache instances may be loaded into the cache tables. Cache instances that already exist in the cache tables are updated or deleted if the corresponding rows in the cached Oracle Database tables have been updated or deleted.