Skip to Content
avatar image
Former Member

HANA Recovery not possible with HANA Studio

Hello,

For reasons unknown the index service crashed and since then our HANA instance is not available. (SAPControl is reachable!)

All servers/services are starting but the index server seems to run in an infinite loop trying to delete files from the garbage collection (Garbage collection of history files running: 0 cleanup files of 0 done). This is blocking the system since all other servers/services are waiting for the index server.

That's why I want to do a restore of the database, however I can't do it in the HANA Studio -> Recovery Wizard is stuck at 66% when trying to receive some version info. I only get the following error: "SAPControl request failed"

I also wanted to do a recovery using the command line. I wasn't able to find a command which tells the system to recovery the database using a certain backup file.

Is there any command to do this task?

In addition:

Can anyone tell me why the index service is stuck in the garbage collection?

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

1 Answer

  • Best Answer
    Sep 28, 2015 at 12:01 PM

    Hi Enzo,

    Yes, command line is an option and it's documented since SP09 if I'm not mistaken. Latest documentation is available here:

    http://help.sap.com/saphelp_hanaplatform/helpdata/en/8f/42dffd50b14a3da72f1220cc7b0eaf/content.htm

    Regarding the state of your recovery: you need to check the nameserver and indexserver traces (during the timeframe you're facing the issue) in order to reach an explanation why your recovery is getting stuck. If you can't interpret those, provide the info here.

    BRs,

    Lucas de Oliveira

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member

      PROBLEM SOLVED:

      After trying it a second time with a different timestamp (Backup Timestamp - 1 Minute) and the CLEAR LOG command it worked!


      HDBSettings.sh recoverSys.py --command="RECOVER DATABASE UNTIL TIMESTAMP '2015-09-21 15:13:00 CLEAR LOG'"