Crashdumps appear as table images, which contain information that Teradata Customer Support uses to investigate crashes.
Crashdumps accumulate as long as there is available space. You must delete old crashdump files manually.
To assign perm space to the crashdumps:
- Calculate optimal perm space for the crashdumps database using the formula:
Crashdumps Perm Space = (Number of TPA Nodes) * (Memory in GB per node) * (6)
This equation is based on the following assumptions:- 32 GB of memory per node
- A crashdump uses approximately 50% of node memory capacity
- Allocate enough space for at least 3 crashdumps
- If you specify FALLBACK protection for tables, the required space doubles
Based on these assumptions, the calculation for a four-nodes system is:
Crashdumps Perm Space = (4) * (32 GB) * (6), or 768 GB.
- Modify the default perm space value for the crashdumps user from the 1 GB default to the calculated value:
MODIFY USER Crashdumps AS PERM=perm_spaceSTARTUP = '' FALLBACK NO BEFORE JOURNAL NO AFTER JOURNAL COLLATION = HOST DEFAULT CHARACTER SET = LATIN DATEFORM = INTEGERDATE TIME ZONE = NULL ;
where perm_space is the amount of space you calculated. All other syntax elements shown are default settings.
Periodically monitor crashdumps space utilization and adjust space allocations as necessary.
Related Information
For step... | Information on... | Is available in... |
---|---|---|
1 and 2 | The use and maintenance of the crashdumps database | Teradata Vantage™ - Database Administration, B035-1093 |
Details about perm space | ||
2 | The MODIFY DATABASE statement | Teradata Vantage™ - SQL Data Definition Language Syntax and Examples, B035-1144 |