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. 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. 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. 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. ORA-28040: No matching authentication protocol
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.
0 kommentar(er)
