Listing Teradata Crashdumps Using CSP - Teradata Database

Listing Teradata Crashdumps Using CSP

Using the CSP utility, you can list views in either the dump directory or the DBC.Crashdumps database.

To list the available crashdumps saved in the DBC.Crashdumps database, use the following CSP command:

# csp -mode list -source table

To list the available raw PDE dumps, use the following CSP command:

# csp -mode list -source dump

Note: The -source parameter defaults to the dump directory. Therefore submitting
“csp -mode list” is equivalent to “csp -mode list -source dump”.

The output will show the fields listed in the following table.

Note: The first line shows if the output is from the dump directory or the database:

csp: Searching for dumps in Teradata database Crashdumps on the local system

or

csp: Searching for dumps in raw dump directory

CSP Output Column	Description
Sel	If an asterisk for the crashdump is listed for this row, the crashdump is eligible or selectable for the specific list, save, or clear operation. If there is no asterisk, it is not included as part of the specific list, save, or clear operation.
ID (date-time-token)	The identifier assigned by CSP to the crashdump. For example, the ID 2008/11/08-15:55:26-24 means the crashdump was taken: On the date of November 8th, 2008 At the time of 15:55:26 With the token 24
Nodes	Number of nodes from which crashdumps information has been collected. If one of four nodes is down, that node is not included.
Event	The TDBMS/PDE event code which caused the crash.
Instigator	The trigger for the crashdump. The format is vproc number/Partition ID/Task ID. In the examples that follow the table: the vproc number is 16384 the Partition IDs are 0 and 11 the Task IDs that triggered the crashdump are 11480, 15160, 28272 and 6418).
Status	The status of the crashdump. If a crashdump is corrupted or is from the wrong Teradata Database software version, this column will report: “Required files are missing or corrupted” or “Dump belongs to a different PDE version.” If the field is blank, the crashdump is usable and valid.

You can constrain the CSP results with criteria such as listing all dumps from a specific date:

# csp -mode list 2008/09/09

csp: Searching for dumps in raw dump directory /var/opt/teradata/tddump

csp: 4 dumps found, 1 dump to process

csp: Sel   ID (date-time-token)   Nodes  Event  Instigator         Status

csp: ---  ----------------------  -----  -----  ---------------    ------

csp:  *   2008/09/09-17:03:13-02      1  10196  16384/0/(11480)

csp:      2008/08/14-11:35:58-01      1  10196  16384/0/(15160)

csp:      2008/07/11-14:41:58-01      1  10416  1/11/(28272)

csp:      2008/07/01-11:58:42-05      1  10196  16384/0/(6418)

#

Note: Despite the date restriction for searching only for dumps on 2008/09/09, the list command returns all dumps including ones from other days such as 2008/08/14, 2008/07/11, and 2008/07/01. However, the crashdump from the desired date criteria of 2008/09/09 has an asterisk in the Sel field, which shows that it matches the command criteria.

If a node is inaccessible (for example, it is down because the BYNET or the PDE is not running), CSP will not be able to access the dump directory on that node. It will report the raw PDE dumps only one nodes that are up.

# csp -mode list

csp: Searching for dumps in raw dump directory /var/opt/teradata/tddump

csp: 4 dumps found, 4 dumps to process

csp: Sel   ID (date-time-token)   Nodes  Event  Instigator         Status

csp: ---  ----------------------  -----  -----  ---------------    ------

csp:  *   2008/09/09-17:03:13-02      1  10196  16384/0/(11480)

csp:  *   2008/08/14-11:35:58-01      1  10196  16384/0/(15160)

csp:  *   2008/07/11-14:41:58-01      1  10416  1/11/(28272)

csp:  *   2008/07/01-11:58:42-05      1  10196  16384/0/(6418)

#