SAP Knowledge Base Article - Preview

3707817 - RECOVERY finished with error: [448] recovery could not be completed, volume <>, reached log position <>, [71000018] ptime::PtimeException ::::

Symptom

  • A HANA Tenant Recovery fails with error "[448] recovery could not be completed, volume <>, reached log position <>, [71000018] ptime::PtimeException"
  • The Backup catalog backup.log file shows that the full redo log has been replayed successfully to 100%, but still fails in error during the final phase  :

    2026-01-17T00:45:11-03:00  ............      19bca0e919c INFO    RECOVERY RECOVER DATA started [1768621511068]
    2026-01-17T00:45:11-03:00  ............      19bca0e919c INFO    RECOVERY command: RECOVER DATA FOR SID  USING FILE ('/hana/backup/bkp_c2/Backup File Name')  CLEAR LOG
    2026-01-17T00:45:11-03:00  ............      19bca0e919c INFO    RECOVERY using backup catalog 1767613675140 from /usr/sap/SID/HDB00/backup/log/DB_SID/log_backup_0_0_0_0.1767613675140
    2026-01-17T00:45:11-03:00  ............      19bca0e919c INFO    RECOVERY state of service: indexserver, Hostname:30040, volume: 0, RecoveryExecuteMetadataRecoveryInProgress


    2026-01-17T01:08:26-03:00  ............      19bca0e919c INFO    RECOVERY progress of service: indexserver, Hostname:30040, volume: 3, 96% 1917702897664/1985029865472
    2026-01-17T01:09:38-03:00  ............      19bca0e919c INFO    RECOVERY progress of service: indexserver, Hostname:30040, volume: 3, 100% 1985029865472/1985029865472
    2026-01-17T03:04:27-03:00  ............      19bca0e919c INFO    RECOVERY state of service: xsengine, Hostname:30043, volume: 2, RecoveryError
    2026-01-17T03:04:27-03:00  ............      19bca0e919c INFO    RECOVERY state of service: indexserver, Hostname:30040, volume: 3, RecoveryError
    2026-01-17T03:04:27-03:00  ............      19bca0e919c INFO    RECOVERY state of service: dpserver, Hostname:30046, volume: 4, RecoveryError
    2026-01-17T03:04:27-03:00  ............      19bca0e919c INFO    RECOVERY state of service: docstore, Hostname:30049, volume: 5, RecoveryError
    2026-01-17T03:04:27-03:00  ............      19bca0e919c ERROR   RECOVERY RECOVER DATA finished with error: [448] recovery could not be completed, volume <>, reached log position <>, [71000018] ptime::PtimeException

 

  • The Indexserver trace encounters these exceptions during recovery & startup and crashes shortly afterward :


    [82967]{-1}[-1/-1] 2026-01-17 04:25:58.991152 e Backup           BackupMgr_Manager.cpp(06901) : :::: RECOVERY finished with error: [448] recovery could not be completed, volume <>, reached log position <>, [71000018] ptime::PtimeException ::::

    [85086]{-1}[-1/-1] 2026-01-17 04:25:58.996109 e Backup           BackupMgr_Manager.cpp(01967) :    1: 0x00007f3f777bf540 in Backup::BackupMgr_Manager::handleRequest(Backup::BackupMgr_Request&, Backup::BackupMgr_Response&)+0x3ef at Backup/Manager/impl/BackupMgr_Manager.cpp:578 (libhdbbackup.so)
       2: 0x00007f3f777ba5f5 in Backup::BackupMgr_Manager::handleRequest(NameServer::Request&, NameServer::Response&)+0x44 at Backup/Manager/impl/BackupMgr_Manager.cpp:517 (libhdbbackup.so)
       3: 0x00007f3f778d5f15 in Backup::Backup_ManagerHandler::handleRequest(NameServer::Request&, NameServer::Response&)+0x24 at Backup/impl/Backup_ManagerHandler.cpp:36 (libhdbbackup.so)
       4: 0x00007f3f7779e470 in Backup::BackupMgr_ClientRequestHandler::handleRequest(TrexNet::Request&, TrexService::HandlerContext&)+0x8f at Backup/Manager/impl/BackupMgr_ClientRequestHandler.cpp:168 (libhdbbackup.so)
       5: 0x000055a68cee1160 in TimezoneComponent.cpp.02082f21+0x480 at TREXIndexServer2/TREXIndexServer.cpp:3129 (hdbindexserver)
       6: 0x00007f3f5cfce548 in TrexNet::Ext::WorkerThread::runImpl(TrexNet::Channel*, ltt::smartptr_handle<TrexService::Service>&, ltt::basic_string<char, ltt::char_traits<char>, 39ul>&, Synchronization::Mutex*, unsigned long&)+0x23c7 at TrexNet/Ext/WorkerThread.cpp:705 (libhdbbasement.so)
       7: 0x00007f3f5cfc3fb2 in TrexNet::Ext::RequestJob::run(Execution::Context&, Execution::JobObject&)+0xd1 at TrexNet/Ext/WorkerThread.cpp:206 (libhdbbasement.so)
       8: 0x00007f3f58832c94 in Execution::JobObjectImpl::run(Execution::JobWorker*)+0x14f3 at Basis/Execution/impl/JobExecutorRunJob.cpp:811 (libhdbbasis.so)
       9: 0x00007f3f588350cf in Execution::JobWorker::runJob(ltt::smartptr_handle<Execution::JobObjectForHandle>&)+0xafe at Basis/Execution/impl/JobExecutorThreads.cpp:360 (libhdbbasis.so)
      10: 0x00007f3f58836b68 in Execution::JobWorker::run(Execution::ThreadRC&)+0x767 at Basis/Execution/impl/JobExecutorThreads.cpp:1515 (libhdbbasis.so)
      11: 0x00007f3f58879d60 in Execution::Thread::staticMainImp(Execution::Thread*)+0x60f at Basis/Execution/impl/Thread.cpp:613 (libhdbbasis.so)
      12: 0x00007f3f5887a59e in Execution::pthreadFunctionWrapper(Execution::Thread*)+0x1cd at Basis/Execution/impl/ThreadInterposition.cpp:687 (libhdbbasis.so)
      13: 0x00007f3f578a6f6c in start_thread+0x2bd (libc.so.6)
      14: 0x00007f3f5792e388 in __clone3+0x29 (libc.so.6)
    exception type information:
     - 0: public ltt::exception@0x00007f3f580e1238
    [85086]{-1}[-1/-1] 2026-01-17 04:25:58.996557 e Backup           BackupMgr_Manager.cpp(06860) : Aborting recovery because of exception  1: no.110025  (Backup/Manager/impl/BackupMgr_Manager.cpp:1962) TID: 85086
        BackupExecutor: exception 71000018: ptime::PtimeException
     (1)
    exception throw location:
       0: 0x00007f3f777c7c94 in Backup::BackupMgr_Manager::reportDataRecovery(Backup::BackupMgr_Request&, Backup::BackupMgr_Response&)+0x543 at Backup/Manager/impl/BackupMgr_Manager.cpp:1962 (libhdbbackup.so)
       1: 0x00007f3f777bf540 in Backup::BackupMgr_Manager::handleRequest(Backup::BackupMgr_Request&, Backup::BackupMgr_Response&)+0x3ef at Backup/Manager/impl/BackupMgr_Manager.cpp:578 (libhdbbackup.so)
       2: 0x00007f3f777ba5f5 in Backup::BackupMgr_Manager::handleRequest(NameServer::Request&, NameServer::Response&)+0x44 at Backup/Manager/impl/BackupMgr_Manager.cpp:517 (libhdbbackup.so)
       3: 0x00007f3f778d5f15 in Backup::Backup_ManagerHandler::handleRequest(NameServer::Request&, NameServer::Response&)+0x24 at Backup/impl/Backup_ManagerHandler.cpp:36 (libhdbbackup.so)
       4: 0x00007f3f7779e470 in Backup::BackupMgr_ClientRequestHandler::handleRequest(TrexNet::Request&, TrexService::HandlerContext&)+0x8f at Backup/Manager/impl/BackupMgr_ClientRequestHandler.cpp:168 (libhdbbackup.so)
       5: 0x000055a68cee1160 in TimezoneComponent.cpp.02082f21+0x480 at TREXIndexServer2/TREXIndexServer.cpp:3129 (hdbindexserver)
       6: 0x00007f3f5cfce548 in TrexNet::Ext::WorkerThread::runImpl(TrexNet::Channel*, ltt::smartptr_handle<TrexService::Service>&, ltt::basic_string<char, ltt::char_traits<char>, 39ul>&, Synchronization::Mutex*, unsigned long&)+0x23c7 at TrexNet/Ext/WorkerThread.cpp:705 (libhdbbasement.so)
       7: 0x00007f3f5cfc3fb2 in TrexNet::Ext::RequestJob::run(Execution::Context&, Execution::JobObject&)+0xd1 at TrexNet/Ext/WorkerThread.cpp:206 (libhdbbasement.so)
       8: 0x00007f3f58832c94 in Execution::JobObjectImpl::run(Execution::JobWorker*)+0x14f3 at Basis/Execution/impl/JobExecutorRunJob.cpp:811 (libhdbbasis.so)
       9: 0x00007f3f588350cf in Execution::JobWorker::runJob(ltt::smartptr_handle<Execution::JobObjectForHandle>&)+0xafe at Basis/Execution/impl/JobExecutorThreads.cpp:360 (libhdbbasis.so)
      10: 0x00007f3f58836b68 in Execution::JobWorker::run(Execution::ThreadRC&)+0x767 at Basis/Execution/impl/JobExecutorThreads.cpp:1515 (libhdbbasis.so)
      11: 0x00007f3f58879d60 in Execution::Thread::staticMainImp(Execution::Thread*)+0x60f at Basis/Execution/impl/Thread.cpp:613 (libhdbbasis.so)
      12: 0x00007f3f5887a59e in Execution::pthreadFunctionWrapper(Execution::Thread*)+0x1cd at Basis/Execution/impl/ThreadInterposition.cpp:687 (libhdbbasis.so)
      13: 0x00007f3f578a6f6c in start_thread+0x2bd (libc.so.6)
      14: 0x00007f3f5792e388 in __clone3+0x29 (libc.so.6)


Read more...

Environment

SAP HANA Platform Edition 2.0

Product

SAP HANA, platform edition 2.0

Keywords

KBA , HAN-DB-BAC , SAP HANA Backup & Recovery , 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.