SQL Developer Does Not Fetch LDAP Information Each Time For Oracle Database Connectivity
(Doc ID 2969699.1)
Last updated on AUGUST 23, 2023
Applies to:Oracle SQL Developer - Version 23.1 and later
Information in this document applies to any platform.
You have an LDAP server defined with Oracle TNS information.
You define SQL Developer database entries with Connection Type = LDAP, configure the LDAP Server, Context, DB Service, and it works fine.
However, if you update LDAP to specify a different host for a database, the subsequent access from SQL Developer tries to use the old information. That is, it does not access LDAP to get the latest information.
It appears you have to delete the database entry and define a new one to force SQL developer to obtain the current information from LDAP.
This is happening with multiple versions of SQL Developer.
How can you get SQL Developer to access the LDAP server for each connection request to get the latest information?
Step-by-step behavior description:
Here is what happens with a database connection definition using LDAP connect type:
- LDAP server points to host A for the database.
- Connect to the database (connects to it on host A).
- Update the LDAP server to point to host B for that database.
- Connect to the database.
At this point, SQL developer still connects to the database at the original host, host A, not using the updated LDAP entry which points to host B.
Is this working as designed, or is this a bug?
The idea of LDAP is that you do not need to be aware of where the database is, or what the host/port are.
You just know that LDAP is correct, and you expect SQL Developer to contact LDAP to always obtain the current host/port values for each connection request.
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