Books
in black and white
Main menu
Share a book About us Home
Books
Biology Business Chemistry Computers Culture Economics Fiction Games Guide History Management Mathematical Medicine Mental Fitnes Physics Psychology Scince Sport Technics
Ads

Teradata RDBMS Database Administration - NCR

NCR Teradata RDBMS Database Administration - NCR , 2004. - 616 p.
Download (direct link): teradatadatabaseadmin2004.pdf
Previous << 1 .. 128 129 130 131 132 133 < 134 > 135 136 137 138 139 140 .. 218 >> Next


You can view PDE crashdump information:

On the dump device (UNIX)

In a dump directory (Windows 2000)

In Teradata RDBMS

PDE Crashdumps Location

The Dump Memory Program (DMP) runs at the time the fault or reset is detected. When a system detects a reset, DMP creates .dat files that represent the processes and memory of the system at the time of the reset. Typically, the DMP operation takes place after Teradata RDBMS is back up following the restart.

The following table describes the dump areas for PDE dumps:

10 - 10

Teradata RDBMS Database Administration Chapter 10: Handling Teradata Crashdumps

Finding PDE Crashdump Data

PDE Dump Type Description
UNIX The PDE dump area is the /dev/pdedump disk slice, which holds multiple PDE crashdumps. Dump area slices are called collectively the "dump device". The dump device is a raw disk partition. When an event occurs that causes a PDE crashdump, the dump is captured on all Teradata RDBMS nodes in the system. All nodes work in parallel to write their PDE crashdumps into a common table in DBC.Crashdumps. Shared dumps: If there is no /dev/pdedump slice, the dumps are shared. In this case, all dumps go into the first (or only) UNIX System dump area slice. (Note that such a configuration is not recommended because it allows UNIX System dumps to overwrite PDE crashdumps.) cspspace utility: The dump device is a raw disk partition on which standard file system commands do not operate, making it difficult to determine whether space was available for subsequent dumps. You can use the cspspace command-line utility to determine how much space is available for dumps on UNIX. This is a UNIX-only requirement; normally, it is not required on Windows 2000, because the default on Windows 2000 is to write each dump as a standard file.
Windows 2000 The default PDE crashdump directory is the drive where Teradata RDBMS is loaded (for example, D:\Program Files\NCR\TDAT\tdconfig\pdedumps). To save the files into the DBC.Crashdumps database, see "Writing PDE Crashdump Files into DBC.Crashdumps" on page 10-23. Note: The defaults for Teradata on Windows 2000 saves the crashdump files to disk files in ".dbm" format. See "Writing PDE Crashdump Files into DBC.Crashdumps" on page 10-23 for instructions on how to change the default save location and save crashdumps to DBC.Crashdumps instead.

Checking the Dump Device on UNIX

On a UNIX system, the PDE crashdumps are temporarily stored on the dump device. You can verify the presence of PDE crashdumps on the dump device with the following command:

# /usr/ntos/bin/dbgcsp -e

This command lists any PDE crashdumps and whether or not they have been saved to the dump save area. If there are no PDE crashdumps present, and you have no / dev/pdedump slice, a UNIX System dump may be present.

On Massively Parallel Processing (MPP) systems, you can obtain a summary of all PDE crashdumps on the dump devices of all nodes with the following command:

# /usr/ntos/bin/pdedumpcheck Following is an example of what might display.

10 - 10 Teradata RDBMS Database Administration

Chapter 10: Handling Teradata Crashdumps

Finding PDE Crashdump Data

Gathering crashdump information from 32 nodes... Crash_960312_122838_02:

ap20 Dump on dump device(pages = 0x68e2)

ap50 Dump on dump device(pages = 0x68d6)

ap60 Dump on dump device(pages = 0x68e3)

Crash_960312_132005_01:

ap20Dump on dump device(pages = 0x73d8)

ap50Dump on dump device(pages = 0x73e1)

ap60Dump on dump device(pages = 0x6fde)

ap71Dump on dump device(pages = 0x7384)

Crash_960312_132201_02: ap20Dump copied(pages = 0x1) ap50Dump copied(pages = 0x1) ap60Dump copied(pages = 0x1) ap71Dump copied(pages = 0x1)

The single-page dumps correspond to header-only dumps, which are captured during TPA resets. That is, no data is actually dumped.

Note: If you save a PDE crashdump on one or more nodes, a node that still lists the PDE crashdump as

Dump on dump device

may still be in the process of copying the PDE crashdump to the Teradata RDBMS DBC.Crashdumps database.

Checking the Dump Directory on Windows 2000

On a Windows 2000 system, PDE crashdumps are temporarily stored in the dump directory.

You can check the presence of PDE crashdumps in a dump directory by entering the following command in the Teradata Command Prompt window:

csp -mode list

Checking DBC.Crashdumps with the SQL HELP Statement

You use the SQL HELP statement to list the contents of the DBC.Crashdumps database. Log onto a BTEQ session as the administrative user and submit the following statement:

help database DBC.Crashdumps;

10 - 10

Teradata RDBMS Database Administration Chapter 10: Handling Teradata Crashdumps

Finding PDE Crashdump Data

Viewing PDE Crashdump Messages

Messages are accessed differently according to your operating system:

IF your server OS is ... THEN .
UNIX open the /etc/.osm file to read the messages because they roll quickly down the screen. There may be several messages about Small Computer System Interface (SCSI) time-outs and SCSI bus resets. This is normal, whether or not any data was dumped. When a PDE crashdump occurs, any SCSI busses associated with the PDE dump device and any swap devices are reset. Once the PDE crashdump completes, the SCSI driver restarts any I/O operations that were active at the time of the PDE crashdump.
Previous << 1 .. 128 129 130 131 132 133 < 134 > 135 136 137 138 139 140 .. 218 >> Next