Does it work with an ldap.ora ?
There was a change - the context specified in the ldap.ora is read - and displayed at the top of the context list.
I will check if there are unintended consequences. I will check it with no ldap.ora.
I`m can use a ldap.ora without installing the Oracle Client? Could you send me a link to step-by-step instuction?
goes in to some detail - SQLDeveloper reads:
from ldap.ora (for example from $TNS_ADMIN/ldap.ora or (Windows) %TNS_ADMIN%\ldap.ora )
You do not need Oracle Client or Instant Client. Thin jdbc driver as shipped with SQLDeveloper should be OK.
The new feature is to read the DEFAULT_ADMIN_CONTEXT line (without Oracle Client),
The new feature is for convenience, and if the ldap server is set up so the context is hard to search for
you can give SQLDeveloper the context (where to find the network database entries) manually through ldap.ora .
I am hoping the issue you saw was the default context being blank (access the other contexts through a pull down menu)
- I cannot remember explicitly testing the no ldap.ora case.
With no ldap.ora context list is empty.
With ldap.ora it`s work .
18.2 is the 'introduced in' version (The component version in the original bug was incorrectly set to originally to 4.1.3, I have updated it).