Skip to Content
-1

Indexserver in sap hana is not running

Hi,

I have a problem with indexserver, after run command HDB start indexserver is not running.

//from linux console ===================================================================

StartService

Impromptu CCC initialization by 'rscpCInit'.

See SAP note 1266393.

OK

OK

Starting instance using: /usr/sap/HDB/SYS/exe/hdb/sapcontrol -prot NI_HTTP -nr 02 -function StartWait 2700 2

26.02.2019 11:34:36

Start

OK

26.02.2019 11:34:46

StartWait FAIL: process hdbindexserver HDB Indexserver-HDB not running

//===================================================================================

in attachement is all log aboud this issue.

The hana base version: 2.00.020.00.1500920972 (fa/hana2sp02)

The OS : SLES 12

indexserver-sapnw75hana30203crashdump20190226-0245.txt

Thank you for any help.

Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

1 Answer

  • Posted on Feb 27, 2019 at 12:02 AM

    Given the I/O related errors in the trace file like

    "Wrong savepoint version: Expected 97854 but found 97851.;"

    and

    " RawRootKeyStoreReader::read: SSFS-4218: Record with key "HDB_SERVER/3/PERSISTENCE/VERSION" not found in secure storage <-- SSFS-4215: Data file "/usr/sap/HDB/SYS/global/hdb/security/ssfs/SSFS_HDB.DAT" exists, but does not contain the requested entry"

    and

    "ste::Exception type FileNotFound message /usr/sap/HDB/HDB02/sapnw75hana//attributes.ini additionalInfo file not found; $sysrc$=2; $sysmsg$=No such file or directory"

    and

    "ste::Exception type FileNotFound message /usr/sap/HDB/SYS/global/hdb/custom/config/attributes.ini additionalInfo file not found; $sysrc$=2; $sysmsg$=No such file or directory"

    my guess is that your file system storage has been damaged in some way.

    In fact, I would guess further that maybe this is the result of an incomplete recovery/flash copy on the storage server/filer level.

    Anyhow, the next steps probably should be:

    • check what backups are available and note down the recovery plan
    • have a support incident opened to verify the cause of the issue
    • talk to your storage folks and get an understanding of what their view is on that matter
    • check the trace files of the other services with persistence to see if they have similar error messages.

    Good luck with this one!

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.