[resolved] Trunjob ORA-28040: No matching authentication protocol

[Anonymous]

Actually my database is Oracle 12, and at this moment no problem running any job. Below the problem with only one job.
The basic run  is not running, error java.sql.SQLException: ORA-28040: No matching authentication protocol
It's strange ...because if I run the job "ExtractTelnet" alone  or alone using Trunjob it doesn't show this problem.

My job only run in java debug mode and don't show no more problems about jdbc or ORA-28040. I tried to delete the talend cache arquive and then alter the XML from toracle connection and toracle input the problem still occurring

[ChaitraCP]

Hi,

Even I am facing same issue in TEST TAC.

We are using route and pooling the file. From there We are extracting the data and inserting it into Oracle DB table.

While running Locally( From Studio) its working fine and data inserted into table. But after we deployed the code into TEST TAC, I'm facing below issue. Could you please help me on this. Thank you.

 

Also, I have tried to run the job from studio with TEST (UAT) context and its working fine.

[Anonymous]

Hello @Chaitra Prakash​ 

Could you please indicate on which talend TAC version you got this issue? And what's your database?

We met this issue on TAC 6.1.1, after upgrading DB to oracle 12 an error appears on TAC in the configuration page:

 Cannot connect to database(ORA 28040: no matching authentification protocol) 

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.

Here is a solution:

SQLNET.ALLOWED_LOGON_VERSION_SERVER=8

SQLNET.ALLOWED_LOGON_VERSION_CLIENT=8

Best regards

Sabrina

[ChaitraCP]

Hello @Xiaodi Shi​ ,

Please find the details.

TAC Version: 6.3.1.20161216_1026-

Database : Oracle (19c) Recently we have updated it from 12c to 19c.

Host : H_TALEND_DDL_REC

Service_name : ROM19EX_CLI

Port : 1521

Its ESB Route. Please find the attached screenshot of route.

 

[Anonymous]

Hello,

Does this issue only repro on TAC side? Did you update JDK version as well when you updating oracle DB from 12 to 19?

Which ojdbc.jar file are you using in TAC? ojdbc8.jar or ojdbc14.jar?

Best regards

Sabrina

[ChaitraCP]

Hi Sabrina,

• Yes. This issue happening only after we deployed the route into TEST TAC. (Another server)
• DB Admin upgraded the oracle. When checked with him he said like "Your client version is old. You must need to upgrade it into 12c or 19c". (How to upgrade it)
• We are using ojdbc7.jar. With this version the job running fine in studio without any issues.

Kindly help me on this.

1. In TAC, where I have to check which version of ojdbc.jar I'm using?
2. Also in studio, for particular job where I have to check which jar I'm using?

Thanks & Regards,

Chaitra CP

[Anonymous]

Hello,

In TAC, You will get the jar version from here

<TomcatInstallationPath>\webapps\org.talend.administrator\WEB-INF\lib.

The ojdbc7.jar is OK with your older version when creating DB connection to oracle 12c DB.

We have added support for Oracle 19c since talend V 7.3.1.

Is there any possible for you to upgrade your studio and TAC version? Talend V 6.3.1 is a quite old version.

Best regards

Sabrina

[ChaitraCP]

Hi Sabrina,

Thank you. We are planning the upgrade by end of this year.

Thanks & Regards,

Chaitra CP

[Anonymous]

Hello,

Feel free to let us know if there is any further help we can give.

Best regards

Sabrina