16.20 - Facility To Save Crashdump Streams - Teradata Database - Teradata Vantage NewSQL Engine

Teradata Vantage™ NewSQL Engine Release Summary

Product
Teradata Database
Teradata Vantage NewSQL Engine
Release Number
16.20
Published
March 2019
Content Type
Release Notes
Publication ID
B035-1098-162K
Language
English (United States)
Last Update
2019-05-03

Previously, when a crashdump occurred, customers used the Crashdump Save Program (CSP) to save the raw crashdump to the Crashdumps database on the customer system. This dump data then had to be exported using the Dump Unload/Load (DUL) utility and sent to Teradata in-house systems for further analysis. For large MPP systems, this was a serial process that could be resource-intensive and time-consuming, delaying root-cause analysis.

Now customers have the option to save a crashdump as a flat (stream) file on each node. The stream files are in compressed binary FastLoad format. Stream files can either be sent directly to the Teradata Support Center from the production system or moved onto another system at the customer site. Customers can save stream files all at once or a few nodes at a time.

Benefits

  • Stream files make it easier and faster to move dump data to the Teradata Support Center. Customers do not need to save to or export from the Crashdumps database on the production system.
  • Stream files enable you to move a dump to an on-premises test system for debugging. This frees the production system for other tasks.

Considerations

Both SMP and MPP platforms can save and transmit crashdump stream files.

Additional Information

For more information, see Teradata Vantage™ - Database Administration, B035-1093.