Advice on Reducing DHCDC_RTSTORE Table Size in S/4HANA

[SCN]

Good day everyone,

We are currently consuming SAP business content in our Datasphere environment, with data being replicated from our on-premise S/4HANA system via replication flows.

Today, my SAP Basis team informed me that the DHCDC_RTSTORE table in S/4HANA has significantly increased in size. They have asked if there's a way to clean up or reduce the space used by this table.

Does anyone have experience or suggestions on how to handle this?

Thank you in advance for your help

SAP Datasphere 

[Savio_Dmello · Accepted solution]

DHCDC_RTSTORE table in S/4HANA is primarily used to store data related to the real-time replication. While old data in this table can be deleted as part of cleanup activities if it is development environment, it’s essential to evaluate its relevance based on your needs. Please check with sap support team and if they suggest, work ABAPER or BASIS perform the deletion process.

Thanks

Savio

[n_gaertner · Accepted solution]

Hello,

this is a very dangerous advice.
Data should never be just deleted via SQL - this may lead to inconsistency and data loss.

[Savio_Dmello · Accepted solution]

@n_gaertner :  I have edited my response. However, in my earlier response, I had mentioned that OP has to evaluate his needs. It's up to the OP to do due diligence and decide. I understand that some options can be risky (not dangerous). When an initialization load is executed, if the load is completed successfully, the data from table DHCDC_RTSTORE gets deleted automatically. But if the load fails, the data gets stuck in DHCDC_RTSTORE and need manual intervention.  https://help.sap.com/doc/d6a3fa1bdb894bf39296d3306e73db45/1.0.04/en-US/SLT%20Performance%20Guide_Nov... .

Thanks for your understanding and suggestion. 

[n_gaertner · Accepted solution]

@Savio_Dmello
Thanks for editing the comment - appreciated.

The data of DHCDC_RTSTORE should always be deleted by the application - also in the case of failures - it is not necessary to manually delete data.
If data gets stuck its either a bug in the application or the replication was paused or disconnected from the source for some reason.
In this case there will be a cleanup performed after the defined retention time.
Hence, if the table is growing it is either a bug (-> support incident), or a misconfiguration of the retention.