ORA-28040: No matching authentication protocol

Document created by Rabia_Sozkesen Employee on Sep 8, 2015Last modified by mike_aronson on Sep 23, 2016
Version 7Show Document
  • View in full screen mode

Error:

ORA-28040: No matching authentication protocol error is encountered on the database connector

 

 

Cause:

In 12.1, the default value for the SQLNET.ALLOWED_LOGON_VERSION parameter has been updated to 11. This means that database clients using pre-11g JDBC thin drivers cannot authenticate to 12.1 database servers unless theSQLNET.ALLOWED_LOGON_VERSION parameter is set to the old default of 8.  This will cause a 10.2.0.5 Oracle RAC database creation using DBCA to fail with the ORA-28040: No matching authentication protocol error in 12.1 Oracle ASM and Oracle Grid Infrastructure environments.

 

Solution:

Set SQLNET.ALLOWED_LOGON_VERSION=8 in the oracle/network/admin/sqlnet.ora file.

 

If this doesn't work, you can follow the below steps:

  1. Check this folder <atom_installation_folder>/userlib/database and confirm it is using the latest drivers needed for Oracle 12c connection. (http://stackoverflow.com/questions/24100117/ora-28040-no-matching-authentication-protocol-exception)
  2. If not, install the latest drivers, restart the atom and run one of the processes again to see if it is causing the same issue.  If userlib/database is not working, install the driver in the userlib/ folder instead.
  3. If it doesn't work add the userlib/database path to the Java endorsed.dirs variable and restart the atom. It would look something like this:
    -Djava.endorsed.dirs=/boomi/Boomi_AtomSphere/Atom/Atom_boomi_dev/userlib/database:/boomi/Boomi_AtomSphere/Atom/Atom_boomi_dev/endorsed
    This should be updated in the atom.vmoptions file. We need to identify the correct vmoptions file to be updated. Depending on how the Atom will be run depends on which atom.vmoptions file must be updated:
    For Atoms running as a service, update atom.vmoptions.
    For Atoms running on the desktop, update atomw.vmoptions.
  4. Restart the atom and rerun the process.

Please take a backup of every file that you change. In case something goes wrong you may have to revert back the changes.

2 people found this helpful

Attachments

    Outcomes