You can use Teradata Viewpoint to regularly monitor space usage, and catch most space problems. However, it may be useful to setup a few alerts in areas where space problems can seriously affect database function.
The following table contains some examples of common space usage alerts.
| Alert | Setup Parameters | Response to Alert Occurrence |
|---|---|---|
| Crashdumps Space The crashdumps database needs enough space to contain possible large data dumps that occur during crashes, and which are used in system recovery. |
Alert rules:
Alert Action:
Severity: Medium |
|
| DBC Space User DBC contains all system tables and logs. Critical system functions depend on DBC having enough space. You can set the same alert parameters for system databases DBCMNGR and SystemFE, which perform other critical system functions.
|
Alert rules:
Alert Action:
Severity: Medium |
Add perm space to the database. |
Set up three alerts to identify when a database exceeds important space thresholds.
|
Alert rules:
Alert Action:
Severity: (apply one of the following to the related alert)
|
You should allocate additional perm space to a database as soon as possible after perm space usage exceeds 90%. Databases that trigger the High or Critical alert levels before you can respond to a Medium alert are growing very fast and should receive more space immediately. You can investigate which tables are using database perm space. |