ODI Agent Fails To Start When Configuring Coherence Cluster For HA
(Doc ID 1355995.1)
Last updated on FEBRUARY 11, 2019
Applies to:Oracle WebLogic Server - Version 10.3.5 to 10.3.5
Oracle Coherence - Version 3.6.0 to 3.6.0 [Release AS10g]
Oracle Data Integrator - Version 184.108.40.206.0 to 220.127.116.11.0 [Release 11gR1]
Information in this document applies to any platform.
Is important to mention that there is no separate installation needed for setting up on Coherence cloud for ODI Agent.
During the installation and configuration steps for setting up an Oracle Data Integrator high availability configuration (see https://download.oracle.com/docs/cd/E14571_01/core.1111/e10106/odi.htm#BGBEIAFE), Coherence needs to be configured to enable communication among the cluster members (see https://download.oracle.com/docs/cd/E14571_01/core.1111/e10106/odi.htm#sthref864).
The prerequisite for deploying the ODI agent on Weblogic Server cluster is to make sure that all the Managed servers in the cluster are configured to use the same Coherence cloud.
This is a straight forward procedure. Nevertheless, the customer may get into situations where the ODI Agent fails to start. You can verify this by visiting the Administrator Console and checking the oraclediagent deployment:
Also logs files from Managed Servers may provide valuable information, e.g.:
com.tangosol.net.RequestTimeoutException: Timeout during service start: ServiceInfo(Id=0, Name=Cluster, Type=Cluster
These symptoms are usually noticed when the environment is being installed.
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