2525420 - Log needed on secondary persistence is missing on primary | SAP Knowledge Base Article

SAP Knowledge Base Article - Preview

2525420 - Log needed on secondary persistence is missing on primary

Symptom

The replication will get the following error when run the following command:

>python systemReplicationStatus.py
nameserver   | YES           | ASYNC       | ERROR       | Log needed on secondary persistence is missing on primary! Secondary is unable to sync with primary! |

indexserver   | YES           | ASYNC       | ACTIVE      |

indexserver   | YES           | ASYNC       | ACTIVE      | 

And also can find the following nameserver trace:
nameserver_alert_******.trc

[****]{-1}[-1/-1] year-month-day 00:00:00.00000 e sr_dataaccess DisasterRecoveryProtocol.cpp(04330) : Log needed on secondary persistence is missing on primary! Secondary is unable to sync with primary!. rc=3

[****]{-1}[-1/-1] year-month-day 00:00:00.00000 e sr_dataaccess DisasterRecoveryProtocol.cpp(01035) : V 1: HT_Sec (CT_Data): void DataAccess::ReplicationProtocolHandler::setError(const ltt::exception&),
pHandler=0x00007f49ff77c000, error=exception 3000335: Synchronisation of log after reconnect in 'full_sync' mode or with enabled 'continuous log replay' failed with rc: 3(DataAccess/impl/DisasterRecoveryProtocol.cpp:4331; 3000335)

Read more...

Environment

SAP HANA 1.0 database: Revisions <= 122.01

Product

SAP HANA 1.0, platform edition

Keywords

replication, persistence, enable_log_retention, missing, sync , KBA , HAN-DB-HA , SAP HANA High Availability (System Replication, etc.) , HAN-DB , SAP HANA Database , Problem

About this page

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

Search for additional results

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