This content has been marked as final. Show 6 replies
Any chance you are using a JDBC driver?
Try changing it to : ( Workaround )
OR = 9
This is an old bug if I remember correctly.
Added to mine, but I'm unable to recreate the error. Using Oracle 11 client.
Action: Administrator should set SQLNET_ALLOWED_LOGON_VERSION parameter
on both client and servers to values that matches the minimum
version supported in the system.
Edited by: mseberg on Feb 16, 2012 12:34 PM
Edited by: mseberg on Feb 16, 2012 12:36 PM
I'm confused to. The error implies that you are using a client that is 9i or below. What are you using to connect?
we are using JDBC 11g driver
That might be it then :
After Applying JDBC Driver Patch (6779501) , Problem still occurs (ORA-28040) [ID 1267169.1]
Cannot set up certs for trusted CAs Error When Using JDBC 11g And SQLNET.ALLOWED_LOGON_VERSION=10 [ID 1315314.1]
When using the property "SQLNET.ALLOWED_LOGON_VERSION=10" set in the file sqlnet.ora on the server side, and using a JDBC thin driver on the client side, the connection failed with ORA-28040: No matching authentication protocol.
it is ojdbc6-18.104.22.168.0.jar . Do we have to set the same entry in sqlnet.ora in the client side?
My thought based on the Oracle note I read is YES.
But the Java is getting out of my area so I'm not the best person to ask.
That said you have to test it anyway, so I start with that.
Note: 10,9,8,are 7 the only values allowed.