Saturday, 21 October 2017

Startup of SAP HANA Service With Persistence can Hang

Tags



Symptom:

                The SAP HANA database hangs during startup. In the traces of the SAP HANA service with a persistence that is hanging (e.g. index server or xsengine) you find repeatedly entries similar to:

[0000]{-1}[-1/-1] 0000-00-00 00:00:00.000000 w Service_Startup  Starter.cc : Version collection triggered times. but version(s) still remain(s). Please check if there is a blocker transaction

Reason and Prerequisites Reason:

Due to a programming error in the time synchronization, a deadlock can occur when a SAP HANA service starts up.

Affected Releases:

SAP HANA 2.0 database:
Revisions of SPS00
Revisions <= 012.01 (SPS01)

Prerequisites:

During startup of a service of the SAP HANA database row store versions are present. This especially can happen if SAP HANA service is not terminated gracefully or if a takeover is performed.
These row store versions are being garbage collected.


Solution :
Apply one of the following SAP HANA database Revisions:

SAP HANA 2.0 database:
Revisions >= 012.02 (SPS01)
or higher

Workaround:

To resolve the deadlock you can restart the master indexserver of the affected SAP HANA database. For details how to stop and start a service with SAP HANA Studio please refer to the section "Stop and Start a Database Service" in the SAP HANA Administration Guide.

More Details refer Snote : 2528893

1 comments so far

This comment has been removed by a blog administrator.


EmoticonEmoticon

Note: only a member of this blog may post a comment.