JDBC Fails With ORA-01017 After Restoring Password, but SQL*Plus Works
(Doc ID 2907480.1)
Last updated on JUNE 28, 2024
Applies to:
JDBC - Version 19.13 and laterInformation in this document applies to any platform.
Goal
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?
Solution
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
Goal |
Solution |
References |