Skip to main content
  • EN

I just upgraded form Oracle 2017.1 to Oracle 2018 and now I'm having issues with Oracle database connections.

I get this 'ORA-12638: Credential retrieval failed' error which is solved by changing SQLNET.AUTHENTICATION_SERVICES= (NTS) to SQLNET.AUTHENTICATION_SERVICES= (NONE) in /oracle home/network/admin/sqlnet.ora.

The thing is that after applying that solution when I execute my workspace there's this Warning line in the log:

Unable to determine version of Oracle database. (serverType=`ORACLE8I', serverName=`myServerName', userName=`myUserNAme', password=`***', dbname=`').

It's confusing because warnings are important in our workflow.

Is there anything I can do to make FME know our database version?

Hi @dms2 - Thanks for reporting this to us - This has actually been linked to a bug in FME, we are logging something which we shouldn't be. We are working on a fix but the warning can be ignored in this case, really sorry for the inconvenience here. Can you perhaps expand on how the warning is effecting your workflow?

Hi @dms2 - Thanks for reporting this to us - This has actually been linked to a bug in FME, we are logging something which we shouldn't be. We are working on a fix but the warning can be ignored in this case, really sorry for the inconvenience here. Can you perhaps expand on how the warning is effecting your workflow?

Some warnings yield a later error in the workflow. So we check for warnings in the log at certain steps in our workflow and make it stop before the error occurs. This helps us to gather the workspace termination cause (the warning text) to send it to the user.

 

The new scenario makes us deliberately discard this warning in our already complex scripts.

 

Hope you find a fix to the bug soon.

 

 

I get this warning when connecting to Oracle too. I can run all the above queries successfully as the same user in sqlplus. The first returns no rows and the second returns a null , because we don't have the Spatial option. 

Connected to:
Oracle Database 12c Release 12.1.0.1.0 - 64bit Production

SQL> SELECT * FROM V$OPTION WHERE PARAMETER = 'Spatial' AND VALUE = 'TRUE';
no rows selected

SQL> select sdo_version from dual;


SQL> SELECT VERSION FROM V$INSTANCE;
12.1.0.1.0

Hello @dms2,

I’m pleased to let you know that a recent update to FME has resolved this issue.

You will find the update in our latest FME 2018.1 beta:

 

https://www.safe.com/support/support-resources/fme-downloads/beta/Should you have any feedback regarding the update, please reply to this thread or contact support. Thank you for your patience as we worked to resolve this issue. We appreciate your involvement in helping us make FME even better!Thank you!

Reply


Community Stats

30,159
Posts
114,480
Replies
37,807
Members
Terms & ConditionsCookie settings
A product of
Safe Software respectfully acknowledges that we live, learn and work on the traditional and unceded territories of the Kwantlen, Katzie, and Semiahmoo First Nations.