Skip to main content
  • EN

We are unable to use the Oracle Non-Spatial reader to retrieve table schemas from the database. The error returned is as follows:

Failed to obtain any schemas from reader 'ORACLE_NONSPATIAL' from 1 datasets. This may be due to invalid datasets or format accessibility issues due to licensing, dependencies, or module loading. See logfile for more information

Unfortunately that is the log file, so there is no further information.

Oddly enough, once the workspace is generated it can be run perfectly fine and read data from the oracle database without error.

We have tried Oracle clients 11.2 and 12.1 with FME 2017, 2018, and 2019 and all error. The Oracle Client has been correctly installed and works great from sql developer, arcgis, and other applications. There is also a TNS_ADMIN environment variable to the TNS names file and the client path is in the PATH environment variable.

Additionally we are unable to retrieve SDE feature class schemas from the oracle database using the ESRI Geodatabase reader. This is already documented by another user here:

https://knowledge.safe.com/questions/75236/issue-connecting-to-arcsde-arcmap-105-using-connec.html

Has anyone had similar issues/experience? We have had a support ticket open on this since July 2018 and no progress, so any help that can be provided from this community would be awesome.

Could it be you are using 64 bit FME and have the 32 bit Oracle client installed?

That will not allow FME to read from Oracle.

Both need to be 32 or 64 bit.

Oracle Client and FME are both 32-bit versions. Like I say it can read data just fine for existing workbenches, so its not a client issue. It just can't retrieve table schemas from the database when you want to read in new tables using the Reader.

Could it be the user you are connecting with to the Oracle database does not have the SELECT_CATALOG_ROLE privilege?

Those allow a user to select from the data dictionary, that contains the schema information.

Not having that role does not prevent the user from retrieving the data, but does prevent reading the views/tables that contain the list of available tables.

That sounds like it could be along the right lines. But we do have that role. Another odd thing, it worked in FME 2015 but we had to upgrade to FME 2019 due to other software depencies/compatibility. Any FME version later than 2017 seems to give the oracle error.

Reply


Community Stats

30,108
Posts
114,302
Replies
37,745
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.