SAP Knowledge Base Article - Preview

3547860 - Calculation of system replication take over time

Symptom

During system replication takeover, the significant replayed log volume and time is recorded in HANA log like below, even if the takeover finished within a short timeframe.

indexserver_<host>.<port>.<num>.trc:
[25487]{-1}[14/-1] 2024-06-22 17:47:05.570427 i PersistenceManag DisasterRecoverySecondaryImpl.cpp(01348) : Prepare takeover started (operationMode=logreplay; replicationStatus=ReplicationStatus_Error) ..
[25487]{-1}[14/-1] 2024-06-22 17:47:05.570440 i PersistenceManag DisasterRecoverySecondaryImpl.cpp(01370) : Takeover: invalidating connections
[25487]{-1}[14/-1] 2024-06-22 17:47:05.570550 i PersistenceManag PersistenceManagerSPI.cpp(01176) : Notify RedoHandler listener about new state: 0
[25487]{-1}[14/-1] 2024-06-22 17:47:05.570559 i CSARedo          RedoMerge.cpp(02947) : Cancel ongoing merges that are not ready to be committed
[25487]{-1}[14/-1] 2024-06-22 17:47:05.570564 i PersistenceManag PersistenceManagerSPI.cpp(01196) : Notification of RedoHandler listener finished
[25487]{-1}[14/-1] 2024-06-22 17:47:05.570566 i PersistenceManag DisasterRecoverySecondaryImpl.cpp(01404) : Takeover: aborting data shipping if running
[25487]{-1}[14/-1] 2024-06-22 17:47:05.570568 i PersistenceManag DisasterRecoverySecondaryImpl.cpp(01411) : Takeover: table preload synchronized
[25487]{-1}[14/-1] 2024-06-22 17:47:05.570570 i PersistenceManag DisasterRecoverySecondaryImpl.cpp(01435) : Takeover: disabling primary functionality temporarily
[25487]{-1}[14/-1] 2024-06-22 17:47:06.696318 i PersistenceManag DisasterRecoverySecondaryImpl.cpp(01473) : Prepare takeover finished
......
[25487]{-1}[14/-1] 2024-06-22 17:47:06.709350 i Logger           RecoveryHandlerImpl.cpp(01972) : Recovery finished at log position 0x1a77643b980
[25487]{-1}[14/-1] 2024-06-22 17:47:06.709385 i PITRestart       LogReplayCoordinator.cpp(00148) : recoveryFinished(): vid=2, pos=0x1a77643b980, reason=0x0
......
[25487]{-1}[14/-1] 2024-06-22 17:47:06.711794 i Logger           LogSegment.cpp(00773) : Closing open log segments after log recovery completed at position 0x1a77643b980
[25487]{-1}[14/-1] 2024-06-22 17:47:06.713078 i Logger           LoggerImpl.cpp(01435) : Replayed 2720887696064B (2594840MB) of log in 2.66065e+06 seconds; 0.975262MB/s; max known TID=15178253480

* 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 1.0
  • SAP HANA Platform Edition 2.0

Product

SAP NetWeaver 7.5

Keywords

take over, log replay, log recovery, start, start up, long time. , 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.