Symptom
- The following error messages appears in primary site traces.
[125562]{-1}[-1/-1] 2022-08-29 19:28:34.232272 e sr_dataaccess DisasterRecoveryProtocol.cpp(02188) : Missing logsegments unavailable on primary
[125562]{-1}[-1/-1] 2022-08-29 19:28:34.232280 e sr_dataaccess DisasterRecoveryProtocol.cpp(02197) : Replication is not able to proceed, 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
[125562]{-1}[-1/-1] 2022-08-29 19:28:34.232283 e sr_dataaccess DisasterRecoveryProtocol.cpp(02198) : Please check if enable_log_retention is set to 'off' on primary; or 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
[125562]{-1}[-1/-1] 2022-08-29 19:28:34.232287 e sr_dataaccess DisasterRecoveryProtocol.cpp(02200) : To resolve the situation, please execute 'hdbnsutil -sr_register ..' on the secondary to trigger a new full data shipping, for automatic resolution you could set [system_replication]/full_replica_on_failed_delta_sync_check=on in secondary
[125562]{-1}[-1/-1] 2022-08-29 19:28:34.232288 e sr_dataaccess DisasterRecoveryProtocol.cpp(02202) : If a secondary would be offline for a long time, remember to unregister the site
[125180]{-1}[-1/-1] 2022-08-29 19:29:04.249844 w sr_dataaccess DisasterRecoveryProtocol.cpp(03369) : Data compatibility check with primary failed, not compatible ..
- As the consequence, the replication session is closed and the secondary site got unregistered:
<timestamp> i sr_dataaccess DisasterRecoveryPrimaryImpl.cpp(02105) : Secondary with siteId=<id> got unregistered (might be due to takeover/finalize), remove its replication session
Read more...
Environment
- SAP HANA, platform edition 1.0
- SAP HANA, platform edition 2.0
Product
SAP S/4HANA foundation on SAP NetWeaver Application Server for ABAP, version for SAP HANA all versions
Keywords
full_replica_on_failed_delta_sync_check, got unregistered, , KBA , HAN-DB-HA , SAP HANA High Availability (System Replication, DR, etc.) , Problem
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.
SAP Knowledge Base Article - Preview