Manually Saving Teradata Crashdumps - Teradata Database

Teradata Database Administration
Product
Teradata Database
Release Number
15.10
Language
English (United States)
Last Update
2018-10-06
Product Category
Software

Manually Saving Teradata Crashdumps

CSP is controlled by the SCREEN DEBUG command of the ctl utility. Use CSP to save crashdumps manually:

1 Submit the following command to list the available raw PDE crashdumps: 

#csp -mode list -source dump

2 Save the raw PDE dumps into table format in the DBC.Crashdumps database.

  • The basic form of the CSP command for saving crashdumps is:
    • #csp -mode save -source dump -target stream

    CSP reads any files created by the DMP program in the Dump area and writes them into the Crashdumps database.

  • You can also use the following command to save all dumps found by CSP:
    • #csp -mode save -force
     
    Dump 2007/11/26-09:54:25-01 is about to be saved
    Are you sure? [y,n,q,?] >
     
    A question will be displayed for each dump and the user must answer each one with yes,  no,  or quit (individual letters such as y, n or q can be used).
     
    csp: Searching for dumps in configured PDE dump directory on all nodes
    csp: 3 dump found, 3 dumps to process
     
    csp: Saving dump 1998/11/05-18:55:26-24 to table Crashdumps.Crash_200711
    05_185526_24
    csp: Writing data rows for dump 2007/11/05-18:55:26-24
    csp: Dump 2007/11/05-18:55:26-24 saved
    csp: Dump 2007/11/05-18:55:26-24 cleared
     
    csp: Saving dump 2007/11/04-17:37:53-23 to table Crashdumps.Crash_200711
    04_173753_23
    csp: Writing data rows for dump 2007/11/04-17:37:53-23
    csp: Dump 2007/11/05-18:55:26-24 saved
    csp: Dump 2007/11/05-18:55:26-24 cleared
     
    csp: Saving dump 2007/11/04-17:23:27-22 to table Crashdumps.Crash_200711
    04_172327_22
    csp: Writing data rows for dump 2007/11/04-17:23:27-22
    csp: Dump 2007/11/05-18:55:26-24 saved
    csp: Dump 2007/11/05-18:55:26-24 cleared

    If the SCREEN DEBUG setting has the Save Dumps flag set to not save crashdumps, use the -force option to allow CSP to override the Save Dumps setting. For example, if you submit:

    #csp -mode save -source dump -target stream -force

    By default, the system saves the crashdumps in Last In, First Out (LIFO) order. The most recent crashdumps are saved first. After the crashdump is saved to DBC.Crashdumps, the crashdumps are automatically cleared from the PDE dump directory.

    3 Verify that the crashdumps were properly saved to DBC.Crashdumps by using the following command: 

    # csp -mode list -source table
    csp: Searching for dumps in Teradata database Crashdumps on the local system
    csp: 1 dump found, 1 dump to process
    csp: Sel   DumpName               Nodes  Event  Instigator     Status
    csp: ---  ----------------------  -----  -----  ------------    ------
    csp:  *   Crash_20080807_142628_01   1   10196  16384/2/(21600)
    #

    You can run CSP commands from any node in the system, but the utility will read the dump directory on all nodes.

    Note: For more information on CSP commands, type csp -h at a Teradata Command Prompt or see the resource file located at /usr/pde/lib/defaults/Libcsp.