Download (direct link):
Windows 2000 PDE crashdump messages are stored in the Windows 2000 Event Log. To view them, use your Microsoft Event Viewer.
Finding Vproc to Node Mappings with csppeek
You may need to find PDE crashdump information for one or more nodes, or all nodes. The DULTAPE and DUL utilities can provide this information, but they operate on the basis of vproc IDs, rather than node IDs in cabinet-module (cc-mm) format.
The csppeek command of CSP has a useful option, -N, which shows the mapping of internal vproc IDs to node IDs.
The -N option is useful for creating partial dumps when you know the node ID, but you do not know the internal vproc ID corresponding to the node.
This option also accepts a variety of useful values, such as "all" for a map of all nodes in the dump, or a list of one or more node IDs or vproc IDs.
Each PDE crashdump table contains the mapping information for the time the PDE crashdump was captured.
You must specify the PDE crashdump name because the vproc-to-node mapping can change each time the Teradata RDBMS restarts.
You can enter the csppeek command in any DB Window. The following examples illustrate how to find a vproc or node ID.
10 - 10 Teradata RDBMS Database Administration
Chapter 10: Handling Teradata Crashdumps
Finding PDE Crashdump Data
The following table lists examples of ways to find the vproc or node ID.
IF you want to . THEN enter the csppeek command in the following format . TO obtain this type of display .
find the vproc number for one or more nodes for a particular PDE crashdump # /usr/ntos/bin/csppeek -d PDE crashdumpid -N nodeid For example, you might enter: # /usr/ntos/bin/csppeek -d Crash_95 0 916_0 64 823_0 5 -N all VPROC ID NODE ID 10241-0 10251-2 10262-0 10272-2 10283-0 10293-2 The response gives the vproc IDs for all nodes
find the ID of the vproc associated with node 6-2 # /usr/ntos/bin/csppeek -d Crash_95 0 916_0 64 823_0 5 -N 6-2 VPROCNODE 1035 6-2
find the vproc IDs for more than one node # /usr/ntos/bin/csppeek -d Crash_95 0 916_0 64 823_0 5 -N "3-2 5-0" VPROCNODE 10293-2 10325-0
get the entire system vproc-to-node mapping # /usr/ntos/bin/csppeek -d Crash_95 0 916_0 64 823_0 5 -N all VPROCNODE 10304-0 10314-2 10325-0 10335-2 10346-0
find the mapping of one or more nodes and one or more vprocs # /usr/ntos/bin/csppeek -d Crash_95 0 916_0 64 823_0 5 -N "3-2 1030 1031" VPROCNODE 10293-2 10304-0 10314-2
find the nodeID when you know the vprocID # /usr/ntos/bin/csppeek -d Crash_95 0 916_0 64 823_0 5 -N 1024 VPROC ID NODE ID 10241-0
10 - 10
Teradata RDBMS Database AdministrationChapter 10: Handling Teradata Crashdumps
About System User DBC.Crashdumps
About System User DBC.Crashdumps
The DIPname SQL script files are usually executed as part of the Teradata RDBMS installation procedure. The DIPCRASH script creates user Crashdumps in system user DBC, which is thus the immediate owner.
Note: DBC.Crashdumps is created on both UNIX and Windows 2000 installations. Because the default on Windows 2000 is to store crashdumps files as flat files, it may be that the PERM allocation in the CREATE USER CRASHDUMPS statement has been reclaimed. If you want to override the default on Windows 2000 and write dumps into DBC.Crashdumps, be sure to check the currently available PERM space as detailed in "Writing PDE Crashdump Files into DBC.Crashdumps" on page 10-23.
• The rows of the Crashdump tables are hash distributed.
• Crashdumps is created with the FALLBACK option.
Caution: Be aware that editing the script file to erase (or insert NO in front of) the FALLBACK keyword means that no dumps will be saved if an AMP goes down. With a down AMP, Teradata can only retrieve a complete dump when fallback rows are available.
Crashdumps space is allocated from current PERM space for DBC. Once you create the Crashdumps database, you can modify user Crashdumps to either increase or reduce its space allocation (see "Modifying DBC.Crashdumps Space" on page 10-13).
• Reducing Crashdumps space makes more free space available in DBC.
• Increasing Crashdumps space reduces DBC space.
Dump Data Access and Protection Considerations
DIP creates the Crashdumps database with the FALLBACK protection option. Because tables default to the same protection defined for the database in which they reside, the PDE dumps are saved as fallback tables by default.
The FALLBACK option enables dumps to be saved in the database when an AMP is down.
This means that even if the Teradata RDBMS cannot come up with all vprocs, you can still access current dump data with the client-resident Dump Load/Unload (DUL) utility to find the cause of the problem. (For DUL utility usage information, see Teradata RDBMS Utilities.)
Note: Without fallback, you will not be able to access current dump data if an AMP is down.
10 - 12 Teradata RDBMS Database Administration
10 - 11Chapter 10: Handling Teradata Crashdumps