OVM 3.4.x : Server Pool Cluster timeout reverts to default 120 seconds after rebuilding OVM DB
(Doc ID 2302814.1)
Last updated on FEBRUARY 20, 2019
Applies to:Oracle VM - Version 3.4.1 and later
Oracle Cloud Infrastructure - Version N/A and later
Oracle VM manager DB rebuild referring to KM "2038168.1" won't restore the OCFS2 cluster timeout value on Oracle VM manager UI and it will revert back to default 120 seconds on Oracle VM Manager UI.
Rebuilding the Oracle VM manager DB referring to KM "2038168.1" might be required at some stage to fix the DB inconsistency, post to that activity it will revert the OCFS2 cluster timeout value to default 120 second on UI, by skipping the custom value available on the OVS server. i.e /etc/sysconfig/o2cb (O2CB_HEARTBEAT_THRESHOLD=N)
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document