Basilion Absent Member.
Absent Member.
55795 views

ORA-28040: No matching authentication protocol

Jump to solution

Hi!

 

After updating  datebase to version 12.1.0.2.2 RDBMS, stopped working job.
Error below:

  File "<string>", line 2, in ?
  File "SCRIPT_TEST", line 92, in DiscoveryMain

line 2: from java.util import Properties

ERROR class = "java.sql.SQLException">
<Message> [CDATA&colon; [Oracle] # 3 ORA-28040: No matching authentication protocol] </ message>
<Stacktrace>
<Frame class = "com.inet.ora.OraDriver" method = "a" file = "unknown" line = "- 1" />
<Frame class = "com.inet.ora.n" method = "a" file = "unknown" line = "- 1" />
<Frame class = "com.inet.ora.n" method = "long" file = "unknown" line = "- 1" />
<Frame class = "com.inet.ora.n" method = "& lt; init & gt;" file = "unknown" line = "- 1" />
<Frame class = "com.inet.ora.OraDriver" method = "connect" file = "unknown" line = "- 1" />
<Frame class = "com.hp.ucmdb.discovery.library.clients.protocols.sql.SqlUtil $ ConnectionThread" method = "run" file = "SqlUtil.java" line = "140" />
</ Stacktrace>
Version UCMDB 9.05
Version DDM Probe 9.05CUP14

Java: Version 7 Update 40
 
In the discovery job, there is a connection to the database, collect the necessary information and UCMDB created CI.
Connect using SQL Developer and perform the necessary inquiries with DDMProbe obtained.

0 Likes
1 Solution

Accepted Solutions
Basilion Absent Member.
Absent Member.

Re: ORA-28040: No matching authentication protocol

Jump to solution

Sorry for this post

 

Solution:

Bug 14575666

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.

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

View solution in original post

2 Replies
Basilion Absent Member.
Absent Member.

Re: ORA-28040: No matching authentication protocol

Jump to solution

Sorry for this post

 

Solution:

Bug 14575666

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.

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

View solution in original post

Absent Member.. scisystemsuppor Absent Member..
Absent Member..

Re: ORA-28040: No matching authentication protocol

Jump to solution

Hi, we are using 11.20 Sitescope Version and trying to configure alerts for 12.1.0.2 DB, receving the error:ORA-28040: No matching authentication protocol

 

0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.