This affects the new release and most likely previous releases.
I have two connections that are nearly identical, the only difference is the hostname (both using “direct” tab). One entry uses the SCAN hostname the other uses a VIP hostname. BTW, the passwords happened to be different between these two entries.
Attempting to change the entry with the wrong password…
- Edit Login Record
- Enter the new password.
- Test (it works!)
- OK
- “There is already a record with that user/database. Update it?” YES
The other record gets the password update, not the one I was editing.
Additional info:
Thought that I should mention that all of my connections have a custom column “Group” that I use to group by DB tier (Prod/Dev/QA, etc.).
In the list of connections, the hostname appears as “XXX02DB01-VIP:1521/DBNAME”, but in the detail pane Host is “XXXXX-SCAN”. The refresh button does not resolve this inconsistency.
Solution:
Was able to get it to save properly by updating both the password and inconsistent host entry.