Home Page for the TeradataForum
 

Archives of the TeradataForum

Message Posted: Mon, 16 May 2005 @ 12:54:40 GMT


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


Subj:   Error 2644 - No more room in database
 
From:   Shaju Kodian

Hi,

I am using following query to monitor the space. But today, below query is giving me strange statistics for particular amp.

Even though there is enough space in database UAXA i.e. 187 GB allocated , 60 Gb used and 127 GB free when a case partitioned table is loaded using fast load it is giving 2644 error. Simultaneously I am loading into another database which is having no problem. I feel there is some thing strange happened in that particular amp.

Did anybody faced such problem ?

I am pasting the output below the query where currentpermspace is more than maxpermspace for that particular amp.

     -------------------------------------------------------------------
     select  vproc,db2.databasename
             ,cast( sum(dbs.maxpermspace) / (1024*1024*1024) as
     decimal(10,4)) AllocSpaceGB
             ,cast( sum(dbs.currentpermspace) / (1024*1024*1024)  as
     decimal(10,4)) UsedSpaceGB
             ,cast( sum(dbs.maxpermspace) / (1024*1024*1024) as
     decimal(10,4)) - cast( sum(dbs.currentpermspace) / (1024*1024*1024)  as
     decimal(10,4)) FreeSpaceGB
     from dbc.databasespace dbs, dbc.databases2 db2
     where dbs.databaseid = db2.databaseid
     and upper(db2.databasename) = ( 'UAXA' )
     and vproc = 4
     group by vproc, db2.databasename


     -------------------------------------------------------------------
     Vproc   DatabaseName    AllocSpaceGB    UsedSpaceGB     FreeSpaceGB
     4       UAXA            5.8441          11.4754	        -5.6313

Regards,

Sh.



     
  <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: 27 Dec 2016