- Cache Guide
- Cleaning Up the Caching Environment
- Destroying the TimesTen Databases
Destroying the TimesTen Databases
TimesTen provides commands to destroy a TimesTen database.
- Ensure you backup all your data, since it will be discarded in the destruction process.
- Make sure that you drop all cache groups before you attempt to destroy a
                    database. If you cannot drop the cache groups, then use the
                        -forceoption on the destroy operation in the next step. See Dropping a Cache Group.
- Perform the destroy operation:- 
                              In TimesTen Scaleout, if the TimesTen database is no longer needed, you can use the ttGridAdmin dbDestroycommand to destroy the databases. See Destroying a Database in the Oracle TimesTen In-Memory Database Scaleout User's Guide.
- 
                              In TimesTen Classic, if the TimesTen databases are no longer needed, you can use the ttDestroyutility to destroy the databases.Note: In TimesTen Classic, if the RAM policy designates that the database stays in memory, then this may prevent you from destroying the database. For example, if the RAM policy is set to always, then you must change the RAM policy tomanualand run thettAdmin -ramunloadcommand to unload the database before destroying the database. See Specifying a RAM Policy section in the Oracle TimesTen In-Memory Database Operations Guide.The following example shows the ttDestroyutility connecting to and then destroying thecache1database:% ttDestroy cache1 
 
- 
                              
- If you used the -forceoption on the destroy operation, run the following script to cleanup the metadata and Oracle database objects.- 
                              For TimesTen Scaleout, run the scaleoutCacheCleanup.sqlscript.
- 
                              For TimesTen Classic, run the cacheCleanup.sqlscript.
 
-