My Oracle Support Banner

JDBC Fails With ORA-01017 After Restoring Password, but SQL*Plus Works (Doc ID 2907480.1)

Last updated on NOVEMBER 10, 2022

Applies to:

JDBC - Version 19.13 and later
Information in this document applies to any platform.


The 'select spare4 from user$ where name='<VALUE>' ' query was used to retrieve the password of a user, and it was restored with 'alter user <USER> identified by values '<VALUE>' ';
After doing this, SQL*Plus connections with the user and password worked fine. However, JDBC connections with these credentials failed with error ORA-01017 Invalid Username/Password, and ended up locking the account.
Resetting the user with the actual password by using 'alter user <USER> identified by 'VALUE' ' resolved the issue, and the JDBC connections worked successfully.

Why is it required to execute 'alter user <USER> identified by "VALUE" in this case?


To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.