Home Page for the TeradataForum

Archives of the TeradataForum

Message Posted: Wed, 25 May 2005 @ 13:47:53 GMT

  <Prev Next>   <<First <Prev Next> Last>>  

Subj:   Re: Fastload Problem: No room in database
From:   Richard Perry


I would start by recruiting someone that understands Teradata.

Failing that try the following:

     select vproc, sum(currentperm), sum(maxperm) from
     where databasename = 'NNNNNNNNNNNNN'   replace NNNNNNNNNN with the target databasename
     group by 1;

If this shows heavy skewing to one or more Amps then this may be the problem. However, if the data on the target database is evenly distributed, you should then have a look at which database the log / error tables are being written to.

If the SQL above shows skewing on the target database you should identify the table or tables that are skewed, and check the suitability of the primary indexes and adjust as necessary.

If you find that the log tables are being written to a database other than the one you expected, or one that is low on space, I would suggest you either allocate more space to the database or choose an alternative.

If all of the above fails don't give up hope, just keep trying, I am sure all will come good in the end.

  <Prev Next>   <<First <Prev Next> Last>>  
  Top Home Privacy Feedback  
Copyright for the TeradataForum (TDATA-L), Manta BlueSky    
Copyright 2016 - All Rights Reserved    
Last Modified: 15 Jun 2023