Stopping the Cache Agent

You can manually stop the cache agent.

Stop the cache agent by performing the following:

In TimesTen Scaleout, use ttGridAdmin dbCacheStop command to stop the cache agent on all instances within the grid. See Stopping the Cache Agents for TimesTen Scaleout in the Oracle TimesTen In-Memory Database Scaleout User's Guide.
In TimesTen Classic, call the ttCacheStop built-in procedure as the TimesTen cache administration user:
```
Command> call ttCacheStop;
```
You can also stop the cache agent from a command line by running a ttAdmin -cacheStop utility command as a TimesTen external user with the CACHE_MANAGER privilege:
```
% ttAdmin -cacheStop cache1
```
Do not stop the cache agent immediately after you have dropped or altered a cache group with autorefresh. Instead, wait for at least two minutes to allow the cache agent to clean up Oracle Database objects such as change log tables and triggers that were created and used to manage the cache group.

The ttCacheStop built-in procedure has an optional parameter and the ttAdmin -cacheStop utility command has an option -stopTimeout that specifies how long the TimesTen main daemon process waits for the cache agent to stop. If the cache agent does not stop within the specified timeout period, the TimesTen daemon stops the cache agent. The default cache agent stop timeout is 100 seconds. A value of 0 specifies to wait indefinitely.

Note:

The TimesTen X/Open XA and Java Transaction API (JTA) implementations do not work with cache. The start of any XA or JTA transaction fails if the cache agent is running.