AutoSys Job Management adapter for Oracle, release 3.0, may fail with exit code 220. 'ERROR: connection error: 28040' IS found in the debug logs. Error occurs after upgrade to Oracle 12.

Document ID:  TEC1897114
Last Modified Date:  04/15/2016
{{active ? 'Hide' : 'Show'}} Technical Document Details

Products

  • Unicenter Job Management for ERP Applications

Releases

  • Unicenter Job Management for ERP Applications:Release:3.0

Components

  • Unicenter AutoSys Adapter for Oracle:ATSYAO

Problem:

AutoSys Job Management adapter for Oracle, release 3.0, may fail with exit code 220.  'ERROR: connection error: 28040' is found in he debug logs.  Error occurs after upgrade to Oracle 12.   Debug log section will look like this:

JMAOA(6) adapter_getenv-> DEBUG: TNS_ADMIN(e)=/oracle/local/sqlnet/10.2.0

UJMAOA(7) adapter_getenv-> DEBUG: ADAPTER_PUTENV(d)=-1 

UJMAOA(8) dial_erp-> DEBUG: connect( apps/*****, prod147 ) 

olog status = 28040 

UJMAOA(9) dial_erp-> ERROR: connection error: 28040 

UJMAOA(10) adapter-> DEBUG: exiting with status 220 at Wed Apr 13 06:30:15 2016

 

Cause: 

The 28040 error from Oracle is this error: 

'ORA-28040: No matching authentication protocol'. 

 

What is happening is that OAP is trying to connect with an older Oracle connection protocol and Oracle will not accept it. 

 

Resolution:

To get around this the oracle server the following setting can be added to the sqlnet.ora file: 

SQLNET.ALLOWED_LOGON_VERSION=8 

SQLNET.ALLOWED_LOGON_VERSION_CLIENT=8 

SQLNET.ALLOWED_LOGON_VERSION_SERVER=8 

 

(depending on things only a subset of these settings may be needed.)

 

 

Please help us improve!

Will this information enable you to resolve your issue?

Please tell us what we can do better.

{{feedbackText.length ? feedbackText.length : '0'}}/255

{{status}}

Not what you were looking for?

Search Again >

Product Information

Support by Product >

Communities

Join a Community >