SAP Knowledge Base Article - Preview

2672505 - FM failed to run as heartbeat stopped due to multiple tempdb exists - SAP SRS

Symptom

  • Installing FM but it failed to run and got the following error

Status: ERROR
Additional Notes: ERROR - Fault Manager is not in a valid state. Check Fault Manager log file "/xxx/dev_sybdbfm" for detail.

Custom Action: com.sybase.ia.ase.CheckFMStatus
Status: FATAL ERROR
Additional Notes: FATAL ERROR - class com.sybase.ia.ase.CheckFMStatus FatalInstallException: fault manager running, pid = xxx, fault manager overall status = OK, currently executing in mode BOOTING
*** sanity check report (x)***.
node x: server XXX, site XXX.
db host status: UNKNOWN.
db status OK hadr status PRIMARY.
node x: server XXX, site XXX.
db host status: UNKNOWN.
db status OK hadr status STANDBY.
replication status: UNKNOWN.

  • The heartbeat process does not exist on both hosts.
  • We can see 2 tempdb used from the syb_sybdbfm level 3 trace. e.g.

SimpleFetch: select db_name(@@tempdbid)
SimpleFetch out: tempdbxx
....
SimpleFetch: select db_name(@@tempdbid)
SimpleFetch out: tempdbxx

Image/data in this KBA is from SAP internal systems, sample data, or demo systems. Any resemblance to real data is purely coincidental.


Read more...

Environment

  • SAP Adaptive Server Enterprise (ASE) 16.0 for Business Suite SP03 PL04

Product

SAP Adaptive Server Enterprise 16.0

Keywords

CR815693, CR#815693, 815693, FM, Fault Manager, , KBA , BC-SYB-REP-SAP , Replication with SAP Suite / SAP BW , Bug Filed

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.