Earlier versions use dblink to connect to 11G versions reports error ora-02063/ora-01017, dblinkora-02063

Earlier versions use dblink to connect to 11G versions reports error ora-02063/ora-01017, dblinkora-02063

A home, a carrier called to create dblink error ora-02063/ora-01017

This BUG was not encountered once. ORACLE described the BUG as follows:

Bug 6738104: ORA-01017 ORA-02063 while connecting FROM10G TO 11G VIA PUBLIC DBLINK
 
Cause
The following Bug 6738104 was logged for this issue which was closed as not abug saying the cause being introduction of password case sensitivity feature in11g
When one creates a database link connection, a user name and password for theconnection needs to be defined. when the database link is created, the passwordis case sensitive. before a user can connect from a pre-release 11g database toa 11g release database and as the password case sensitivity is enabled bydefault, you must re-create the password for this database link using alluppercase letters.
The reason you need to re-create the password using all uppercase letters is sothat it will match how Oracle Database stores database link passwords. oracleDatabase always stores this type of password in uppercase letters, even if thepassword had originally been created using lower or mixed case letters. if casesensitivity is disabled, the user can enter the password using the case thepassword was created in.

When the earlier version uses dblink to connect to the 11G library, the password is changed to uppercase by default.

Solution is easy. re-create dblink and use double quotation marks and lowercase letters for the password.

Example: create database link db_test
2 connect to wxboss
3 identified by "wxboss"
4 using '(DESCRIPTION =
5 (ADDRESS_LIST =
6 (ADDRESS = (PROTOCOL = TCP) (HOST = 192.168.99.100) (PORT = 1521 ))
7)
8 (CONNECT_DATA =
9 (SERVER = DEDICATED)
10 (SID = wxboss)
11)
12 )';

It is hereby recorded.