DWHPro Insights

No More Room in Database (Error 2644) in Teradata: Causes and Fixes

By Roland Wenzlofsky ·

No More Room in Database (Error 2644) in Teradata: Causes and Fixes

Teradata Version 16.00 introduces thrilling Space Management features capable of significantly enhancing daily data warehouse administration and loading processes.

In my current setting, the data warehouse’s daily loading is frequently interrupted due to insufficient permanent database storage.

The maximum capacity of a database is established during its creation. The following syntax creates a database with a permanent space of 80 GB:

CREATE DATABASE Customer AS PERM = 80000000000;

Teradata evenly distributes the defined space across all AMPs. Assuming the availability of 8 AMPs, each AMP will have 10GB of permanent space allocated.

Limits for Skewed Tables

Is the PermSpace evenly distributed among all AMPs if the table rows are not uniformly distributed?

Assuming we need to load an 11GB table and the Primary Index assigned all rows to only one AMP, which is an inefficient design choice. As each AMP has a space limit of 10GB, we will encounter an error message:

Teradata Query Performance Tuning: The DWHPro Guide book cover

Get the complete Teradata tuning book, free

Teradata Query Performance Tuning: The DWHPro Guide
By Roland Wenzlofsky & Artemios Vogiatzis

206 pages on statistics and demographics, access paths and indexes, query execution plans, and joins. Get the full PDF and practical Teradata updates from DWHPro.

Confirm your email to receive your download link. Privacy policy. Unsubscribe in any newsletter.

About the free book

Skew/soft limits change space accounting; they do not create physical capacity or eliminate every 2644 error. Monitor both per-AMP use and aggregate capacity. The corrected 80 decimal GB example is 80,000,000,000 bytes; no large allocation was performed.

Despite the 10GB available on the remaining 7 AMPs, Teradata cannot load the table.

Use the documented space views for the deployed release and inspect their keys and aggregation level. DBC.DatabaseSpace contains AMP-level space accounting; aggregate the appropriate rows for a database total rather than treating each row as a whole-database total. CurrentPermSpace and MaxPermSpace are not a substitute for checking physical capacity.

Teradata 16.00 provides the option to globally define available space, effectively reducing or eliminating related issues.

The introduction of the new DBC Table GlobalDBSpace and an expanded syntax for database creation has been implemented.

CREATE DATABASE Customer AS PERM = 80000000000 SKEW = 10 PERCENT;

The new “SKEW = 10 PERCENT” feature is set when creating the database and means the following:

The PermSpace capacity remains at 80GB. Each of the eight AMPs can store up to 11GB of data if the database’s absolute limit of 80GB is not surpassed. This determines the percentage by which an AMP can surpass its assigned space without the query being terminated.

Skew and soft-limit controls can accommodate some accounting imbalances within available capacity. They cannot prevent every insufficient-space failure, and require monitoring and an explicit capacity policy.

Global Space Soft Limit

The Global Space Soft Limit is defined via DBSControl GlobalSpaceSoftLimit.

A 10% aggregate soft-limit allowance on an 80 decimal GB limit corresponds to 88 decimal GB in the simplified arithmetic. It does not independently grant every AMP 11 GB: per-AMP skew controls, aggregate accounting and available physical space must all be considered. Check the release-specific GlobalSpaceSoftLimit behavior before configuring it.

When the database size exceeds the base size, an event is triggered and recorded in the Software Event Log. These log entries enable administrators to analyze the situation and implement necessary measures.

Deciding what to change in your data platform?

Compare optimisation, modernisation and migration against your workload and business requirements.

Explore independent platform assessments

Teradata Query Performance Tuning: The DWHPro Guide book cover

Get the complete Teradata tuning book, free

Teradata Query Performance Tuning: The DWHPro Guide
By Roland Wenzlofsky & Artemios Vogiatzis

206 pages on statistics and demographics, access paths and indexes, query execution plans, and joins. Get the full PDF and practical Teradata updates from DWHPro.

Confirm your email to receive your download link. Privacy policy. Unsubscribe in any newsletter.

About the free book

Follow DWHPro in Google to see our articles more often in Search.

3 thoughts on “No More Room in Database (Error 2644) in Teradata: Causes and Fixes”

  1. Question about skew = 10 percent: the error “2644 No more room in database Customer” would no longer occur.

    Is it so that you still might get No more room in database. Now you have just 1 gigabytes per AMP more space to follow clumsy primary index?

    Reply

Leave a Comment

Teradata Query Performance Tuning: The DWHPro Guide book cover

Get the complete Teradata tuning book, free

Teradata Query Performance Tuning: The DWHPro Guide
By Roland Wenzlofsky & Artemios Vogiatzis

206 pages on statistics and demographics, access paths and indexes, query execution plans, and joins. Get the full PDF and practical Teradata updates from DWHPro.

Confirm your email to receive your download link. Privacy policy. Unsubscribe in any newsletter.

About the free book

Protected by Security by CleanTalk and CleanTalk Anti-Spam