Cleaning up of the System

[Former Member]

Hi ,

In one of our servers we are having a space constraint.So we are planning to do a cleanup.Below is the list which are occupying the most.Could anyone throw some light where we can delete the data and if yes how.Thanks.

Owner Object Type Tablespace KBytes Blocks Extents

SAPSR3 AGR_HIERT TABLE PSAPSR3 1.769.472 221.184 27

SAPSR3 ARFCSDATA TABLE PSAPSR3 3.866.624 483.328 171

SAPSR3 AGR_HIERT~0 INDEX PSAPSR3 1.507.328 188.416 23

SAPSR3 E071~1 INDEX PSAPSR3 1.769.472 221.184 27

SAPSR3 E071K TABLE PSAPSR3 1.769.472 221.184 27

SAPSR3 GLFUNCA TABLE PSAPSR3 1.376.256 172.032 21

SAPSR3 E071K~0 INDEX PSAPSR3 1.769.472 221.184 27

SAPSR3 E071K~ULI INDEX PSAPSR3 1.769.472 221.184 27

SAPSR3 MC13VD0ITMSETUP TABLE PSAPSR3 1.245.184 155.648 19

SAPSR3 MC13VD0KONSETUP TABLE PSAPSR3 1.572.864 196.608 24

SAPSR3 PCL2 TABLE PSAPSR3 4.063.232 507.904 62

SAPSR3 TBTCO TABLE PSAPSR3 1.769.472 221.184 195

SAPSR3 TBTCO~9 INDEX PSAPSR3 1.007.616 125.952 179

SAPSR3 TBTCP TABLE PSAPSR3 2.097.152 262.144 200

SAPSR3 DDNTF TABLE PSAPSR3 1.048.576 131.072 128

SAPSR3 TST01 TABLE PSAPSR3 1.245.184 155.648 187

SAPSR3 EDI40 TABLE PSAPSR3 1.245.184 155.648 131

SAPSR3 VARI TABLE PSAPSR3 3.216.384 402.048 162

SAPSR3 VARI~0 INDEX PSAPSR3 1.032.192 129.024 182

[Former Member · Accepted solution]

Hi,

Do you really intend to delete some tables and indexes ?

The only way safe way to reduce the growth of a SAP database is to use SAP archiving.

Regards,

Olivier

[Former Member · Accepted solution]

No intention of deleting the table.But the data in the table can be deleted.Could you please let me know as to how to delete the data in the table.Thanks.

[Former Member · Accepted solution]

>Could you please let me know as to how to delete the data in the table.

I already told you : you use SAP archiving.

Use help.sap.com and search for archiving.

Regards,

Olivier

[ashish_vikas · Accepted solution]

Hi Ambarish annapureddy ,

I think you have pasted DB02 screen..am i correct ?

Okk..you have just mentioned subject little confusing..

General procedure to recover space is :

1. Archiving : It deletes old data (which can be deleted from SAP after taking backup to archiving sol like ISOX) from tables.

2. Reorganization of tables & Index. Check for your fragmented tables and do it online. It will free some space.

3. Many times Index with poor quality also free some space after INDEX REBUILT. So you can definitelu look this option for all larger fragmented indexes. 

Let me know in case of any other queries.

thanks

ashish

[Former Member · Accepted solution]

Data archiving for which table should we be doing.Thanks.

[ashish_vikas · Accepted solution]

HI,

Search SAP Notes on archiving entries for these tables first (you will eaisly get them many):

ARFCSDATA

EDI40

Do Reorganization first :

TST01

TBTCO

Do Index rebuild for all of these table (for all Indexes)

thanks

ashish

[Former Member · Accepted solution]

>Data archiving for which table should we be doing

You are the only one supposed to know your own database.

For your information SAP data archiving is a major project and will take weeks to design and implement with a lot of work for the system team as well as for the functional team also.

Also, Data archiving will not decrease the size of your database until you do a database reorg.

Usually as I said before Data archiving is used to reduce the database growth and to keep good performance.

This is NOT a quick "step by step procedure for the same" that you apply by pressing a keyboard key without understanding what you are doing....

Regards,

Olivier

[Former Member · Accepted solution]

To add to what Oliver has`stated further data archiving is not directly at selective table level but rather at object or actually at data level and hence in order to ensure data integrity data has to be archived from several tables many of which maynot feature in your list. For instance your list mentions EDI40 which suggest idocs. So you set up archiving for idocs on the whole and not for EDID40 alone. Other tables like EDIDC would also get involved.

Further TBTCO tables can be reduced by running reorg jobs for background processes.

Also none of these tables is really huge so basically so actually this might a case for additional disk storage.

I mean PCL2 is just 4 GB!

Regards.

Ruchit.

[Former Member · Accepted solution]

>I mean PCL2 is just 4 GB!

In our system, we consider a table as big starting at 100 GB...

[Former Member · Accepted solution]

> In our system, we consider a table as big starting at 100 GB...

Completely agree. Infact I have seen PCL2 go upto 500 GB hence the example.

Regards.

Ruchit.

[JPReyes]

You don't delete data because you have space issues... you get more disk space!... Either by adding additional disks to your box or space from a SAN.

As mentioned by Olivier the most viable way to reduce the amount of data in the system is to do archiving... but then you are just moving the data to a content repository. Additional to that archiving is done mainly to increase system performance rather than saving space.

Hardware is cheap... my recomendation will be to get extra space.

Regards

Juan