SAP Knowledge Base Article - Preview

2473521 - HANA Database recovery running long

Symptom

Every process until RecoveryExecuteDataRecoveryFinishedRecovery runs very fast, but then the recovery self takes 5 hours time for 4 TB, which took normally 1 hour before.

[142587]{-1}[12/-1] 2017-01-25 21:18:46.073540 e Authentication Provider.cpp(00110) : Kerberos: Error during initialization of GSS; Major: "Miscellaneous failure [851968]
", minor: " []"
[143592]{-1}[12/-1] 2017-01-25 21:21:53.012357 e MultiDB metadata_utils.cpp(00193) : isValidRemoteDatabaseLookup in non-multidb mode has databaseName X02

After that, the indexserver constantly complained about the following error:
[143507]{2000086}[20/-1] 2017-01-25 21:39:22.896496 e SessionContextCa SessionContext.cc(00638) : no connection on volume2: lcid=282, rvid=7 (retrieve local session context)


Read more...

Environment

SAP HANA DB 1.0

Product

SAP HANA 1.0, platform edition

Keywords

Process, RecoveryExecuteDataRecoveryFinishedRecovery, Recovery time, 4 TB, 1 hour, Kerberos, Error, GSS, Major, Miscellaneous failure, MultiDB, metadata_utils.cpp, isValidRemoteDatabaseLookup, non-multidb mode, databaseName X02, indexserver, error, SessionContextCa, SessionContext.cc, no connection, volume2, SAP HANA DB 1.0, Storage related issue, unmounted, remounted, storage , 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.