2352487 - Indexserver failing to start due to missing log segment(s). | SAP Knowledge Base Article

SAP Knowledge Base Article - Preview

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

Symptom

Let's say for example, your system failed to start due to a log volume full situation.

To solve this issue you had to create a symbolic link and move some of log volumes to free up space so the system could start.

In the process of creating the symbolic link, you accidently deleted some log segments and now the indexserver server is crashing on start up with the crash stack:


----> Pending exceptions (possible root cause) <----
exception  1: no.1000000  (DataAccess/DataRecovery/impl/LogSegment.cpp:1848)
    Logfile /hana/log/<SID>/mnt00004/hdb00007/logsegment_000_<log_segment_number>.dat for segment LogSegment[0/14:0x48e05892c0-0x48e15892c0(0x40000000B)/GUID=27717399-38C0-20160619-073121-357000170A/PrevGUID=27717399-38C0-20160619-073121-3570001709,TS=2016-08-07 00:24:20.035511,Hole=0x48e05892c0/Truncated/0x0]@0x00007f3650afef00 not found
exception throw location:
 1: 0x00007f36ff7fb474 in DataRecovery::LogSegmentFactory::loadSegments(bool)+0x330 at LogSegment.cpp:1846 (libhdbdataaccess.so)
 2: 0x00007f36ff7caa70 in DataRecovery::DirectoryLogSegmentFactory::loadSegments(bool)+0x10 at DirectoryLogSegmentFactory.cpp:648 (libhdbdataaccess.so)
 3: 0x00007f36ff7dec63 in DataRecovery::LoggerImpl::addPartition(DataRecovery::LoggerPartitionInfo const&)+0x150 at LoggerImpl.cpp:1625 (libhdbdataaccess.so)
 4: 0x00007f36ff7df9c7 in DataRecovery::LoggerImpl::LoggerImpl(ltt::allocator&, DataRecovery::LoggerFactory const&, Diagnose::StatisticsData*, Configuration::ConfigurationHandler&, DataAccess::DuplicateTIDChecker&, DataAccess::Savepoint*, DataAccess::LogShippingHandler*, bool, bool, bool, bool, bool, ltt::guid const&, ltt::guid const&)+0x783 at LoggerImpl.cpp:681 (libhdbdataaccess.so)
 5: 0x00007f36ff7e053a in DataRecovery::LoggerFactory::createLogger(DataAccess::PersistenceManager&, bool, bool)+0x1c6 at LoggerImpl.cpp:2734 (libhdbdataaccess.so)
 6: 0x00007f36ff55a41e in DataAccess::PersistenceManagerImpl::createLogger(bool, bool)+0x6a at PersistenceManagerImpl.cpp:4347 (libhdbdataaccess.so)
 7: 0x00007f36ff56df80 in DataAccess::PersistenceManagerImpl::prepareRecoveryOrReplay(bool, bool)+0x50 at DiagTopic.hpp:321 (libhdbdataaccess.so)
 8: 0x00007f36ff56eca4 in DataAccess::PersistenceManager::prepareLogRecovery(DataAccess::LogRecoveryCallback&, bool, bool)+0x150 at PersistenceManagerImpl.cpp:2719 (libhdbdataaccess.so)
 9: 0x00007f36ff56f0c4 in DataAccess::PersistenceManagerImpl::replayOrClearLog(bool, bool)+0x40 at PersistenceManagerImpl.cpp:4666 (libhdbdataaccess.so)
10: 0x00007f36ff56f641 in DataAccess::PersistenceManager::replay()+0xa0 at PersistenceManagerImpl.cpp:2442 (libhdbdataaccess.so)
11: 0x00007f370ce08101 in PersistenceLayer::PersistenceSystem::start(NameServer::ServiceStartInfo const&, bool, bool)+0x700 at PersistenceSystem.cpp:470 (libhdbpersistence.so)
12: 0x00007f370ce43ad4 in PersistenceLayer::PersistenceFactory::startPersistence(NameServer::ServiceStartInfo&, bool, bool, DataAccess::TablePreloadWriteCallback*)+0xa0 at PersistenceFactory.cpp:466 (libhdbpersistence.so)
13: 0x00007f370cd2afab in PersistenceController::startup(PersistenceLayer::PERSISTENCE_MODE, NameServer::ServiceStartInfo*, bool, DataAccess::TablePreloadWriteCallback*, DataAccess::TablePreloadReadCallback*, Backup::RecoverCbc_Federation*)+0x1157 at PersistenceController.cpp:646 (libhdblogger.so)
14: 0x00007f371874f368 in TRexAPI::TREXIndexServer::assign(NameServer::ServiceStartInfo&, bool, TREX_ERROR::TRexError&)+0x2e4 at TREXIndexServer.cpp:1193 (hdbindexserver)
15: 0x00007f3718785ad5 in TRexAPI::AssignThread::run(void*)+0x31 at TREXIndexServer.cpp:542 (hdbindexserver)
16: 0x00007f370d62dff8 in TrexThreads::PoolThread::run()+0x8e4 at PoolThread.cpp:402 (libhdbbasement.so)
17: 0x00007f370d630600 in TrexThreads::PoolThread::run(void*&)+0x10 at PoolThread.cpp:175 (libhdbbasement.so)
18: 0x00007f36f4c07059 in Execution::Thread::staticMainImp(void**)+0x7e5 at Thread.cpp:467 (libhdbbasis.so)
19: 0x00007f36f4c07f2d in Execution::Thread::staticMain(void*)+0x39 at ThreadMain.cpp:26 (libhdbbasis.so)

Read more...

Environment

SAP HANA 1.0

Product

SAP HANA 1.0, platform edition

Keywords

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