Unable to log in as new created user in Oracle 11g

Question

I recently made a new tablespace and associated a user with it (sonar).

Currently, a copy and paste of the user profile looks like this:

Name    SONAR
Profile DEFAULT
Authentication  Password
Default Tablespace  SONAR
Temporary Tablespace    TEMP
Status  UNLOCK
Default Consumer Group  None


Role    Admin Option    Default
CONNECT N   Y
DBA N   Y
RESOURCE    N   Y


System Privilege    Admin Option
CREATE SESSION  N
UNLIMITED TABLESPACE    N

I can log in to the OEM console with this new user but am unable to connect to the sonar tablespace with that user. I know the connection properties I'm using are valid because I can connect with other users and view their tablespaces.

So, does anyone have an idea what I might be missing that is preventing me from connecting with this user and using their default tablespace? If I need to provide any more information, let me know. I'm not very experienced with DBA stuff.

Thank you.

Answer 1

Just a note that I had a similar issue with Oracle 19c and the problem turned out to be that the username consisted of lower case letters. I had to change it to upper case and then it would work.

• I had created a user called "pm_bool" with SQL Developer and could not log in with it through SQL Developer or SQLplus.
• Then I created the user as "PM_BOOL" with SQL Developer. After that both ways of logging in worked fine.

Answer 2

Since you're getting an "ORA-01017: invalid username/ password" error, there are only a handful of possibilities

1. The password specified in SQL Developer is wrong.
2. The username specified in SQL Developer is wrong.
3. The password you're typing is correct but the tool is passing the wrong password to the database. When 11g made passwords case-sensitive by default, many tools hiccuped because they hadn't been preserving the casing in the passwords that were stored. I have no recollection of any version of SQL Developer being affected by this problem but if you have an old version, it's probably worth upgrading to the newly released 3.0 version anyway.
4. The database you are connecting to is not the database where you created the Sonar user. If you can connect as other users using the same connection information, can you query DBA_USERS and verify that you see the Sonar user?