Denodo Reader

FME can access attribute data held in Denodo database tables. FME provides read access via Denodo's JDBC driver.

Note  Denodo’s JDBC driver is not bundled with FME, but can be installed as part of Denodo Express. To install Denodo Express, please visit http://www.denodo.com/en/denodo-platform/denodo-express.

Denodo’s JDBC driver is located at

<Denodo folder location>/lib/vdp-jdbcdriver-core/denodo-vdp-jdbcdriver.jar

within the installed Denodo Express folder.

Please note that in order for Denodo’s JDBC driver to work correctly, the version of the driver must match the version of the Denodo server used.

Installing the JDBC Driver

To view instructions for installing the JDBC driver, please see Getting Started with JDBC.

Usage Notes

The performance of this format is dependent on the amount of memory allocated to the Java Virtual Machine (JVM). The following environment variables allow you to specify memory available to Java Plugins:

Initial heap size for initializing the JVM. If unset, the default value is 1024K.

This variable must be set in multiples of 1024 and greater than 1 MB. To indicate kilobytes, megabytes, or gigabytes, append k or K, m or M, or g or G, respectively. For example, any of these values is acceptable:

6291456

6144k

6m

Maximum heap size for initializing the JVM. If unset, the default value is 16384K.

This variable must be set in multiples of 1024 and greater than 2 MB. To indicate kilobytes, megabytes, or gigabytes, append k or K, m or M, or g or G, respectively. For example, any of these values is acceptable:

83886080

81920k

80m

Tip  To pass additional parameters used by FME to the Java Virtual Machine, use the JAVA_TOOL_OPTIONS environment variable.
Memory Usage (applicable to writers only): Changing the value in the writer parameter Features Per Transaction can control the number of features that FME places in each transaction before a transaction is committed to the database.