ORA-28040: No matching authentication protocol after 12c upgrade

[Former Member]

Dear Friends,

i have upgraded oracle version ( 11.2.0.4 )of solution manager 7.1 SP14 system  to 12c successfully.

ABAP started but java was unable to start due to JDBC issue.

i got error log in bootstrap folder

ORA-28040: No matching authentication protocol.

JDBC version is ojdbc14.jar ( java_class_archive.jar )

ABAP and Java worked before upgrade with 12x client.

after 12c only java had issue.

kindly suggest us.

Regards,

hari

[fidel_vales · Accepted solution]

Hi,

have you set SQLNET.ALLOWED_LOGON_VERSION in the sql_net.ora? it is not normal to set it in SAP environment but check it on ethe DB server.

check note 1718415 and 1714490

[Former Member · Accepted solution]

Hai Friends,

Thanks a lot to Fidel vales and Fabian.

Note 1714490 is useful note for this issue.

java issue resolved by add parameter SQLNET.ALLOWED_LOGON_VERSION_SERVER=8

in sqlnet.ora in both areas ( network/admin ,profile/oracle )

by seeing note 1859713,i have added value to 10 earlier itself. but its java not started.

Thanks a lot once again..

Regards,

hari

[fschoen · Accepted solution]

HI Fidel

A side question related to the issue of JDBC and 12c

ojdbc14.jar is for version 10.2 if I'm not wrong. Should not be a newer driver used when upgraded to 12c?

To set SQLNET.ALLOWED_LOGON_VERSION_xxx is for me more a workaround if older drivers are used.

Or is this the only supported driver version for the installed Solution Manager version?

thanks

fabian

[fidel_vales · Accepted solution]

Hi,

Here is where a lot of "confusion" arises.

There is a difference between the jdbc driver "delivered" with an oracle RDBMS version, the jdbc that can "connect" to a RDBMS version and the jdbc "supported by SAP"

A lot of people thinks that if the RDBMS is updated then the SAP jdbc must be changed, and that does not have to be like that. (with this I mean the driver "name")

AFAIK, the jdbc releases follow the "same support" as the main RDBMS versions.and it is true that the ojdbc14.jar is a bit old, but that is the one that the SAP J2EE is using so, unless there is a note that tells you to change it to other one (like ojdbc6.jar) don't do it.

Neither the Oracle instantclient 11.2.0.4 nor the 12.1.0.2 have the ojdbc14.jar, therefore you must have the mentioned parameter until there is a note indicating that it can be changed.

Last information I had was from the FAQ 867176, where indicates that SAP J2EE applications release 7.00 run jdbc driver ojdbc14.jar.

But on the note 915079 it is mentioned that

As of Version 7.20, the J2EE engine uses only the driver file ojdbc6.jar. You do not require other auxiliary files.

so, it would be possible to use such driver from the 12c instantclient and not to have the parameter (I think, better test it just in case as I cannot do it).

[stefan_koehler · Accepted solution]

Hi Fidel,

There is a difference between the jdbc driver "delivered" with an oracle RDBMS version, the jdbc that can "connect" to a RDBMS version and the jdbc "supported by SAP"
...
Neither the Oracle instantclient 11.2.0.4 nor the 12.1.0.2 have the ojdbc14.jar ...

... ohh, if it would be just that. SAP builds its "own" Oracle client based on the instant client and specific JDBC files, but does not document the exact version and bug fixes of the included (old) JDBC files. So the SAP/Oracle client could be something like "V1" in the readme file, but you have no clue which JDBC fixes are deployed or not. The jdbc.version program is also no solution as it just shows the main version up to the 4th digit. I struggled several times with such things as you have no idea which bug fix is included or not.

Luckily the guys at Oracle development were able to figure out, but it is a rough time until you get up to this point.

Regards

Stefan

[fidel_vales · Accepted solution]

Hi,

Sometimes the "answer" is so easy we even "we" do not realize.

In the SAP upgrade manual page 29 it is stated:

3. When upgrading an SAP 7.0X system with AS Java or dual-stack (ABAP+Java), add the parameter SQLNET.ALLOWED_LOGON_VERSION_SERVER = 8 to SQLNET.ora (independent of the Oracle database software owner) in directory <ORACLE_HOME>/network/admin and in the directory $TNS_ADMIN.
Without the entry in SQLNET.ora, the following error occurs:
ORA-28040: No Matching authentication

so clearly we have not read the manual in detail

[fidel_vales · Accepted solution]

Hi,

first I have to clarify what I said about the instantclient; the instantclient 11g and 12c delivered by SAP has older versions of the jdbc. As mentioned by you, it is "modified" by SAP.
The instantclient 12c and 11g delivered by SAP has a file called SAPIC_README with version and patches installed.

I cannot say about the 10g

Of course, if other jdbc is used, I have no clue how to check what patches are installed on it.

Thank good, it is a long time I do not get involved seriously in jdbc issues

[former_member214380 · Accepted solution]

Just wanted to say: THANK YOU! That saved my evening. Setting the parameter made it possible for the Java-System to connect and start up.

[fschoen]

Hi Hari

Did you also update the JDBC driver on the application server side?

Did you upgrade the client and the database to 12c?

We had the same issue on a Non-SAP installation and the reason was just, that the JDBC driver was outdated.

regards

fabian

[fschoen]

Hi

Just found a note

867176 - FAQ: Oracle JDBC

3. Which JDBC driver version is certified to connect to which database version?
              From the Oracle side: 
              The Oracle 10g and 11g JDBC drivers are certified to work with currently-supported versions of the database. 
              JDBC 8i/9i Thin drivers are certified to work with supported (previous) versions of the database. 
              JDBC drivers >= 9.2. 0 are certified to work with Oracle Database 10g 10g and 11g. 
              From the SAP side: 
              SAP only supports homogeneus setups. The oracle driver major version must match the database major version, and the driver version must not be smaller than the database version. 

This note is from 2011. So maybe it is quite outdated, but at least a starting point.

[Former Member]

Hai Fabian,

Thanks for your reply.

As mentioned initial message,i had updated 12x client before upgrade.ABAP and Java was running after updated 12x client.

Now the issue after 12c only.log mentioned issue with JDBC only.

Regards,

hari