Oracle Spatial Object Writer Parameters

Add Named Database Connection: Named Connections store (in a central location) authentication information associated with a user.

For information about setting up and using named connections, please see:

Using Named Database Connections

Specifies the Oracle database to connect to. This may be a Net Service Name defined in tnsnames.ora or an Easy Connection Identifier. Either form of connection identifier may be prefixed with username and password information.

[<username>[/<password>]@][//]<hostname>[:<port>]/<service_name>.

[<username>[/<password>]@]<net_service_name>

Enter the username and password to access the service.

The name of the Oracle Workspace Manager workspace that will be used by the writer. All tables will be written using the same workspace. If this parameter is omitted, or left blank, the default LIVE workspace will be used.

If this checkbox is selected (default), the Oracle database connection remains open for other requestors. A persistent connection is useful for workspaces that are long-running, or published using FME Server.

If this checkbox is not selected, the connection to the Oracle database is closed as soon as possible after data processing is complete.

Oracle Spatial (object model) directly supports composite surfaces, 3D polygons and rectangles. Writing of 3D surfaces and solids is available only for Oracle 11g and above. If the Oracle Spatial (object model) writer detects an older version of Oracle Database, surface features will automatically be downgraded to a 2D representation prior to writing.

This directs the writer to write measures to the destination table. When this box is checked and the incoming feature does not have any measures, then null values are written. This option applies when writing to existing tables.

Note that if you are updating an existing table, ensure that the metadata table has proper entry of the measures for that table. The writer does not perform checks on existing tables for their measures support. It writes measures based on the Contains Measures option. Therefore, if you attempt to write measures to an existing table that originally did not support measures, this may result in datasets that do not pass Oracle’s validity tests.

However, when creating new tables, the writer takes care of everything including writing to the metadata table. The above directive is ignored when writing to points, multipoints, multiareas and heterogeneous collections, as Oracle does not support measures for these geometries.

These values apply to the entire layer – features with coordinate values outside this range will not be correctly indexed.

Specifies the minimum and the maximum measure values expected in the dataset.

Traditionally, FME would assign a GEOM name to all geometry columns stored in Oracle databases in all generated workspace and mapping files. This gives you the option of modifying what the geometry column will be named in tables created by FME.