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 .. 131 132 133 134 135 136 < 137 > 138 139 140 141 142 143 .. 218 >> Next


4 Compare SUM(MaxPerm) for Crashdumps with the amount you calculated as your total space requirement.

IF Crashdumps SUM(MaxPerm) is . THEN .
less than your crashdump total space requirement modify user DBC.Crashdumps and increase its PERM allocation by this difference. a Note the difference for use in step 7. b Go to step 6.
equal to or somewhat greater than your crashdump total space requirement end the session. You do not need to modify DBC.Crashdumps PERM.
much greater than your crashdump total space requirement modify user DBC.Crashdumps and reduce its PERM allocation to increase available free space in user DBC.

10 - 12

Teradata RDBMS Database Administration 10 - 11 Chapter 10: Handling Teradata Crashdumps

About System User DBC.Crashdumps

Step Action
5 Query the DBC.DiskSpace view to find the current MAXPERM for user DBC: SELECT DataBaseName, SUM(MaxPerm) FROM DBC.DiskSpace WHERE DataBaseName = DBC;
6 Compare the SUM(MaxPerm) of DBC with the amount you want to increase Crashdumps (derived in step 5) to verify that DBC has enough space to accommodate both of the following: Transfer of the necessary increase to Crashdump. Retention of adequate space for the largest-anticipated transient journal, including overhead.

IF DBC has enough space for your largest transient journal . THEN .
plus enough space to increase Crashdumps for three dumps go to step 10.
plus enough space to increase Crashdumps for two dumps decide whether this is sufficient: If it is, go to step 10. Otherwise, go to step 8.
but not enough space to increase Crashdumps for even two dumps go to step 8.

Increase available space in user DBC and update system space counters:

Step

Action

To add PERM space to DBC, perform one or more of the following:

Transfer space to DBC from some other database or user by modifying the database or user to reduce its PERM allocation.

Drop obsolete tables and modify the owning database or user to reduce its PERM allocation.

Drop obsolete databases and / or users.

Make sure system logs and tables have been archived, if needed, and reset or purged. (For details, see "Maintaining Your Data Dictionary Logs and Tables" on page 4-15.)

Add disks to the configuration

Update current space calculations for users, databases, and DBC, as described in step 3.

Query DBC.DiskSpace to see the current MAXPERM for DBC, as described in step 6.

Repeat step 8 until MAXPERM for DBC is large enough to increase DBC.Crashdumps.

7

a

b

c

8

10 - 12 Teradata RDBMS Database Administration

10 - 11 Chapter 10: Handling Teradata Crashdumps

About System User DBC.Crashdumps

Step Action
9 When DBC has enough space, submit the following statement: MODIFY USER DBC.Crashdumps AS PERM=nnnnnnnnnn [BYTES]; where nnnnnnnnnn is the total amount of permanent space you calculated as necessary in step 1.
10 After the statement completes successfully, you can log off the session and quit BTEQ.

10 - 12

Teradata RDBMS Database Administration 10 - 11 Chapter 10: Handling Teradata Crashdumps

Administering PDE Crashdumps

Administering PDE Crashdumps

This section describes how the system captures a PDE Crashdump and how to force a PDE Crashdump capture to occur.

You can force a crash or restart to recover from a system hang. The forced dump may provide useful information about why the system hung.

You can control the dump type (System or PDE) by the way you force the dump. Select the type of dump you need from the following table.

IF one or more of these conditions exist . THEN use .
The node is not responding System dump
The system is not making a PDE crashdump. (The system does not respond to input while it is making a PDE crashdump).
Teradata RDBMS sessions are not progressing PDE crashdump
New sessions cannot start
The Administration Workstation (AWS) is responding
The rlogin shell is responding.

Automatic PDE Crashdumps

The following table describes the events that cause a PDE crashdump:

This event . Can occur .
Teradata RDBMS error restart for many reasons. Most commonly, a restart is due to a fatal error condition in the Teradata RDBMS. The PDE Crashdump capture occurs before the restart on each node in order to preserve the error information in node memory.
forced Teradata RDBMS restart (with PDE crashdump) at any time, using restart commands. Only use restart commands for maintenance, so you do not interrupt jobs that are running. See "Forcing a PDE Crashdump" on page 10-18.

Teradata RDBMS Database Administration

10 - 17 Chapter 10: Handling Teradata Crashdumps

Administering PDE Crashdumps

This event . Can occur .
Windows 2000 operating system crash for many reasons. It might not be caused by Teradata RDBMS operations, but a Windows 2000 crash always causes a Teradata RDBMS restart. A Windows 2000 memory dump is captured; see "Handling Windows 2000 System Dumps" on page 11-9. The default is not to save dumps into Crashdumps, but to save 'dbm' style dumps. These are stored as Windows 2000 files; by default, the files are saved in the directory C:\Program Files\NCR\TDAT\tdConfig\pdedumps. (For more information on Windows 2000 dumps, see "Administering PDE Crashdumps" on page 10-17.)
Previous << 1 .. 131 132 133 134 135 136 < 137 > 138 139 140 141 142 143 .. 218 >> Next