This content has been marked as final. Show 8 replies
- Did you specify a fixed username & password in the database link definition? Or are you connecting as the current user?
- Are you sure the username & password you're entering in SQL*Plus are the same as the username & password you specified in the database link?
- 11g passwords, by default, are case sensitive. Prior releases were not case sensitive. Any chance you specified the wrong case when creating the database link?
- Are you sure that the database link is connecting to the same database that you're testing via SQL*Plus?
refer to metalink Doc ID: 549067.1
Sub:- ORA-01017 ORA-02063 : Accessing 11G Database Via Database Link
Thanks I just found one more Metalink Note with workaround. Metalink Note: 473716.1
Looks like this 11g BUG after all.
According to this note it's not a bug,it works as expected in 11g.
Looks like this 11g BUG after all.Just to be clear, assuming the problem was case sensitive passwords, this is not a bug in Oracle. It is a change to the way Oracle validates passwords to increase security. The fix doesn't require patching the 11g database, it just requires creating the database link with the properly cased password.
Maybe. In past I always created DBLinks and specified password without double quotes and work around was to put double quote around password.
Pre 11g :
CREATE PUBLIC DATABASE LINK TEST11.WORLD
CONNECT TO DBLINK_USER
IDENTIFIED BY dblink_user
And after reading this article I have to changed IDENTIFIED BY "dblink_user"
Right. Because Oracle always stores unquoted identifiers (in this case the password) in upper case. In the past, it didn't matter because the destination database didn't care about the password's case. Now that the destination database does care about the case of the password (assuming a default 11g install), you can no longer get away with using case-insensitive passwords in your database link definitions. If you create database links to non-Oracle databases (where passwords are generally case sensitive), you've always had to specify the password in double-quotes.1 person found this helpful
This is an expected outgrowth of the move to enhance security in 11g by making passwords case sensitive.