My company has recently moved our database servers (including LDAP server) to a remote data center. Now the main issue with SQL Nav is that it does not check whether the database connection is alive before attempting any actions on the database (running a query or exploring database objects) and it results frequent lock-ups and a need to kill sqlnavigator.exe using a task manager because it simply becomes unresponsive.
Second issue is that once SQL navigator has started you can connect to any of the databases, but 10-15 minutes later the connection to the LDAP nameserver drops and any attempt to reconnect to the same or a new database database results in
“ORA-12154: TNS:could not resolve the connect identifier specified”. The only way to connect to the database is by opening a new instance of SQL Nav.
Also as I reported before, SQL Nav still has no check for busy connection (a query running against the database), so any attempt to use DB explorer causes SQL Nav to lock-up.
So I wonder if the development team can make some kind of method to keep the database connection alive and also to fix the name service querying by correctly re-initializing the connection to LDAP before trying to query it.