Symptom
- Fault Manager (FM) fails to boot when it is restarted
- After new FM profile parameters are added to the profile file (.PFL), for example:
ha/syb/waittime_if_unresponsive = 150
ha/syb/failover_if_unresponsive =1
- In the stat_sybdbfm file:
SYBDBFM_STATUS: 15079 ERR BOOTING
SYBDBFM_SANITY_STATUS_BEGIN:
*** sanity check report (1334)***.
node 1: server host1.corp.xxx.pvt, site HAP.
db host status: UNKNOWN.
db status UNKNOWN hadr status PRIMARY.
node 2: server host2.corp.xxx.pvt, site HAC.
db host status: UNKNOWN.
db status UNKNOWN hadr status STANDBY.
replication status: UNKNOWN.
VIPA status: ERROR.
failover prerequisites fulfilled: NO.
SYBDBFM_SANITY_STATUS_END
- The dev_sybdbfm log shows the following error:
Error: NIECONN_REFUSED (Connection refused), NiRawConnect failed in plugin_fopen()
call is running.
call exited (exit code 32).
execution of saphostctrl failed (31, 1).
- Restarting the Host Agent does not help.
- The same error is reported again after the newly added FM profile parameters are removed from the .PFL file.
Read more...
Environment
- SAP Adaptive Server Enterprise (ASE) 16.0
- HADR
Product
Keywords
sapstartsrv, SHA, SRS, FM , KBA , BC-SYB-ASE , Sybase ASE Database Platform (non Business Suite) , How To
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.