Home Page for the TeradataForum
 

Archives of the TeradataForum

Message Posted: Mon, 24 Apr 2006 @ 14:46:16 GMT


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


Subj:   Re: 2644, No more room in database DBC
 
From:   Diehl, Robert

Warren,

Don't forget you can save a lot of space on your historical copies of DBQL tables by using NO FALLBACK and COMPRESSION.

This post also leads me to bring up a few other points on DBC filling up.

DBC can actually go negative because some tables like Transient Journal are allowed to use more space than what is available in DBC. The negative space situation will actually prevent logons and any DDL as these require addition of rows to DBC tables. To prevent this situation keep plenty of room in DBC. And this is even more important if using ACCESS LOGGING or QUERY LOGGING as they can eat up a lot of space. So real point here is keep lots of space in DBC. DON't create SPOOL RESERVE databases; put the space in DBC. Spool uses any free Cylinders anyhow.

Clean up ACCESS LOGs and QUERY LOGS using History tables.

Another incentive to keep ACCESS and QUERY log history tables is you cannot backup these DBC tables. In the event of a major failure you cannot rebuild these tables. Same applies to RESUSAGE.


Thanks,

Bob Diehl
Travelocity.com



     
  <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