Table entries that can be deleted to release some space in SAP database

[Former Member]

Hi All,

In our R/3 database size has grown to 550 GB. Database is ORACLE 10g.No client is deleted nor any data is erased by the functional team.Our standard clean up jobs runs on a regular basis.Not too sure but there are some standard BASIS tables

whose data can be deleted to get some additional free space as they are not utilized.

I searched but couldn't get any OSS notes related to it.Any help or suggestion will be highly appreciated.

Regards,

PG

[Former Member]

If table logging has been activated then you could check for the size of DBTABLOG and if it is more then could delete.When you delete through sara please make sure that you do it on off peak hours since it would generate lot of redo logs and system load would be high.Thanks.

Other things like IDOCS archiving.

[Former Member]

Dear Ambarish,

If table logging has been activated then you could check for the size of DBTABLOG and if it is more then could delete.

How to check that and how to use SARA to delete the same..?

Other things like IDOCS archiving.

Could you please give an example or so?

Regards,

PG

[JPReyes]

You won't find a note because it doesn't exist...

Beside the standard jobs no other data is deleted as a standard practice.

Your database is going to increase on size overtime this is a fact and planning should be in place to accomodate DB growth.

Now, you could create a business case for Archiving but Archiving is not meant to be done to reduce the amount of space used but rather to improve performance.

If no clients or data has been deleted the chances of getting any mayor space recovery from reorganization are slim.

Regards

Juan

[Former Member]

Hi,

>but Archiving is not meant to be done to reduce the amount of space used but rather to improve performance.

You can at least, decrease the growth of your database which is a very interesting result.

We have a production R/3 4.7 system where the monthly data growth has been halved (from 120 GB to 60 GB) after implementing automatic scheduled archiving jobs.

We did not improve performance but kept it at the same level despite the huge database size increase which is a very good result.

Regards,

Olivier