3758597 - Recovery fails with 'recovery could not be completed, volume 2, reached log position 0' error

Symptom

During file-based tenant recovery, recovery got aborted with the following error.
backup.log
- 2026-03-02T22:38:26-08:00 P1662162 19cb26b5e68 INFO RECOVERY RECOVER DATA started [1772519906920]
  2026-03-02T22:38:26-08:00 P1662162 19cb26b5e68 INFO RECOVERY command: RECOVER DATA FOR ABC USING FILE ('/backup/abc/COMPLETE_DATA_BACKUP') CLEAR LOG
  ...........
  2026-03-02T22:54:09-08:00 P1662162 19cb26b5e68 INFO RECOVERY state of service: indexserver, saps4wnewdb:30003, volume: 2, RecoveryError
  2026-03-02T22:54:09-08:00 P1662162 19cb26b5e68 ERROR RECOVERY RECOVER DATA finished with error: [448] recovery could not be completed, volume 2, reached log position 0, [1000000] Assertion failed: m_hasBufferInTransit == false

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

Environment

SAP HANA, Platform Edition 2.0

Product

SAP HANA, platform edition 2.0

Keywords

HANA, recovery, recovery could not be completed, reached log position, assertion failed, m_hasBufferInTransit , KBA , HAN-DB-BAC , SAP HANA Backup & Recovery , 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.