SAP Knowledge Base Article - Preview

3078958 - Indexserver slow startup because long recovery queue

Symptom

You observe the indexserver taking longer to restart after one of the following scenarios:

  • Ungraceful shutdown of an SAP HANA system
  • Removal of a system from SAP HANA System Replication

In the indexserver trace you can observe progressing entries similar to the following:

[73447]{-1}[-1/-1] 2021-07-19 13:07:59.204597 i Logger           RecoveryHandlerImpl.cpp(00735) : Redo done up to position: 0x236fb68f40 and time: 2021-07-19 09:59:55.934557-07:00 (47%)
[72452]{-1}[-1/-1] 2021-07-19 13:11:59.156403 i PITRestart       LogReplayCoordinator.cpp(00611) : Log Replay Coordinator (master, volume=3)
- lastReplayStepStartLogPos: 0x237296b5c9
Replay Step Information
- replayStepStatus: ReplayStep_Running
[75132]{-1}[-1/-1] 2021-07-19 13:12:05.014295 i Logger           RecoveryHandlerImpl.cpp(01790) : Triggering log recovery up to position 0x2372d6b5c9


Read more...

Environment

SAP HANA, platform edition

Product

SAP HANA, platform edition all versions

Keywords

KBA , HAN-DB-PER , SAP HANA Database Persistence , 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.