My Oracle Support Banner

Mismatch Setup Within EDQ Login.properties (Doc ID 2459505.1)

Last updated on MARCH 20, 2019

Applies to:

Oracle Enterprise Data Quality - Version 12.2.1.2.0 and later
Information in this document applies to any platform.

Symptoms

Following errors are seen within LDAP and EDQ MainX.log files that dictate a log in error by user: 


LDAP Error 1 : LDAP response read timed out, timeout used:120000ms
       OEDQ Managed server showing STARTING state after LDAP setup and in managed server log file we can see below error
          edq_server1.out:oracle.ods.virtualization.engine.util.DirectoryException: LDAP Error 1 : LDAP response read timed out, timeout used:120000ms.
 
ERROR encountered in the edq_server1-diagnostic.log File


[2018-08-31T11:30:51.080+00:00] [edq_server1] [WARNING] [LIBOVD-40066] [oracle.ods.virtualization.engine.backend.jndi.ikea] [tid: [STANDBY].ExecuteThread: '39' for queue: 'weblogic.kernel.Default (self-tuning)'] 

[APP: edq] [partition-name: DOMAIN] [tenant-name: GLOBAL] Remote Server Failure:cds.XXXXX.com:389.[[
javax.naming.NamingException: LDAP response read timed out, timeout used:120000ms.; remaining name 'cn=usergroups,ou=Security,ou=Global,o=XXXXX.com'
at com.sun.jndi.ldap.Connection.readReply(Connection.java:490)

Changes

 

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
Changes
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.