OracleAS 10.1.3 Instances On Separate Machines And Same Subnet Cannot See Each Other
(Doc ID 392498.1)
Last updated on JUNE 29, 2023
Applies to:Oracle Fusion Middleware - Version 10.1.3.0.0 to 10.1.3.5.1 [Release AS10gR3]
Information in this document applies to any platform.
Oracle Application Server 10g Enterprise Edition - Version: 10.1.3.0.0 to 10.1.3.4.0
Oracle Application Server (AS) 10.1.3 instances residing on two different machines are unable to 'see' or communicate with each other. For example, issuing the command line
shows only the processes from the local node.
Similarly the AS Control application only shows the components which are local to the Oracle AS instance on that machine.
Also it is only possible to deploy an application to the Oracle AS instance via the local Oracle Process monitoring and Notification (OPMN) command line or local AS Control. A remote deployment (e.g via JDeveloper) does not work.
It does not matter which OPMN communication method is configured - multicast, discovery server, node-to-node - all fail to work.
The two nodes are in the same subnet, there is no firewall.
If two instances are installed on the same machine the OPMN communication works fine and the '@cluster' shows processes from both instances.
The machine(s) hosting the OracleAS instances have more than one network interface (NIC) or IP address. It is possible that the problem can arise if the bind order of the network cards on the operating system is changed after installing the OracleAS instances.
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