3.1 is about 4 years old, but
In version 4.1
I created a user with password of AaBbCc
I'm able to connect with SQL Developer - no need to quote the password when entering it in the connection properties dialog.
right, upper and lowercase normally are no problem, as my second example shows.
What I wanted to say is, that there are no characters in username or password which SQL-Developer probably doesn´t accept.
I am searching for the reasons why I can´t login with the first account though all connection parameters are the same to the second one and I could check username and password in sqlplus.
Is there somethong other I could check?
username ist the right one- checked in sqlplus
password is the right one - checked in sqlplus
database is reachable from SQL-Developer - checked with second login
Just a wild guess, does your password contain characters which are multibyte in UTF-8 encoding? (German umlauts and "ß" which you might consider normal characters but encoded as two bytes in UTF-8).
I don't know how password hashing works in Oracle but entering the password in SQL*Plus using MsWin1252 or ISO-8859-15 may result in a different hash than SQL Developer produces when using UTF-8.
No there are no german Umlaute or something else.
The password is like this one for example: hiatpWftdbs9
To characters where I could see problems.
your sqlplus connect string doesn't show this, but is that account logging in AS SYSDBA?
no, there is even no SYSDBA login ......
grasping at straws, BUT
What if instead you did
When I try to connect to another schema on the same database it runs.
There is only another username and another password, compared to the first account which doesn´t work on SQL Developer.
The logical solution is to use sql*plus to connect to that account which gives you the error.and just change the password to something else.
Sometimes the BEST solution is the SIMPLE solution.