Shulou(Shulou.com)06/01 Report--

The test environment installed a set of 12cR2 databases and tried to connect to the database through PL/SQL developer, but reported an error

ORA-28040: No matching authentication protocol

Check the reason on the Internet: the parameter SQLNET.ALLOWED_LOGON_VERSION of Oracle 12c is 11 by default. When we use a thin driver connection prior to 11g JDBC, there will be an error.

So follow the online solution to do it:

Add a line SQLNET.ALLOWED_LOGON_VERSION=8 to the oracle/network/admin/sqlnet.ora file on the database server

Reconnect after modification but report an error ORA-01017: invalid username/password; logon denied

It's OK to confirm the user name and password, but you can't connect. You can connect on the server side.

[oracle@t13s] $sqlplus pdbadmin@pdb1SQL*Plus: Release 12.2.0.1.0 Production on Fri Mar 17 10:25:22 2017Copyright (c) 1982, 2016, Oracle. All rights reserved.Enter password: Last Successful login time: Thu Mar 16 2017 20:28:26 + 08:00Connected to:Oracle Database 12c Enterprise Edition Release 12.2.0.1.0-64bit ProductionPDBADMIN@pdb1 >

So search for relevant documents on MOS and find such an article Client / Server Interoperability Support Matrix for Different Oracle Versions (document ID 207303.1)

It can be seen from the article that only clients of version 11.2.0.3 and above can connect to the server of version 12.2. Check again that the local Oracle client version is 11.2.0.1. It turns out that the client version is too low. Install the 12.1 client and log in smoothly.

The general content of the MOS article is as follows:

Client

VersionServer Version12.2.0#1012.1.011.2.011.1.010.2.010.1.09.2.012.2.0YesYesYesNoNoNo#3No#312.1.0YesYesYesWasMDS # 7No#3No#311.2.0Yes#9YesYesWasMDS # 7NoWas # 511.1.0NoWasWasWasWas # 7Was # 6Was # 510.2.0NoMDS # 7MDS # 7Was # 7MDSWasWas # 510.1.0#4NoNoWas # 6Was # 6WasWasWas9.2.0NoNo#8Was # 5Was # 5Was # 5WasWas

Key:

YesSupportedESSupported but fixes only possible for customers with Extended Support .LES or MDSSupported but fixes only possible for customer with a valid Limited Extended Support or Market-Driven Support contract respectively.WasWas a supported combination but one of the releases is no longer covered by any of Premier Support, Primary Error Correct support, Extended Support, nor Extended Maintenance Support. Fixes are no longer possible.NoHas never been Supported

Specific Notes:

# 1-See Note:207319.1#2-An ORA-3134 error is incorrectly reported if a 10g client tries to connect to an 8.1.7.3 or lower server. See Note:3437884.8. 3-An ORA-3134 error is correctly reported when attempting to connect to this version.#4-There are problems connecting from a 10g client to 8i/9i where one is EBCDIC based. See Note:3564573.8#5-For connections between 10.2 (or higher) and 9.2 the 9.2 end MUST be at 9.2.0.4 or higher. Connections between 10.2 (or higher) and 9.2.0.1,9.2.0.2 or 9.2.0.3 have never been supported.#6-For connections between 11.1 (or higher) database server and 10.1 / 10.2 database server across a database link the 10g end MUST be at 10.1.0.5 / 10.2.0.2 (or higher) respectively in order to use PLSQL between those versions. (This does not apply to normal 11g clients to 10g database server only server to server and a few very specific client products, such as Oracle Forms). See Note:4511371.8 for more details.#7-For database link connections between 11.1 (or higher) and 10.2 the 10g end MUST be at 10.2.0.2 (or higher) in order to use PLSQL between those versions. See Note:4511371.8 for more details.#8-Attempting to connect from 9.2 to 12.1 will fail with an "ORA-28040: No matching authentication protocol" error.#9-11.2.0.3 or 11.2.0.4 only. We do not support any 11.2 client interoperability with Oracle Database Exadata Express Cloud Service#10-Includes Oracle Database Exadata Express Cloud Service-see Note:2183770.1 for additional details

General Notes:

For database links between different Oracle versions connections must be supported in BOTH directions in the matrix above.

Eg: As 11.2-> 10.1 is not supported then database links between these version are not supported in either direction.

Unsupported combinations may appear to work but can encounter errors for particular operations. The fact that they appear to work should not be relied upon-issues on unsupported combinations will not be investigated.

Since new database servers are compatible with a limited set of older OCI clients, it may not be necessary to upgrade the client software when upgrading the database. However, some new features may not work without upgrading the client software. For example, an Oracle 10.2 client is able to connect to an 11.2 database, but is not able to take advantage of newer features such as Client Result Cache (introduced in 11.1).

Oracle Applications, or other Oracle products, may have supported configurations not listed in the matrix above.

The matrix above also applies between different platforms and between 32/64 bit releases of Oracle client / server except where any Oracle platform desupport notice indicates otherwise.

Unix BEQUEATH (BEQ) connections are NOT supported between different releases. Eg: Client 10.2 is not supported to make an Oracle Net connection to a 11.2 server using the BEQ protocol adapter regardless of the interoperability support listed above. See Note:364252.1 for more details.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.