DOA 4.x cannot handle "complex" usernames

[Greg Stevenson]

In DOA 3.x, I can log into a DB that has a username like "Firstname.LastName@MyCompany.com".

However in 4.x, this now results in a "ORA-12154: TNS:could not resolve the connect identifier specified." error. Same results in recent PL/SQL Developer versions vs. older version.

Looking at LogIn source nothing jumps out as a change that would cause it to fail now where it succeeded before. Any suggestions? I would hate to go back to 3.x, but we have customers that have such usernames and our latest version of software (with DOA 4.1) will not work for them.

--Greg

 

[Marco Kalter]

This works fine for me. How exactly do you specify the username, password and database?

 

[Greg Stevenson]

as Firstname.LastName@MyCompany.com
with no quotes. This works fine in 3.x.
In 4.x I have found that the above will work if surrounded in double quotes but that a simple username like "MyUsername" will not work if it has double quotes. What's the rule for passing a username to Oracle. Do I have to first scan the name and surround it in double quotes if it has an "@" in it? If so, what other special cases do I need to handle?