cancel
Showing results for 
Search instead for 
Did you mean: 

two different sizes for a table

Former Member
0 Kudos

Dear Experts,

When i estimate the size of the table "GLPCA" in our production system via SE38 using program "RSTABLESIZE", i got the output size 600+ GB. But when i check this table size (including indexes) in DB02, it was showing only 375 GB. Appreciate can any one let me know whats the problem here.

Output:-

RSTABLESIZE :-

0X.0X.20XX Test Program for Determining Table Sizes 1

State of Table Analysis: 0X.0X.20XX XX:XX:XX

Table: GLPCA

Compress Cluster:

Not Delivery Class L:

Not Delivery Class A:

Client: XXX 617,501,743.32 kByte

DB02:-

Object Type Tablespace KBytes

GLPCA TABLE SAPXXX 301,448,384

GLPCA~0 INDEX SAPXXX 16,081,664

GLPCA~1 INDEX SAPXXX 6,181,568

GLPCA~2 INDEX SAPXXX 10,474,944

GLPCA~Z1 INDEX SAPXXX 10,227,648

GLPCA~7 INDEX SAPXXX 18,435,072

GLPCA~3 INDEX SAPXXX 12,940,608

Total 375,789,888

Thanks & Regards,

Kalyan.

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

I had a look into the program RSTABLESIZE.

If i got it right then it calculates the size out of the number of records times the record length.

  P_SIZETAB-SIZE = P_SIZETAB-NBRINS * P_SIZETAB-TABLEN.
  P_SIZETAB-SIZE_KB = P_SIZETAB-SIZE / 1024.

While the number of record is retrieved by a select count(*) - but client depending!!! - the record length is taken from the abap dictionary. Obviously this can lead to very interesting results. I suggest you always use DB02 to get the real size of the table. The only thing you need to be aware of, is that lob segments are stored in dedicated segments and not in the table segment. But GLPCA does not have a lob column.

Cheers Michael

Edit: so in your case the table is "only" 375 GB and the report overdid slightly

Answers (1)

Answers (1)

former_member204746
Active Contributor
0 Kudos

DB02 has the reliable info.