Aborting a Transaction - Call-Level Interface Version 2

Teradata Call-Level Interface Version 2 Reference for Workstation-Attached Systems

Product
Call-Level Interface Version 2
Release Number
16.10
Published
May 2017
Language
English (United States)
Last Update
2018-05-01
dita:mapPath
ggf1488824663364.ditamap
dita:ditavalPath
Audience_PDF_include.ditaval
dita:id
B035-2418
lifecycle
previous
Product Category
Teradata Tools and Utilities

Under some circumstances, such as the detection of a break key at a keyboard, the application may want to stop and abort a transaction on a session.

If a transaction is “between requests” that is, does not have an active Teradata SQL request, the application program can abort the transaction by sending in a Teradata SQL request containing a single Teradata SQL ABORT or ROLLBACK statement.

The request is submitted the same way as any other Teradata SQL request, described above.

When the transaction is aborted, the Teradata Database discards the Teradata SQL response being held for any Teradata SQL request in the transaction, closes out all Teradata SQL requests in the transaction, and backs out from the Teradata Database any effects of the Teradata SQL requests in the transaction.