Save Crashdumps to Disk | Teradata Vantage - 17.00 - 17.05 - Saving Crashdumps to Disk - Advanced SQL Engine - Teradata Database

Teradata Vantage™ - Database Administration

Product
Advanced SQL Engine
Teradata Database
Release Number
17.00
17.05
Published
June 2020
Language
English (United States)
Last Update
2021-01-22
dita:mapPath
rgu1556127906220.ditamap
dita:ditavalPath
lze1555437562152.ditaval

If you cannot use FTP services to send your crashdumps to Teradata and must save your crashdumps to disk, use the DUL utility. DUL is a separate package that you must order and install individually. For more information on DUL, see Teradata Vantage™ - Database Utilities , B035-1102 .

You can unload crashdump information to several sequential files, which are:
  • Rows of data dumped from the AMPs
  • Internal load module correspondence information
  • Applicable rows from Software_Event_LogV

Mainframe systems have only one copy of each of these files. System with multiple nodes have one copy for each node involved in the crashdump.

By default, crashdump files are named Crash_yyyymmdd_hhmmss_nn where:

Variable Definition
yyyymmdd Year, month, and day of the crashdump
hhmmss Time (hour, minute, and second) of the crashdump
nn Sequential number associated with the crashdump

You can change the file name using BTEQ, but remember that the timestamps are important. For more information on DUL, see Teradata Vantage™ - Database Utilities , B035-1102 .