ttDestroy
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.
Syntax
ttDestroy {-h | -help | -?} ttDestroy {-V | -version} ttDestroy [[-wait] [-timeout secs]] [-force] {-connStr connection_string | DSN | dspath}
Options
ttDestroy
has the options:
Option | Description |
---|---|
|
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 For example, for a database consisting of files |
|
Prints a usage message and exits. |
|
Destroy even if files are from an incompatible version or a different instance of TimesTen. |
|
Indicates the time in seconds that |
|
Prints the release number of |
|
Causes |
Examples
% ttDestroy /users/pat/TimesTen/Daily/F112697
Notes
-
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 thecachecleanup.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.