- #No ip duc v3 0.4 download driver
- #No ip duc v3 0.4 download upgrade
- #No ip duc v3 0.4 download software
- #No ip duc v3 0.4 download password
The connections from 9i to 12c can be worked around by the solutions provided in this post. To set the minimum authentication protocol allowed for clients, and when a server is acting as a client, such as connecting over a database link, when connecting to Oracle Database instances. Same reason here for ORA-28040, it's a compatible issue: Purpose In sqlnet.ora to prevent unmatched authenticated protocol error ORA-28040.įor your reference, I quote some text about SQLNET.ALLOWED_LOGON_VERSION_CLIENT below. Scenario 2: New Database is Acting as a Clientįrom the opposite direction, if you want to connect from a 12.1 to a 9.2 database, say database link connections, you should also set: SQLNET.ALLOWED_LOGON_VERSION_CLIENT=8 Moreover, we can migrate data from 9i to 12c over a database link.įor some users who saw ORA-01017: invalid username/password logon denied need DBA's interventions. This time, our connections have no ORA-28040 shown up. And I have confirmed that.Īs for taking effect, you don't have to restart listener, the new incoming connections will apply the new values. Please note that, you should use sqlnet.ora at database-level, not grid-level if you're in a RAC environment according to MOS Doc ID 562589.1. ~]$ vi $ORACLE_HOME/network/admin/sqlnet.ora Here is my solution to ORA-28040: Adding SQLNET.ALLOWED_LOGON_VERSION_SERVER=8 to sqlnet.ora in 12.1 database server (not the old client). If the client version does not meet or exceed the value defined by this parameter, then authentication fails with an ORA-28040: No matching authentication protocol error or an ORA-03134: Connections to this server version are no longer supported error. The term VERSION in the parameter name refers to the version of the authentication protocol, not the Oracle Database release. To set the minimum authentication protocol allowed when connecting to Oracle Database instances. In which, it explains in what situation we should use SQLNET.ALLOWED_LOGON_VERSION_SERVER to be compatible with both ends of authentication protocol. ORA-28040 SQL*Plus Connect from 9i to 12cĪfter searching for some other solutions, I found an Oracle documentation about "Parameters for the sqlnet.ora File" is very helpful to explain ORA-28040. Scenario 1: New Database is Acting as a Server As a matter of fact, most developers do not have the right. If you have the right to change the network configuration on the server side, then you have chances to solve ORA-28040 for all users in minutes. As for developers, fixing or upgrading Oracle clients is the only choice you can do, so as to match authenticated protocol of Oracle 12c databases.įor better understanding different applicable situations, I will split the solutions against ORA-28040 into two main parts in this post, the first part is for server side, the other one is for client side.
For database administrators, you can change the server configuration to solve all users' problems at once. In fact, it depends on what privileges you have.
#No ip duc v3 0.4 download upgrade
But now the question is: Should we change server configuration or just upgrade Oracle clients? Server or Clients?Īccording to the above explanation about ORA-28040, we should provide compatible authentication protocol for either client or server to accept.
#No ip duc v3 0.4 download password
In this situation, that account's password must be reset, in order for the required verifier to be generated and allow authentication to proceed successfully.
#No ip duc v3 0.4 download software
This error ORA-28040 is also raised when the client is authenticating to a user account which was created without a verifier suitable for the client software version. The administrator should set the values of the SQLNET.ALLOWED_LOGON_VERSION_SERVER and SQLNET.ALLOWED_LOGON_VERSION_CLIENT parameters, on both the client and on the server, to values that match the minimum version software supported in the system. There was no acceptable authentication protocol for either client or server.
#No ip duc v3 0.4 download driver
I'll talk more about Oracle JDBC driver with ORA-28040 later in the post. Same error may occur while you're using old Oracle JDBC drivers, say ojdbc14.jar or below, to connect a 12c or 18c database. But I didn't expect ORA-28040 to show up.įor those users who want to use Oracle client 11g to connect to database 19c, but failed with ORA-28040, I'll talk about it in the last section. I knew there could be some interoperability problems between versions, especially when the version gap is big like this case, Oracle 9i client connect to 12c, 18c or 19c database. When I tried to connect to a 12.1 database from an Oracle client 9.2, it failed with ORA-28040: No matching authentication protocol. ORA-28040: No matching authentication protocol
0 kommentar(er)
