Customise Consent Preferences

We use cookies to help you navigate efficiently and perform certain functions. You will find detailed information about all cookies under each consent category below.

The cookies that are categorised as "Necessary" are stored on your browser as they are essential for enabling the basic functionalities of the site. ... 

Always Active

Necessary cookies are required to enable the basic features of this site, such as providing secure log-in or adjusting your consent preferences. These cookies do not store any personally identifiable data.

No cookies to display.

Functional cookies help perform certain functionalities like sharing the content of the website on social media platforms, collecting feedback, and other third-party features.

No cookies to display.

Analytical cookies are used to understand how visitors interact with the website. These cookies help provide information on metrics such as the number of visitors, bounce rate, traffic source, etc.

No cookies to display.

Performance cookies are used to understand and analyse the key performance indexes of the website which helps in delivering a better user experience for the visitors.

No cookies to display.

Advertisement cookies are used to provide visitors with customised advertisements based on the pages you visited previously and to analyse the effectiveness of the ad campaigns.

No cookies to display.

ORA-28040: No Matching Authentication Protocol.

Breadcrumb Abstract Shape
Breadcrumb Abstract Shape
Breadcrumb Abstract Shape
Breadcrumb Abstract Shape
Breadcrumb Abstract Shape
Breadcrumb Abstract Shape
  • User AvatarKiran Dalvi
  • 21 Dec, 2023
  • 0 Comments
  • 1 Min Read

ORA-28040: No Matching Authentication Protocol.

Solution :

This is because, the development is using old JDBC drivers, which are not compatible to Oracle 12c.

So We added the parameter SQLNET.ALLOWD_LOGON_VERSION_SERVER=8 in sqlnet.ora file under $ORACLE_HOME/rdbms/admin

For RAC system, add the parameter in sqlnet.ora file on all the nodes. And no need to restart the listener after changing sqlnet.ora.
Sometimes, parameter also need to be added in $GRID_HOME/network/admin/sqlnet.ora.

SQLNET.ALLOWED_LOGON_VERSION_SERVER=8

After adding the parameter, through JDBC connection to the database was successful.
So if you have legacy systems and facing this same, then adding this parameter will fix this issue.