JDBC (Java Database Connectivity) Reader/Writer

FME can access attribute data held in databases accessible via JDBC. It provides generic non-spatial access to a wide number of database formats through JDBC drivers. The advantage of the JDBC is that it is available on all platforms supported by FME.

Once configured, the JDBC format allows access to many database formats.

See the FME Community for information about the compatibility of various JDBC drivers with FME, and to view FME Workbench examples.

JDBC Product and System Requirements

Dependencies  JDBC access requires a driver (4.0 or 4.1) for the target database, and a connection string. See Getting Started with JDBC.

Format

FME Platform

Operating System

Reader/Writer

FME Form

FME Flow

FME Flow Hosted

Windows 64-bit

Linux

Mac

Reader

Yes

Yes

No

Yes

No

No

Writer

Yes

Yes

No

Yes

No

No

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:

FME_JVM_MIN_HEAP_SIZE

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

FME_JVM_MAX_HEAP_SIZE

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.

FME Knowledge Base