My Oracle Support Banner

Exalogic Virtual: How To Change O2CB Timeout Value In OVM Manager 3.4.X To Default Value Of 300? (Doc ID 2752647.1)

Last updated on NOVEMBER 10, 2022

Applies to:

Oracle Exalogic Elastic Cloud Software - Version to
Oracle Exalogic Elastic Cloud Software - Version and later
Linux x86-64
Oracle Virtual Server x86-64
Exalogic Virtual Racks with versions (with OVMM 3.4.X)


In Exalogic Virtual racks the default Heartbeat dead threshold timeout value on Dom0 OVS Compute nodes is 151. This can be verified by running "service o2cb status" command (look for Heartbeat dead threshold value in command output). For default Heartbeat dead threshold value of 151, O2CB timeout value in OVM Manager 3.4.X should be 300. Below is formula

O2CB Timeout Value in OVMM = Heartbeat dead threshold x 2 (Network keepalive delay value) - 2 (Network reconnect delay)

So with default values of 151 for Heartbeat dead threshold, 2 seconds for Network keepalive delay and 2 seconds for Network reconnect delay, O2CB timeout value in OVMM will be 300

151 x 2 = 302
302 - 2 = 300 (O2CB timeout value in OVMM)

In Exalogic Virtual racks with & October 2020 PSU running with OVM Manager 3.4.X version, in some cases we may notice O2CB timeout value is set to different value than default value of 300. If there is mismatch in O2CB timeout values between Dom0 OVS Compute nodes and OVM Manager BUI console, rediscovering Dom0 Compute nodes in OVM Manager BUI console fails with below error.

This MOS Note provides detailed steps on how to change the O2CB timeout value in Exalogic Virtual racks with OVMM 3.4.X to default 300 (if it is configured with different value).


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

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.