Effect of a Database Restart - Teradata Director Program

Teradata® Director Program Reference - 17.20

Deployment
VantageCloud
VantageCore
Edition
Enterprise
IntelliFlex
Lake
VMware
Product
Teradata Director Program
Release Number
17.20
Published
June 2022
Language
English (United States)
Last Update
2023-11-17
dita:mapPath
cki1641301536147.ditamap
dita:ditavalPath
obe1474387269547.ditaval
dita:id
frc1470439950465
Product Category
Teradata Tools and Utilities

When a database restarts, sessions remain but active requests not in-doubt are terminated. When the database recovers, TDP elicits error responses from the database for all requests that were active at the time of the restart. These responses will then be reflected to the application.

Sessions that did not have active requests but were in-transaction have lost the in-transaction state. So the next request sent by the application will be unconditionally aborted to reflect the loss of transaction status to the application.

In-doubts requests remain in-doubt.

If a previously active SP is down after a restart, TDP switches any sessions on that SP to other SPs as session capacity exists. This is transparent to the application except that a request initiated before the session is switched will be delayed.