SAP Knowledge Base Article - Preview

3382908 - Replication Synchronization via delta is not possible even though logshipping_max_retention_size is largely configured

Symptom

You get issues during Replication Synchronization. Below errors are observed in HANA trace: 

[xxxxx]{-1}[-1/-1] xxxx-xx-xx xx:xx:xx.xxxxx w sr_dataaccess    DisasterRecoveryProtocol.cpp(02237) : Synchronization via delta is not possible, reason: the secondary has probably been disconnected for a relatively long time, that the primary has reached the configured limit or disk space limit for log retention
[xxxxx]{-1}[-1/-1] xxxx-xx-xx xx:xx:xx.xxxxx w sr_dataaccess    DisasterRecoveryProtocol.cpp(02238) : Please check if enable_log_retention is set to 'off' on primary; or if logshipping_max_retention_size on primary is not big enough; or if Disk/Log volume is full on primary, for more information please check 'Log Retention' section in administration guide.

You have already increased logshipping_max_retention_size to (for example) 2TB for the affected service and set the value '2,097,152' (value in MB). 

However, the errors still occur as before.

"Image/data in this KBA is from SAP internal systems, sample data, or demo systems. Any resemblance to real data is purely coincidental."


Read more...

Environment

SAP HANA, platform edition 2.0

Product

SAP HANA, platform edition 2.0

Keywords

logshipping_max_retention_size, not big enough, enable_log_retention, Log Retention, delta, Synchronization  , KBA , HAN-DB-HA , SAP HANA High Availability (System Replication, DR, etc.) , How To

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.