Login  Register

DBlink errors

classic Classic list List threaded Threaded
3 messages Options Options
Embed post
Permalink
Reply | Threaded
Open this post in threaded view
| More
Print post
Permalink

DBlink errors

satish
1160 posts
Dear Erman,

Is it possible to create dblink from 11.1 version ro 12.2 oracle database?

We are facing error while testing connectivity

ORA-28040 No Matching Authentication Protocol

We came across this note id 12c and Later Releases: ORA-28040 After Upgrade: No Matching Authentication Protocol (Doc ID 1957995.1)

Do we need add below parameters in 11.1 database or 12.2 database?Please suggest

SQLNET.ALLOWED_LOGON_VERSION_SERVER=11
SQLNET.ALLOWED_LOGON_VERSION_CLIENT=11


Thank You
Reply | Threaded
Open this post in threaded view
| More
Print post
Permalink

Re: DBlink errors

satish
1160 posts
We have added these parameters in 12.2 database

When we tried to connect with dblink,we are facing below error but the password is correct

SQL> drop database link APPS_TO_UATNEW;

Database link dropped.

SQL> create database link APPS_TO_UATNEW connect to "system" identified by "pass" using '10.0.5.0:1521/CATSTG';

Database link created.

SQL> select sysdate from dual@APPS_TO_UATNEW;
select sysdate from dual@APPS_TO_UATNEW
                         *
ERROR at line 1:
ORA-01017: invalid username/password; logon denied
ORA-02063: preceding line from APPS_TO_UATNEW


Please suggest
Reply | Threaded
Open this post in threaded view
| More
Print post
Permalink

Re: DBlink errors

ErmanArslansOracleBlog
Administrator
5727 posts
This post was updated on Aug 03, 2020; 8:38pm.
First things first; check the compatability matrix -> Client / Server Interoperability Support Matrix for Different Oracle Versions (Doc ID 207303.1)
According to this note it is not supported.
Maybe you can find a workaround  using a trial and error approach. For instance by changing password-related db parameters in the 12.2 side.. (case sensitive logon and so on) But I say maybe.. Ofcouse, I don't recommend it.

In this kind of situation, you may use a intermediate db and make a workaround.

For instance :

11.1 ->(db link) 11.2 -> (db link) 12.2

However; I recommend a db upgrade for your 11.1 instance. It is already very old.