Last updated on SEPTEMBER 14, 2016
Applies to:Oracle Internet Directory - Version 22.214.171.124.0 and later
Information in this document applies to any platform.
After creating a new OID instance (oid2) as per
<Document 1203271.1> - 11g - How To Create New OID Instance And Configure For SSL Server Auth (mode 2)
The server has a secondary or virtual IP address that resolves to a different hostname
192.0.2.10 physical.au.oracle.com physical
192.0.2.20 example.au.oracle.com example
the default orclhostname was changed from "localhost" to "example.au.oracle.com"
So these ports are now bound to that specific IP/hostname as can be seen with netstat, eg.
netstat -an|grep 3061
tcp 0 0 192.0.2.20:3061 0.0.0.0:* LISTEN
netstat -an | grep 3132
tcp 0 0 192.0.2.20:3132 0.0.0.0:* LISTEN
In Enterprise Manager Console (EM)
General Port usage screen: shows the correct values
Port Hostname Protocol
3132 example.au.oracle.com LDAPS
3061 example.au.oracle.com LDAP
Error on the EM OID Server Configuration Page for component oid2:
Note that it is still trying to connect to the original hostname, which is not listening on these ports.
Component oid2 was reregistered with:
opmnctl updatecomponentregistration -adminHost physical.au.oracle.com -Host example.au.oracle.com -adminPort 7001 -adminUsername weblogic -componentType OID -componentName oid2 -Port 3061 -Sport 3132
topology.xml and targets.xml now have the correct values for "host" for the oid2 component, but EM is still trying to connect to the original hostname.
By default OID will listen on all network adapters.
OID has been reconfigured to bind to a specific IP address.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms