16.10 - Automatic Teradata Crashdumps - Teradata Database

Teradata Database Administration

Product
Teradata Database
Release Number
16.10
Release Date
April 2018
Content Type
Administration
Publication ID
B035-1093-161K
Language
English (United States)

The following table describes the events that cause a Teradata crashdump.

This event … Can occur …
Teradata Database error restart for many reasons. Most commonly, a restart is due to a fatal error condition in Teradata Database.

The Teradata crashdump capture occurs before the restart on each node to preserve the error information in node memory.

Forced Teradata Database restart (with Teradata crashdump) at any time, using restart commands.

Only use restart commands for maintenance, so you do not interrupt jobs that are running. See Commands for Forcing a Teradata Crashdump.