How to Restore a Database After a Failed ABORT Request | Basic Teradata Query - Restoring a Database After a Failed ABORT Request - Basic Teradata Query

Basic Teradata® Query Reference

Product
Basic Teradata Query
Release Number
17.10
Published
February 2022
Language
English (United States)
Last Update
2022-02-03
dita:mapPath
nnw1608578382132.ditamap
dita:ditavalPath
obe1474387269547.ditaval
dita:id
B035-2414
lifecycle
previous
Product Category
Teradata Tools and Utilities
If the request did not affect the database, or if the affect was not damaging, then the impact of a failed abort request is minimal. If the request damaged the database, then correct the damage using one of the following options:
  • If the request was embedded in a transaction, abort the transaction by submitting an SQL ABORT statement as a normal SQL request, which backs out the effect of the damaging request.
  • If the request was not embedded in a transaction, submit a second request that has the opposite effect of the first, thus returning the database to its state before the damaging request.