Error when coming out of standby: hdbdaemon HDB Daemon not running

  • 7021376
  • 11-Sep-2017
  • 08-Nov-2017

Environment

SUSE Linux Enterprise Server for SAP Applications 11 Service Pack 3
SUSE Linux Enterprise Server for SAP Applications 11 Service Pack 4
SUSE Linux Enterprise Server for SAP Applications 12 Service Pack 1
SUSE Linux Enterprise Server for SAP Applications 12 Service Pack 2
SUSE Linux Enterprise Server for SAP Applications 12 Service Pack 3

Situation

After upgrading to some versions of SAP, a bug is introduced which causes an error when trying to bring a node out of standby.

Examples of the bug seen in messages or cluster logs:-

     <date+time> <node> SAPHana(<resource>)[11752]: ERROR: ACT: SAPHANA Instance <instance> start failed:  08.05.2017 09:58:12 WaitforStarted FAIL: process hdbdaemon HDB Daemon not running.

Also seen at the same time:

     <resource>  on <code> 'unknown error' (1): call=69, status=complete, exit-reason='none', last-rc-change='Mon May  8 09:57:52 2017', queued=0ms, exec=19762ms



Resolution

1: Ask SAP to provide a patch for the version of SAP software being used

2: Upgrade to a version of SAP where the problem is already fixed

3: Live with the inconvenience of the issue and manually re-start the SAP instance (after coming out of standby and the error is encountered, the slave node must be re-registered and any problem resources must be cleaned up).

The issue is known to be present in (at least) these 2 SAP versions:-

     1.00.111.00.1454183496
     1.00.112.00.1457525470


The issue appears to be fixed/not present in version:

    1.00.121.00.1466466057


It is assumed that any SAP software versions later than 1.00.121.00.1466466057 will also not suffer from the issue.



Cause

SAP introduced a bug which is triggered when the SAPHanaSR resource agent executes specific 'legal' SAP commands. This is not a SUSE OS or SUSE clustering issue, it is a bug in some versions of the SAP software.

Feedback service temporarily unavailable. For content questions or problems, please contact Support.