Aborting a Transaction | Analytics Database (SQL Engine) - Aborting a Transaction - Call-Level Interface Version 2

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

Deployment
VantageCloud
VantageCore
Edition
Enterprise
IntelliFlex
Lake
VMware
Product
Call-Level Interface Version 2
Release Number
20.00
Published
January 2024
Language
English (United States)
Last Update
2024-05-14
dita:mapPath
bmn1691484839905.ditamap
dita:ditavalPath
obe1474387269547.ditaval
dita:id
fvz1470444150352
Product Category
Teradata Tools and Utilities

Under some circumstances, for example, 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, as described earlier.

When the transaction is aborted, the 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 database any effects of the Teradata SQL requests in the transaction.