Reputation: 5028

ORA-01017 Invalid Username/Password when connecting to 11g database from 9i client

I'm trying to connect to a schema on 11g (v11.2.0.1.0) from a PC with 9i (v9.2.0.1) client. It seems to connect fine to some schemas, but not this one - it comes back with a ORA-01017 Invalid Username/Password error every time.

The username and password are DEFINITELY correct - can anyone think of a reason why this wouldn't work?

Are there any fundamental incompatibilities between 9i and 11g?

Upvotes: 76

Answers (21)

Anish kumar

Reputation: 21

I have faced similar issue.

ERROR

    auxiliary database Password:
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00554: initialization of internal recovery manager package failed
RMAN-04006: error from auxiliary database: ORA-01017: invalid username/password; logon denied

CAUSE:

The passwordfile became stale where sqlplus as sysdba connections worked but RMAN and other tools raised ORA-1017.

SOLUTION:

Recreate the target/auxiliary passwordfiles

% orapwd file=orapwSID1 password=<password> entries=10 force=y

Upvotes: 0

baklarz2048

Reputation: 10938

The user and password are DEFINITELY incorrect. Oracle 11g credentials are case sensitive, so try:

ALTER SYSTEM SET SEC_CASE_SENSITIVE_LOGON = FALSE;

and alter password.

http://oracle-base.com/articles/11g/case-sensitive-passwords-11gr1.php

Upvotes: 54

Iustin

Reputation: 80

If someone has this problem while trying to log as SYSDBA and using DataGrip, you just have to change the username from SYSDBA to sys as sysdba

Upvotes: 0

Hung Tran

Reputation: 21

Long time to answer, but I suggest to add

SQLNET.ALLOWED_LOGON_VERSION_SERVER=8

into sqlnet.ora

That will fix your issue.

Upvotes: 0

Usama Sarfraz

Reputation: 41

I face the same issue for connection in laravel 7 I face issue that my password is used in charater base when the password goes to the connect file is not go incomplete from .so I give the string password in my oci8.php file

Upvotes: 1

Yogi Arif Widodo

Reputation: 679

in my case with oracle database using tableplus build 373 on my m1 device type username and password in another text editor, copy and paste into username and password in tableplus. when i type in tableplus the text automatically changes to lowercase. because i had no problem with sqldeveloper, but when trying tableplus it always refused now i have solved it. i dunno why its problem on apps or other, but i have solved by the trick.

Upvotes: 0

Glen Little

Reputation: 7128

I had a similar issue. The id/pw I was using was correct, but I was getting ORA-01017 Invalid Username/Password on one particular connection only.

It turned out that my connection settings in Oracle SQL Developer had the "Use DB Proxy Authentication" turned on in the "Proxy User" tab. I didn't notice that for quite a while.

After I unchecked that option, it worked fine.

Upvotes: 2

Rama Krishna Chaganti

Reputation: 31

I also had the similar problem recently with Oracle 12c. It got resolved after I changed the version of the ojdbc jar used. Replaced ojdbc14 with ojdbc6 jar.

Upvotes: 1

vapcguy

Reputation: 7537

I know this post was about 11g, but a bug in the 12c client with how it encrypts passwords may be to blame for this error if you decide to use that one and you:

Don't have the password case-sensitivity issue (i.e. you tried ALTER SYSTEM SET SEC_CASE_SENSITIVE_LOGON = FALSE and resetting the password and still doesn't work),
Put quotes around your password in your connection string and it still doesn't help,
You've verified all of your environmental variables (ORACLE_HOME, PATH, TNS_ADMIN), and the TNS_ADMIN registry string at HKLM\Software\Oracle\KEY_OraClient12Home is in place,
You've verified your connection string and user name/password combination works in Net Manager, and
You can connect using SQL*Plus, Oracle SQL Developer using the same credentials.

All the basic checks.

Fix: Try setting HKLM\System\CurrentControlSet\Control\Lsa\FIPSAlgorithmPolicy\Enabled to 0 in the registry (regedit) to disable FIPS.

Oracle.ManagedDataAccess and ORA-01017: invalid username/password; logon denied

ORA-01005 error connecting with ODP.Net

https://community.oracle.com/thread/2557592?start=0&tstart=0

https://dba.stackexchange.com/questions/142085/ora-01017-invalid-username-passwordlogon-denied/142149#142149

Upvotes: 0

ram

Reputation: 2343

Oracle 11 G and 12 C versions suggest to use more complex passwords, Although there is no issues during the user creation. The password must be alphanumeric and with special character.

Verify the password version and status of the user:

select * from dba_users where username = <user_name>;

Amend it to be like below in case of 11G 12C:

alter user <user_name> identified by Pass2019$;

Now test connection!

Upvotes: 4

TheGabiRod

Reputation: 418

I had a similar issue some time ago. You must be careful with quotes and double quotes. It's recommended to reset the user password, using a admin credentials.

ALTER USER user_name IDENTIFIED BY new_password;

But don't use double quotes in both parameters.

Upvotes: 17

Jan Molnár

Reputation: 420

Credentials may be correct and something else wrong. I based my pluggable DB connection string on its container DB. Instead of the original parent.example.com service name the correct appeared to be pluggable.example.com.

Upvotes: 0

Jim H

Reputation: 106

I had a similar problem recently with Oracle 12c. I created a new user with a lower case password and was able to login fine from the database server but all clients failed with an ORA-01017. The fix turned out to be simple in the end (reset the password to upper case) but took a lot of frustrating effort to get there.

Upvotes: 0

ManishSingh

Reputation: 1156

for oracle version 12.2.x users cannot login using case insensitive passwords, even though SEC_CASE_SENSITIVE_LOGON = FALSE if PASSWORD_VERSIONS of user is not 10g.

following sql should show the PASSWORD_VERSIONS for a user.

select USERNAME,ACCOUNT_STATUS,PASSWORD_VERSIONS from dba_users;
USERNAME          ACCOUNT_STATUS    PASSWORD_VERSIONS 
---------------   --------------    -----------------
dummyuser         OPEN              11G 12C

to make PASSWORD_VERSIONS compatible with 10g

add/modify line in sqlnet.ora of database to have SQLNET.ALLOWED_LOGON_VERSION_SERVER=8 restart database change/expire password for existing user new users created will also have same settings after above steps PASSWORD_VERSIONS should be something like this

select USERNAME,ACCOUNT_STATUS,PASSWORD_VERSIONS from dba_users;
USERNAME          ACCOUNT_STATUS    PASSWORD_VERSIONS 
---------------   --------------    -----------------
dummyuser         OPEN              10G 11G 12C

Upvotes: 17

Andreas Covidiot

Reputation: 4755

I had the same error, but while I was connected and other previous statements in a script ran fine before! (So the connection was already open and some successful statements ran fine in auto-commit mode) The error was reproducable for some minutes. Then it had just disappeared. I don't know if somebody or some internal mechanism did some maintenance work or similar within this time - maybe.

Some more facts of my env:

11.2
connected as: sys as sysdba
operations involved ... reading from all_tables, all_views and granting select on them for another user

Upvotes: 4

Lay Leangsros

Reputation: 9296

You may connect to Oracle database using sqlplus:

sqlplus "/as sysdba"

Then create new users and assign privileges.

grant all privileges to dac;

Upvotes: 5

gautejohan

Reputation: 428

I also got the same sql error message when connecting through odp.net via a Proxy User.

My error was that my user was created with quotation marks (e.g. "rockerolf") and I then also had to specify my user in the connectionstring as User Id=\"rockerolf\"..

In the end I ended up deleting the user with the quotation marks and create a new one without..

face palm

Upvotes: 0

ridi

Reputation: 140

The tip on Oracle's OTN = Don't type your password in TOAD when you try to connect and let it popup a dialog box for your password. Type the password in there and it will work. Not sure what they've done in TOAD with passwords but that is a workaround. It has to do with case sensitive passwords in 11g. I think if you change the password to all upper case it will work with TOAD. https://community.oracle.com/thread/908022

Upvotes: 0

Shuaib Puthukudi

Reputation: 31

I am not an expert. If you are getting ORA-01017 while trying to connect HR schema from SQL Developer in Oracle 11g Please try to unlock the HR as follows

alter user HR identified by hr DEFAULT tablespace users temporary tablespace temp account unlock;

Upvotes: 3

Greg

Reputation: 31

I had the same issue and put double quotes around the username and password and it worked: create public database link "opps" identified by "opps" using 'TEST';

Upvotes: 3

lucrussell

Reputation: 5160

If all else fails, try resetting the password to the same thing. I encountered this error and was unable to work around it, but simply resetting the password to the same value resolved the problem.

Upvotes: 12

ORA-01017 Invalid Username/Password when connecting to 11g database from 9i client

Answers (21)

Related Questions