TMF Planning and Configuration Guide (H06.05+)

Concepts and Capabilities
HP NonStop TMF Planning and Configuration Guide—540136-002
1-8
Deleting the TMF Configuration and Starting Over
•
Enables audited updates on all configured data volumes that were not previously
disabled by a DISABLE DATAVOLS command
•
Permits new transactions to begin
If TMF ever stops abnormally (because of a system failure, for example), the
subsequent restart sequence will automatically include volume recovery for any data
volumes that had database tables or files open at the time of the failure. This is done
as TMF attempts to start each data volume.
Files that cannot be recovered successfully by the volume recovery process are not
available for audited access by your OLTP applications. Such files, if there are any,
are listed in the EMS log. To make them available, you might have to invoke the file
recovery process. For information about performing file recovery, see the TMF
Operations and Recovery Guide.
Deleting the TMF Configuration and Starting
Over
This subsection discusses how to delete an existing TMF configuration for the purpose
of creating a completely new TMF environment.
When you delete the TMF configuration, TMF takes the following actions:
•
It purges the entire TMF configuration, including the data volume configuration and
all audit information.
•
It produces an empty configuration with no audit trails and with default values for
other configuration information.
Caution. You should delete the TMF configuration only when necessary. This action has the
following consequences:
•
Any existing audit trail files are purged.
•
All online dump entries in the TMF catalog are invalidated, and then are deleted the next
time TMF is started.
•
It is no longer possible to do volume recovery or file recovery from dumps generated in the
deleted environment.
Unless you have obtained a clean shutdown of TMF immediately before deletion, the following
consequences also result:
•
Any distributed transactions that were in progress are abandoned completely.
•
The database might be left in an inconsistent or damaged state.