2579728 - Fault Manager Installation reporting "ERROR - Fault Manager is not in a valid state" and "db host status: UNKNOWN" on log "FaultManager.log". | SAP Knowledge Base Article

SAP Knowledge Base Article - Preview

2579728 - Fault Manager Installation reporting "ERROR - Fault Manager is not in a valid state" and "db host status: UNKNOWN" on log "FaultManager.log".

Symptom

When installation Fault Manager on Unix environment the Fault Manager will report an error "ERROR - Fault Manager is not in a valid state" and "db host status: UNKNOWN" on log "FaultManager.log".

 FaultManager.log:

-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

                         Status: ERROR
                          Additional Notes: ERROR - Fault Manager is not in a valid state.  Check Fault Manager log file "/home/sybase/SAP1/FaultManager/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 is not responding, currently busy, retrying.
fault manager is not responding, currently busy, retrying.
fault manager is not responding, currently busy, retrying.
fault manager running, pid = 7740, fault manager overall status = OK, currently executing in mode BOOTING
*** sanity check report (51)***.
node 1: server ase16srv1, site SFHADR1.
db host status: UNKNOWN.
db status UNKNOWN hadr status PRIMARY.
node 2: server ase16srv2, site SJHADR2.
db host status: UNKNOWN.
db status UNKNOWN hadr status STANDBY.
replication status: UNKNOWN.

Where "/home/sybase/SAP1" is the $SYBASE variable.

Also from "dev_sybdbfm" log file will report:

2017 12/08 07:35:15.099 (26224) add instance status: failure.
2017 12/08 07:35:15.099 (26224) *** sanity check report (7)***.
2017 12/08 07:35:15.099 (26224) node 1: server ase16srv1, site SFHADR1.
2017 12/08 07:35:15.099 (26224) db host status: UNKNOWN.
2017 12/08 07:35:15.099 (26224) db status UNKNOWN hadr status PRIMARY.
2017 12/08 07:35:15.099 (26224) node 2: server ase16srv2, site SJHADR2.
2017 12/08 07:35:15.099 (26224) db host status: UNKNOWN.
2017 12/08 07:35:15.099 (26224) db status UNKNOWN hadr status STANDBY.
2017 12/08 07:35:15.099 (26224) replication status: UNKNOWN.
2017 12/08 07:35:15.099 (26224) insert status to fault manager status table.
2017 12/08 07:35:15.099 (26224) omitting insert into fault manager status table as db is not in status ok.
2017 12/08 07:35:15.099 (26224) omitting insert into fault manager status table as db is not in status ok.
2017 12/08 07:35:15.099 (26224) bootstrap failed.

-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------


Read more...

Environment

SAP ASE 16.0 SP02 PL<x>

SAP ASE 16.0 SP03 PL<x>

Product

SAP Adaptive Server Enterprise 16.0

Keywords

KBA , BC-SYB-ASE , Sybase ASE Database Platform (non Business Suite) , BC-DB-SYB , SAP Business Suite on Sybase ASE Database Platform , Problem

About this page

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

Search for additional results

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