17.00 - 17.05 - Checking DBC.Crashdumps Space Allocation and Usage - Advanced SQL Engine - Teradata Database

Teradata Vantage™ - Database Administration

Product
Advanced SQL Engine
Teradata Database
Release Number
17.00
17.05
Published
June 2020
Language
English (United States)
Last Update
2021-01-22
dita:mapPath
rgu1556127906220.ditamap
dita:ditavalPath
lze1555437562152.ditaval

When your system was first installed with Teradata database, there was a very small default amount of PERM space allocated to DBC.Crashdumps. You should adjust the space based on what you find is required for your workload and your site. For example, you may have to also increase or decrease the amount of space based on how many crashdumps you want to actually retain at one time. If the starting figures suggested above are not large enough, the best thing to do is run some tests and increase or decrease PERM as required.

As described in Teradata Crashdump Sizes, a full crashdump is the size of the raw dump multiplied by the number of nodes for your system. The DBC.Crashdumps database, which is allocated from the PERM space of DBC, should be large enough to hold 4 to 5 crashdumps.

To first check the amount of space used by DBC.Crashdumps, use the following query:

sel databasename,
sum(maxperm),
sum(currentperm)
from dbc.diskspaceV
where databasename='crashdumps'
with sum(maxperm) (title 'Total'),sum(currentperm)
group by 1;

 *** Query completed. 2 rows found. 3 columns returned.
 *** Total elapsed time was 1 second.

DatabaseName         Sum(MaxPerm)    Sum(CurrentPerm)
-------------------  --------------  ----------------
Crashdumps           21,474,836,424  991,296,000
                     --------------  ----------------

In this example 21,474,836,424 (21 GB) are allocated to the crashdumps database and 991,296,000 (1 MB) is used.