16.10 - Saving Crashdumps to Disk or Tape - 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)

If you cannot use FTP services to send your crashdumps to Teradata and must save your crashdumps to disk or tape, use the DUL or DULTAPE utility. DUL and DULTAPE are separate packages that you must order and install individually. For more information on DUL and DULTAPE, see Utilities.

Use this utility … On a … To load/unload a crashdump to/from a …
DUL node file on the node.
mainframe file or a tape.
You must run DULTAPE on the node that has the internal tape drive.
DULTAPE node tape.
You must run DULTAPE on the node that has the internal tape drive.

DULTAPE uses the FastLoad utility to copy a crashdump onto a tape. You can run multiple DULTAPE sessions as long as the total number of sessions does not exceed the limit specified in the MaxLoadTasks field in DBS Control.

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

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 name using BTEQ, but remember that the timestamps are important. For more information on DUL and DULTAPE, see Utilities.