My Oracle Support Banner

ODI Agent Test Fails in FDMEE When FDMEE is Deployed on Windows Machine with Multiple Network Interface Cards (Doc ID 1586335.1)

Last updated on AUGUST 28, 2024

Applies to:

Hyperion Financial Data Quality Management, Enterprise Edition - Version 11.1.2.3.000 and later
Microsoft Windows x64 (64-bit)
Microsoft Windows (32-bit)

Symptoms

1. The ODI Agent that is automatically deployed to weblogic when installing and configuring FDMEE is showing as not started in Enterprise Manager and the ODI Agent test from the FDMEE web interface fails.
2. When trying to the ODI Agent in Enterprise Manager it the following error is seen:

Invoking Start Up operation for application oraclediagent on target EPMServer0.
[Deployer:149193]Operation 'start' on application 'oraclediagent' has failed on 'EPMServer0'
[Deployer:149034]An exception occurred for task [Deployer:149026]start application oraclediagent on EPMServer0.: [HTTP:101216]Servlet: "AgentServlet" failed to preload on startup in Web application: "oraclediagent".
com.tangosol.net.RequestTimeoutException: Timeout during service start: ServiceInfo(Id=0, Name=Cluster, Type=Cluster

3. An error like the below is seen in C:\Oracle\Middleware\user_projects\domains\EPMSystem\servers\ErpIntegrator0\logs\ErpIntegrator0.log (when web applications have been deployed to individual managed servers - log may differ if all applications have been deployed to a single managed server) where it can be seen that the 'Address=' parameter and the 'WKA list' (well known address) do not have corresponding IP addresses but the ports do match (e.g. below we have x.x.x.x & y.y.y.y as the IP addresses rather than two matching IP addresses):

This Member(Id=0, Timestamp=2013-09-17 12:27:40.508, Address=x.x.x.x:9088, MachineId=2451, Location=site:,machine:MachineName,process:1660, Role=WeblogicServer) has been attempting to join the cluster using WKA list [MachineName/y.y.y.y:9088] for 30 seconds without success; this could indicate a mis-configured WKA, or it may simply be the result of a busy cluster or active failover.

Cause

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
Symptoms
Cause
Solution
References


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