Negative maxperm DBC - response (2) by mikesteeves

This can occur when your restore after a sysinit with a backup from a system that has a larger configuration than the system being retored.  For example, you restored a DBC restore from your production system of 25TB to your Staging system that only have 18TB.  You'll need to manually move disk space in Teradata Administrator, up the hierarchy from lower databases by reducing the size of database's maxperm, which will give that space to its immediate parent.  This effort will in effect, push the space up to DBC.  Keep doing this until your DBC is positive. 
You can also do this in SQL Asst. using statements like the following.
MODIFY Database db123 AS PERM=100000; -- moves space from DB123 to DBOwner since it is its immediate parent.
MODIFY Database dbabc AS PERM=100000; -- moves space from DBabc to DBOwner since it is its immediate parent.
MODIFY Database DBOwnerAS PERM=100000; -- moves space from  DBOwner to sysdba
MODIFY user sysdba AS PERM=100000; -- moves space from sysdba to DBC