Mac OS, FME and Oracle

Liz Sanderson
Liz Sanderson
  • Updated

FME Version

  • FME 2019.x


The following was tested in FME Desktop (2015.1.3, 2016.x, 2017.x, 2018.x, 2019.x) for Mac OS on Mojave, El Capitan, Sierra, High Sierra. Yosemite OS is expected to work but has not been tested.

A new article for configuring Mac OS and Oracle Clients has been created from FME 2019.2.3.2 & FME 2020.x. See here.  



  1. Oracle Client 10g for Mac or greater downloaded and extracted to a known location
  2. FME 2015+ for Mac OS.
  3. Mac OS Yosemite or newer.


Configuration Steps

1. Download your Oracle Client for Mac OS (available from Oracle)


2. Identify the location of your Oracle Client files: We will assume for this article that they have been copied to /Applications/OracleClient.


3. Open a Terminal Window.


4. Run the following command to create a lib folder in your HOME folder and generate all but one required symbolic links for the dylib files. NOTE: "/path/to/" is to be updated in the lines below to point to your Oracle Client files.

mkdir -p ~/lib ; ln -fhs /path/to/OracleClient/*.dylib* ~/lib/


5. Create one more symbolic link for libclntsh dylib file:

ln -s /path/to/OracleClient/libclntsh.dylib.<insert version eg 11.1> ~/lib/libclntsh.dylib


6. You should now have something like this in your Home Folder (~/lib from Finder):



7. Launch FME Workbench and add an Oracle Reader and test the workspace.


Optional Parameters to help your Oracle Experience on Mac OS

TNS_ADMIN - variable points to your tnsnames.ora file. This is optional and if you plan to use direct connect. i.e. //servername:1521/sid you don't need to add this Environment Variable. SQLPATH - is for Oracle's SQLPlus command if you have downloaded this as part of the OracleInstant client. This is optional and if you don't plan to use the SQLPlus command line then this can be ignored.


Report issues

Please report any problems you encounter with FME and the Mac OS to Safe Software Support team. Please include a ~/dydl.log which can be obtained from the instructions below:

1. Launch Workbench from the command line using the following command (you may need to replace the version in the command line)


2. Try to add an Oracle reader/writer (which should not be possible if formats are greyed out).

3. Shut down Workbench.

4. Send us the resulting ~/dydl.log


Was this article helpful?



Please sign in to leave a comment.