Perm Space Management

Database
The Teradata Database channel includes discussions around advanced Teradata features such as high-performance parallel database technology, the optimizer, mixed workload management solutions, and other related technologies.
Enthusiast

Perm Space Management

I have seen few databases have consumed more than 200 percent perm space. What is the reason for consuming more than 100 percent space. There are lot of databases having small amount of space but not in use. What is the best practice to collect all scattered space and allocate to a specific database for future use. Is there any script for scattered unused space collection ?


Accepted Solutions
Teradata Employee

Re: Perm Space Management

Which release of TD, and how are you determining the percentage?

 

Prior to TD16, restoring databases from a larger TD system to a smaller one (and not following best practices for adjusting space) can result in some Perm Space anomalies. 

Starting with TD16, Global Space Management introduces additional options for how limits are applied.

 

You can use MODIFY DATABASE to reduce the allocation and allow the space released to flow to the parent (immediate owner). Or use the "move space" approach as Teradata tools do: CREATE DATABASE Space_To_Move FROM OverAllocated_DB AS PERM=n; GIVE Space_to_Move TO Receiving_DB; DROP DATABASE Space_To_Move;

 

 

1 ACCEPTED SOLUTION
1 REPLY
Teradata Employee

Re: Perm Space Management

Which release of TD, and how are you determining the percentage?

 

Prior to TD16, restoring databases from a larger TD system to a smaller one (and not following best practices for adjusting space) can result in some Perm Space anomalies. 

Starting with TD16, Global Space Management introduces additional options for how limits are applied.

 

You can use MODIFY DATABASE to reduce the allocation and allow the space released to flow to the parent (immediate owner). Or use the "move space" approach as Teradata tools do: CREATE DATABASE Space_To_Move FROM OverAllocated_DB AS PERM=n; GIVE Space_to_Move TO Receiving_DB; DROP DATABASE Space_To_Move;