Teradata Database Crash and Recovery - Call-Level Interface Version 2

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

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

When the Teradata Database detects an internal error that prevents it from continuing, it will store diagnostic information and reinitialize itself. This event is called a crash (or reset). After the Teradata Database has reinitialized, it rolls back any incomplete transactions or requests in progress. This process is called a recovery.

When an AP on an AP/1012 or 3600 system is taken down or encounters an internal error that prevents it from continuing, it will shut down. This event is called an AP reset. Any incomplete transactions or requests in progress for sessions connected through that AP will be rolled back. Sessions connected through any other APs are unaffected.