The procedure for Teradata crashdumps is as follows:
1 An event occurs that triggers a crashdump.
2 DMP runs at the time the fault or reset is detected and saves a crashdump to the PDE raw dump directory.
3 After Teradata Database restarts, what happens next depends on the setting of the Save Dumps field of Screen Debug in the Ctl utility. If the field is set to:
Because Teradata Database is a parallel system, a full crashdump is a system-wide entity in a table format consisting of data from each node. All nodes work in parallel to write their piece of the crashdump into a common table in DBC.Crashdumps: they write the contents of memory to internal disk and save the raw PDE dump into the DBC.Crashdumps database on all nodes of the system at approximately the same time.
Note: In some cases, Teradata Customer Support may choose to debug crashdumps directly from the dump area. For more information, see “Debugging Crashdumps” on page 568.
4 Copy the crashdump from the table in DBC.Crashdumps and send the crashdump data to Teradata Customer Support either:
For more detailed information on how to handle crashdumps for your specific OS, see “Handling Teradata Crashdumps” on page 562.