SAP Knowledge Base Article - Preview

2849785 - Nameserver keeps crash while HANA starting up "invalid slot map update. allocate = false, m_address(L) = xxx, m_address(P) = xxx; $condition$=allocate != page->isOccupied"

Symptom

HANA can't startup due to nameserver keeps crash during startup, the crash stack similer to:

[CRASH_STACK] Stacktrace of crash
----> Pending exceptions (possible root cause) <----
--- Pending assertion:
exception 1: no.1000000 (RowEngine/Logging/Impl/RSUndoContext.cc:109) TID: xxxx
invalid slot map update. allocate = false, m_address(L) = xxx, m_address(P) = xxx; $condition$=allocate != page->isOccupied(page->getOffset(m_address))
exception throw location:
1: xxx in RowEngine::Logging::RSUndoContext::RSUndoActionBase::rollbackSlotMap()+0x11b at RSUndoContext.cc:105 (libhdbrskernel.so)
2: xxx in RowEngine::Logging::RSUndoContext::RSUndoSlotAction::applyUndo(RowEngine::RSContext&)+0x654 at RSUndoContext.cc:381 (libhdbrskernel.so)

In addition, you may found below error in nameserver trace:

nameserver_alert_<hostname>.trc
...
[xxxxxx]{xxxxxx}[xx/xxxxxx] <time_stamp> e Transaction transmgmt.cc(06724) : Redo-logging turned off

The result of LOGGING_ENABLED shown as FALSE:

select LOGGING_ENABLED from m_transacations;


isOccupied""> Read more...

Environment

  • SAP HANA database 1.0
  • SAP HANA database 2.0

Product

SAP HANA 1.0, platform edition ; SAP HANA, platform edition 2.0

Keywords

System logging, nameserver crash, redo-logging, can't startup , 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 for Me (Login required).

Search for additional results

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