Destroys a database, including all checkpoint files, transaction logs, and daemon catalog entries (though not the DSNs). If the CacheAdminWallet connection attribute is set to 1, ttDestroy also deletes the associated Oracle Wallet containing Oracle cache administrator credentials.

Required Privilege

This utility requires the instance administrator privilege.

Usage in TimesTen Scaleout and TimesTen Classic

This utility is supported in TimesTen Classic but not supported in TimesTen Scaleout.


ttDestroy {-h | -help | -?}
ttDestroy {-V | -version}
ttDestroy [[-wait] [-timeout secs]] [-force] {-connStr connection_string | 
 DSN | dspath}


ttDestroy has the options:

Option Description

-connStr connection_string

An ODBC connection string that specifies a database location, driver, and optionally other connection attribute settings.


Specifies an ODBC data source name of the database to be destroyed.


The fully qualified name of the database to be destroyed.

This is not the DSN associated with the connection but the fully qualified database path name associated with the database as specified in the DataStore= parameter of the database's ODBC definition.

For example, for a database consisting of files/home/payroll/2011.ds0, /home/payroll/2011.ds1, and several transaction log files /home/payroll/2011.logn,dspath is /home/payroll/2011.




Prints a usage message and exits.


Destroy even if files are from an incompatible version or a different instance of TimesTen.

-timeout seconds

Indicates the time in seconds that ttDestroy should wait. If no timeout value is supplied, TimesTen waits five seconds before retrying the destroy operation.

-V | -version

Prints the release number of ttDestroy and exits.


Causes ttDestroy to continually retry the destroy operation until it is successful, in those situations where the destroy fails due to some temporary condition, such as when the database is in use.


% ttDestroy /users/pat/TimesTen/Daily/F112697


  • Using ttDestroy is the only way to delete a database completely and safely. Do not remove database checkpoint or transaction log files manually.

  • ttDestroy does not perform cleanup of Oracle database objects from autorefresh or AWT cache groups. If there are autorefresh or AWT cache groups in the database, run the cachecleanup.sql script to clean up the cache objects in the Oracle database for that particular database, to generate Oracle SQL to perform cleanup after the database has been destroyed.