About Tom

Hi  pcpg,   Apologies for the confusion created.  The EFM behaviour will be same on all the operating systems (Supported platforms).   Please if you could provide following details to have a clear understanding :   1. Were the EFM configurations kept same in both the test cases i.e on Suse and RHEL environments ? 2. Was the chkconfig set for starting the database on both servers ? To be more specific, on Suse server was the database started once the server was up and running and on RHEL the database did not start ?   There might be a possibility of below scenario :     On RHEL (where the failover happened) after reboot of the server the database was not in running state, whereas on Suse (where failover did not happen) after reboot the database must be up and running.     ... View more

Hi  Tom,   The document correction for the earlier updates cannot be determined exactly.  However, EFM 3.2 has been released and has build of SLES.   Refer document : https://www.enterprisedb.com/docs/en/3.2/edbfm/toc.html   Hope this helps. ... View more

Hi  Tom,   There are specific parameters which need to be enabled for EFM using VIP namely : virtualIp virtualIp.interface virtualIp.prefix     The documentation point number 3.5 has the details covered in brief for setting EFM using VIP : https://www.enterprisedb.com/docs/en/3.1/edbfm/EDB_Failover_Manager_Guide.1.13.html#pID0E0N50HA   The steps and details mentioned here are correct unlike the supported platforms details.   For, 1. Configure new network inteface (eg., eth1) and assign VIP to eth1 (or) 2. With existing inteface (eth0) in which public IP has assigned with.   Both the approches are valid you can go ahead with whichever is feasible for you.   Hope this helps.   ... View more