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

With the launch of Oracle 12C 18C 19C 20C, people begin to upgrade the core or non-core database to ensure the security and stability of the database. However, when using the old version of JDBC or Oracle client to access the database after the database upgrade, there will be the problem of unable to log in and ORA-28040 0RA-03134 error. This design of three parameters before 12C parameter ALLOWED_LOGON_VERSION and 12C start to use the new parameter ALLOWED_LOGON_VERSION_SERVER/ALLOWED_LOGON_VERSION_CLIENT this chapter our node to explain the reasons, we hope to be able to solve the problem!

JDBC of the lower version of the database (11G and below) or client access to the higher version of the database (12C and above) error messages

ORA-28040: No matching authentication protocol error

ORA-03134: Connections to this server version are no longer supported

Reason:

Let's introduce parameters first:

SQLNET.ALLOWED_LOGON_VERSION=9

This parameter is adjusted in the Oracle_HOME/network/admin/sqlnet.ora file under Oracle.

This parameter here means that version 9 and above will allow login. The above parameters allow 9i, 10g, and 11 versions to access the database. Version 8i fails when "ORA-28040: no matching authentication protocol".

If we choose SQLNET.ALLOWED_LOGON_VERSION = 10, it means that 10g and 11g versions are allowed to access the database. For ORA-28040, 9i and 8i versions will fail.

Instead of using the ALLOWED_LOGON_VERSION parameter in Oracle database 12c, there are two new Oracle Net service parameters:

SQLNET.ALLOWED_LOGON_VERSION_SERVER=n

SQLNET.ALLOWED_LOGON_VERSION_CLIENT=n

In version 12.1, the default setting for new parameters is 11. Any client trying to connect must be 11G or above, and unless these parameters are explicitly set in the server-side sqlnet, version 11 or later should be used.

In version 12.2, the default ALLOWED_LOGON_VERSION_SERVER setting for SQLNET was changed from 11 to 12 in 12.2. If your client does not exceed 11.2.0.3 or contains CPUOCT2012 patches, this is why we upgraded the database to 12C, which is why this problem occurs frequently.

Note: it is recommended that this parameter be adjusted to the minimum version of the current environment, such as 8 or 9.

Note: under the SQLNET.ORA file, ALLOWED_LOGON_VERSION_CLIENT is required on the server when the database acts as a client. For example, in the case of dblink. After this change, we do not need to restart the listener or database.

The details are as follows:

Https://docs.oracle.com/database/121/NETRF/sqlnet.htm#NETRF2010

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.