cancel
Showing results for 
Search instead for 
Did you mean: 

SAP Hana not starting after upgrade (localsecurestore not starting up)

Vero_Levin
Discoverer
0 Kudos
133

Hi,

After an upgrade of our HANA from 2.00.081 to 2.00.083 the HANA does not start up correctly. When running HDB start I can clearly see that all components are starting up and are working fine except localsecurestore. I not able to access the database using HANA studio, the startup process never finishes. The main error I encounter at the daemon log file are:

Daemon.cpp(00756) : Found terminated and planned instance 0 of program 'localsecurestore'

Jose_Paniagua_cr_0-1745668510575.png

This line is always popping up every 30 seconds in the logs as seen above.

I have found another post with this issue, but no solution was posted.

Anyone has an idea of how to solve this?

I have opened a case with sap but have not got an answer yet.

Any help would really be appreciated.

Regards,

View Entire Topic
Chuma
Active Participant
0 Kudos

Hi,

It looks like the localsecurestore service failure is what’s blocking your full HANA startup after the upgrade.

This usually happens because of one of these issues:

  • Corrupted secure store (SSFS) files.

  • Wrong file permissions on the secure store.

  • Disk space issues on the server.

Here’s what you can do

  1. Check the SSFS files under $(DIR_GLOBAL)/hdb/security/ssfs/.

    • Confirm that SSFS_HDB.DAT and SSFS_HDB.KEY are present.

    • Check that they are owned by the <sid>adm user and have correct permissions (typically 600).

  2. Check disk space:

    • Use df -h to make sure your /usr/sap/ and related file systems have free space.

  3. Check traces for more clues:

    • Look at daemon_trace, nameserver_trace, and indexserver_trace files.

  4. If files are corrupted:

    • You might need to restore the SSFS files from a backup if you have one.

    • If not, SAP Support will likely need to assist you to recreate or recover it safely.

Since you already raised an SAP case, keep it open. if it's a deeper SSFS corruption or version-specific issue with 2.00.083, they may also provide a patch or fix note