SAP standard archiving -- impact to daily operations ?

[Former Member]

hi,

we have done SAP standard archiving procedure for some archiving objects from FI, CO, MM, WM and SD.

after we archiving, some enduser feels daily transaction become slower, where this transaction relates to the archiving object/ table that have been archived (mostly in FI transactions)

is there any relationship between transaction response time and the archiving process itself ?

note that we already reorganization (reorg) related table after we archive it.

thank you in advance.

rgds,

alfonsus guritno

[Former Member · Accepted solution]

Hi,

Did you rebuild the indexes from the tables from which there were the most deletion ?

Did you recalcultae the database statistics ?

In my experience, this has a very big impact on performance.

Regards,

Olivier

[Former Member]

we have checked, our info structure table created during archiving project is not consistent about its index. since we have re-transport the index, a significant increase have appear.

[Former Member]

Hi..

This may be happening when the retension period in all the archiving objects are not defined or not defined properly. we are using retension period of 18 or 27 months in all the archiving objects we are using and this has really nothing to do with the current data or the data of age less 18 months.

So, try to specify the retension period of 18 months in all the archiving objects and then do the archiving..Also this retension period depends on the size of the Enterprise data.

Just maintain the gap of 18 months or less than 18 months say 10 between the transaction data and the old data.

Archiving means improving the performance but lowering the performance.

Regards,

Shamim

[Former Member]

hi Olivier,

we have checked and monitored all you have mentioned above, and everything is fine.

is there any consideration that resulting performance decrease after archiving ?

rgds

alfonsus guritno

[Former Member]

Hi Alfonsus,

After archiving, index rebuild, database statistics updated we had a small performance increase.

Fortunately, because it was one of the project goal !

You have to check the slow transactions, analysing the response time with STAD and, maybe, take some SQL traces with ST05.

Regards,

Olivier

[former_member185954]

Hello,

If your database is not very big, meaning in Terabytes or so, performing a tablespace reorg would also help.

If its oracle i meant!

Regards,

Siddhesh