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

Teradata RDBMS Database Administration - NCR

NCR Teradata RDBMS Database Administration - NCR , 2004. - 616 p.
Download (direct link): teradatadatabaseadmin2004.pdf
Previous << 1 .. 133 134 135 136 137 138 < 139 > 140 141 142 143 144 145 .. 218 >> Next

Manually Saving

10 - 20 Teradata RDBMS Database Administration

Chapter 10: Handling Teradata Crashdumps

Unloading PDE Crashdumps on Windows 2000

Handling PDE Crashdumps on Windows 2000

For Windows 2000 systems, the default is to write crashdumps to flat files on the drive on which Teradata RDBMS is installed. Typically, the path is:

D:\Program Files\NCR\TDAT\tdConfig\pdedumps

You can save PDE crashdumps files in the DBC.Crashdumps database, if you prefer. For instructions, see "Writing PDE Crashdump Files into DBC.Crashdumps" on page 10-23.

Using the CSP Utility

The CSP utility saves PDE crashdumps on Windows 2000. The behavior of CSP is controlled by GDO options accessible through the SCREEN DEBUG command of the ctl utility.

The default is for CSP to run each time the Teradata RDBMS starts. CSP reads any files created by the DMP program in the Dump area and converts them into dump files labeled Crash_timestamp_nn. The most recent crashdump captured is the first one saved (last in, first out).

CSP can take about 30 minutes to save a crashdump from the dump directory to D:\Program Files\NCR\TDAT\tdConfig\pdedumps directory. When CSP is finished, three files, similar to the following, exist for each dump:

02/18/99 01:07p 122,398,440 Crash_19 9 9 0218_1243 4 5_02

02/18/99 12:51p 0 Crash_19 9 9 0218_1243 4 5_02.dir

02/18/99 01:08p 3,915,832 Crash_19 9 9 0218_1243 4 5_02.pag


The file name . Where the parameter . Indicate the contents are .
Crash_YYYYMMDD_HHMMSS_nn Timestamp YYYYMMDD_HHMMSS represents the Y2K-compatible date and time the dump was created. nn is a system-global counter that increments by 1 each time a dump is taken. crashdump data associated with the timestamp and counter.
Crash_YYYYMMDD_HHMMSS_nn.pag index of the Crashdump.
Crash_YYYYMMDD_HHMMSS_nn.dir Not used at this time.

10 - 20

Teradata RDBMS Database Administration Chapter 10: Handling Teradata Crashdumps

Unloading PDE Crashdumps on Windows 2000

Manually Saving PDE Crashdumps

Because CSP can greatly impact system resources, you should temporarily disallow the system from automatically capturing crashdumps. The Screen Debug fields in the ctl utility should read as follows:

Field Name Value
Maximum Dumps 0
Save Dumps Off

If crashes begin to occur, change the Maximum Dumps value in Screen Debug to a small non-zero value and let the system capture at least one dump after a crash. Then manually save the crashdump by following the procedure in "Writing PDE Crashdump Files into DBC.Crashdumps."

Manually saving dumps with CSP during scheduled maintenance time instead of automatically saving dumps helps reserve system resources. You can save the PDE crashdump manually, out of sequence if necessary, to determine the cause of failure. Contact the TSC for assistance.

Note: NCR recommends that you leave the Auto Dump Clear option set to On, so that space is always available to perform a dump when a node crashes in case the dump is needed for database recovery.

Error Messages

Error Messages related to saving PDE Crashdumps are logged in the Windows Event Viewer Application Log.

Writing PDE Crashdump Files into DBC.Crashdumps

You can override the Windows 2000 default of saving PDE dumps as flat files. To save them in the DBC.Crashdumps database, you use the CSP and the ctl utility. First, however, make certain that the current PERM allocation for DBC.Crashdumps is large enough to hold three, or at the very least two, PDE crashdumps.

Note: If space is not adequate, dumps may not captured or may not be usable. The complete procedure to override the default is as follows:

10 - 20 Teradata RDBMS Database Administration

Chapter 10: Handling Teradata Crashdumps

Unloading PDE Crashdumps on Windows 2000

Step Action
1 Calculate how much total PERM space you need in DBC.Crashdumps. For guidelines and a general formula, see "Calculating DBC.Crashdumps Space Requirements" on page 10-13.
2 Query the DBC.DiskSpace view to find the current MAXPERM of user DBC.Crashdumps: SELECT DataBaseName, SUM(MaxPerm) FROM DBC.DiskSpace WHERE DataBaseName = Crashdumps;
3 Compare the current space to your requirements.
IF ... THEN .
DBC.Crashdumps does not need more space Go to step 5.
DBC.Crashdumps needs more space query the DBC.DiskSpace view for database (or user) DBC and go to step 4.

4 Compare the amount you need to add to DBC.Crashdumps with the DBC SUM(MaxPerm) amount to see whether DBC can be reduced by that much and still grow to accommodate a maximum-sized transient journal.
user DBC does not have enough space to allocate more to DBC.Crashdumps. you can: Retain the default and let the dumps be written as flat files to \pdedumps on your local drive. Make more space in DBC by - Adding disks - Dropping obsolete tables, indexes, procedures, users, and/or databases.
user DBC has enough space to allocate more to DBC.Crashdumps a Submit the following SQL statement: MODIFY USER DBC.Crashdumps AS PERM=nnnnnnnnnn [BYTES]; where nnnnnnnnnn is the total amount of permanent space you calculated in step 1. b Go to step 5.
Previous << 1 .. 133 134 135 136 137 138 < 139 > 140 141 142 143 144 145 .. 218 >> Next