SAP Knowledge Base Article - Preview

2352487 - Indexserver failing to start due to missing log segment(s).

Symptom

  • You start SAP HANA and you get one of the following (or similar) error messages:

    • FAIL: process hdbdaemon HDB Daemon not running
    • FAIL: process hdbindexserver HDB Indexserver not running
    • FAIL: process hdbxsengine HDB XSEngine not running
  • You can find similar entries in SAP HANA service trace files as follows:

[122089]{-1}[-1/-1] 2020-03-01 20:31:28.446792 f PersistenceLayer PersistenceController.cpp(00723) : startup failed exception 1: no.2000004 (DataAccess/DataRecovery/impl/LogSegment.cpp:2278)
Cannot open file "<root>/logsegment_000_<log_segment_number>.dat", rc=$sysrc$: $sysmsg$; $[1]$=Logfile $file$ for segment $seg$ not found; $seg$=LogSegment[0/17:0x49914bdf80-0x49914bdf80(0x0B)/GUID=7e4e9a3b-e402-20200912-074700-04800001de/PrevGUID=7e4e9a3b-e402-20200912-074700-04800001db,TS=2020-09-12 11:07:00.345231,Hole=0x49914bdf80/Writing/0x0]@0x00007f46fea07000
exception throw location:
1: 0x00007f4867064107 in DataRecovery::LogSegmentFactory::loadSegments()+0x713 at LogSegment.cpp:2331 (libhdbdataaccess.so)
2: 0x00007f48670b0962 in DataRecovery::DirectoryLogSegmentFactory::loadSegments()+0x10 at DirectoryLogSegmentFactory.cpp:805 (libhdbdataaccess.so)
3: 0x00007f486709ad74 in DataRecovery::LoggerImpl::addPartition(DataRecovery::LoggerPartitionInfo const&)+0x1c10 at LoggerImpl.cpp:1864 (libhdbdataaccess.so)
4: 0x00007f48670a5f7f in DataRecovery::LoggerImpl::LoggerImpl(ltt::allocator&, DataRecovery::LoggerFactory const&, Diagnose::StatisticsData*, Configuration::ConfigurationHandler&, DataAccess::DuplicateTIDChecker&, DataAccess::Savepoint*, ltt::smartptr_handle<DataAccess::LogShippingHandler>, bool, bool, bool, bool, bool, bool, ltt::guid const&, ltt::guid const&)+0x10eb at LoggerImpl.cpp:571 (libhdbdataaccess.so)
5: 0x00007f486708ddbe in DataRecovery::LoggerFactory::createLogger(DataAccess::PersistenceManager&, bool, bool, bool)+0x21a at LoggerImpl.cpp:3900 (libhdbdataaccess.so)
6: 0x00007f4867313ebd in DataAccess::PersistenceManagerImpl::createLogger(bool, bool)+0x89 at PersistenceManagerImpl.cpp:2733 (libhdbdataaccess.so)
7: 0x00007f48673170a2 in DataAccess::PersistenceManagerImpl::prepareRecoveryOrReplay(bool, bool)+0x50 at PersistenceManagerImpl.cpp:2894 (libhdbdataaccess.so)
8: 0x00007f48673020d9 in DataAccess::PersistenceManagerImpl::prepareLogRecovery(DataAccess::LogRecoveryCallback&, bool, bool, unsigned long)+0xb5 at PersistenceManagerImpl.cpp:6797 (libhdbdataaccess.so)
9: 0x00007f48673164d9 in DataAccess::PersistenceManagerImpl::replayOrClearLog(bool, bool, bool, unsigned long&, unsigned long&)+0xe5 at PersistenceManagerImpl.cpp:3132 (libhdbdataaccess.so)
10: 0x00007f486730f00c in DataAccess::PersistenceManagerImpl::replayImpl(bool)+0x178 at PersistenceManagerImpl.cpp:4974 (libhdbdataaccess.so)
11: 0x00007f48696ecf9e in PersistenceLayer::PersistenceSystem::start(NameServer::ServiceStartInfo const&, bool, bool)+0xa8a at PersistenceSystem.cpp:566 (libhdbpersistence.so)
12: 0x00007f48696a6d7e in PersistenceLayer::PersistenceFactory::startPersistence(NameServer::ServiceStartInfo&, bool, bool, DataAccess::TablePreloadWriteCallback*, ltt::smartptr_handle<DataAccess::DisasterRecoveryPrimaryCallback>, DataAccess::DisasterRecoveryESCallback*)+0xba at PersistenceFactory.cpp:546 (libhdbpersistence.so)
13: 0x00007f4886aba6b9 in PersistenceController::startup(PersistenceLayer::PERSISTENCE_MODE, NameServer::ServiceStartInfo*, bool, DataAccess::TablePreloadWriteCallback*, DataAccess::TablePreloadReadCallback*, Backup::RecoverCbc_Federation*)+0x5d5 at PersistenceController.cpp:679 (libhdblogger.so)
14: 0x00005651b4300125 in TRexAPI::TREXIndexServer::assign(NameServer::ServiceStartInfo&, bool, TREX_ERROR::TRexError&)+0x7d1 at TREXIndexServer.cpp:1236 (hdbxsengine)
15: 0x00005651b43096c9 in TRexAPI::AssignThread::run(void*)+0x35 at TREXIndexServer.cpp:533 (hdbxsengine)
16: 0x00007f4868e7dd8b in TrexThreads::PoolThread::run()+0x787 at PoolThread.cpp:462 (libhdbbasement.so)
17: 0x00007f4868e80850 in TrexThreads::PoolThread::run(void*&)+0x10 at PoolThread.cpp:143 (libhdbbasement.so)
18: 0x00007f4863f154e8 in Execution::Thread::staticMainImp(Execution::Thread*)+0x534 at Thread.cpp:529 (libhdbbasis.so)
19: 0x00007f4863f04798 in Execution::pthreadFunctionWrapper(Execution::Thread*)+0x164 at ThreadInterposition.cpp:633 (libhdbbasis.so)
20: 0x00007f48636962de in start_thread+0xfa (libpthread.so.0)
21: 0x00007f4861e93a63 in __GI___clone+0x40 (libc.so.6)


Read more...

Environment

  • SAP HANA, platform edition 1.0 SPS09 and higher;
  • SAP HANA, platform edition 2.0;

Product

SAP HANA 1.0, platform edition

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 ONE Support launchpad (Login required).

Search for additional results

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