Download IMDB Cache User's Guide

Dropping a cache group
An active standby pair replication scheme cannot be dropped from a TimesTen
database if that database is still attached to a cache grid.
Execute the following statement as the cache manager user on the cacheactive,
cachestandby and rosubscriber databases to drop the active standby pair
replication scheme:
Command> DROP ACTIVE STANDBY PAIR;
Command> exit
Before you can drop a cache group, you must grant the DROP ANY TABLE privilege to
the cache manager user.
Execute the following statement as the instance administrator on the cachealone1,
cachealone2, cacheactive and cachestandby databases to grant the DROP ANY
TABLE privilege to the cache manager user. The following example shows the SQL
statement issued from the cachealone1 database:
% ttIsql cachealone1
Command> GRANT DROP ANY TABLE TO cacheuser;
Command> exit
Use a DROP CACHE GROUP statement to drop the cache groups from the standalone
TimesTen databases, and the active master and standby master databases.
Execute the following statement as the cache manager user on the cachealone1,
cachealone2, cacheactive and cachestandby databases to drop the
subscriber_accounts global cache group. The following example shows the SQL
statement issued from the cachealone1 database:
% ttIsql "DSN=cachealone1;UID=cacheuser;PWD=timesten;OraclePWD=oracle"
Command> DROP CACHE GROUP subscriber_accounts;
If you are dropping an AWT cache group, use the ttRepSubscriberWait built-in
procedure to make sure that all committed updates on its cache tables have been
propagated to the cached Oracle tables before dropping the cache group.
% ttIsql "DSN=cachealone1;UID=cacheuser;PWD=timesten;OraclePWD=oracle"
Command> call ttRepSubscriberWait('_AWTREPSCHEME','TTREP','_ORACLE','sys1',-1);
The replication scheme that was created for the AWT cache group to enable
committed updates on its cache tables to be asynchronously propagated to the cached
Oracle tables is automatically dropped when you drop the cache group.
If a grid member has a global cache group that contains cache instances, the cache
group cannot be dropped until all of its cache tables are empty or the member has
detached from its cache grid.
If the cache agent is stopped immediately after dropping a
cache group, or altering the cache group's automatic refresh state to
OFF, the Oracle objects used to manage the caching of Oracle data may
not have been dropped. When the cache agent is restarted, it drops the
Oracle objects that were created for the dropped or altered cache
group.
Note:
Cleaning up the Caching Environment
8-3