Database space issues

Database
Teradata Employee

Database space issues

Not sure if the below is a DS issue or Teradata issue. Neverthless , I am posting it here

We are using Teradata connector in Bulk/Load mode (this is nothing but fastload in Teradata parlance)to load data into empty teradata table with three columns. The source is a sequential file stage.

Out of three columns in the table, 2 columns have  nulls for all rows and one column has values for all rows. This column which has values, is the primary index of the table and the all values are unique. The table itself is a multiset table i.e, it allows duplicates

When the job runs, it aborts after processing 7 million rows out of 60 million total rows in source. The error we are getting is 

Teradata_Connector,0: RDBMS code 2644: No more room in database .  

When we got in touch with the DB team they told there is a high amount of "skew factor" causing the space to be filled and we have to solve this first rather than increasing space.

Any suggestions?

5 REPLIES
Enthusiast

Re: Database space issues

Can you post the table ddl?

Enthusiast

Re: Database space issues

First you must verify the DB space with this:

Select Sum(MaxPerm) - Sum(CurrentPerm)

From DBC.DiskSpace

Where DatabaseName = 'xxx'

Then calculate how many bytes are each row inserted.

If your PI are always distinct, then you not will have skew.

Teradata Employee

Re: Database space issues

Load a sample of the data to ensure that your job is properly mapping the source field to the target PI. If it is loading nulls to the PI for instance, the job will be terribly skewed.

Teradata Employee

Re: Database space issues

Table DDL

CREATE MULTISET TABLE DEVA1_RSDS_HIST.T_CAPCISAU_CAPACCTD10ST ,NO FALLBACK ,

     NO BEFORE JOURNAL,

     NO AFTER JOURNAL,

     CHECKSUM = DEFAULT,

     DEFAULT MERGEBLOCKRATIO

     (

      REP DECIMAL(23,0) NOT NULL,

      REP_TY_ID INTEGER,

      PAN_REP_ID BIGINT)

PRIMARY INDEX ( REP );

In the above the first column will have distinct values and remaining columns have nulls for all rows

Enthusiast

Re: Database space issues

Hi,

Since , the PI has distinct values, then 1.change PI to UPI.

Then  , check from dbqlogtbl  , if during the same period were running(insert statements) other queries which were taking pernament space.If yes ,  

1)the one possibility is that some other jobs had really big skew ,, so you have to fix the PI.

2)if not , then the space that you have is not enough ,add space.

Before adding more space , try to check the skew of all tables on the target DB and then add if needed space.

Thanks.