Oracle Spatial Object Reader 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 reader. All tables will be read 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.

If selected, the Table List will include tables that live in system schemas or contain special characters like / and $.

Recycled tables (names starting with BIN$) will never be displayed.

Specifies whether to keep the schema qualifier. The full name of a table in an Oracle database is of the format <owner_name>.<table_name>. Selecting this option indicates that the reader should return the table name without any prefixes. This is useful, for example, when creating a workspace that will be passed on to another organization using the same table names.

When this option is selected during the generation of a workspace, the source feature types will be the table names without any prefix; otherwise, they will contain the owner name as a prefix. It is recommended that you do not change this setting after generating the workspace as it is possible for no features to be successfully passed onto the writer (since the writer is expecting feature types with different names).

Note: Even when this option is selected, if the table is owned by a user other than the current user, the <owner_name> prefix will not be dropped. This is to ensure that the reader will find the correct table.

Controls whether 3D polygons are read by Oracle Spatial as 3D face geometries or as regular polygons.

After you have completely specified the database connection, click the Browse button to select tables for import. A connection window appears while the system compiles a table from the database.

Once the table list appears, you can select one or more tables, and then click OK to dismiss the window. The table name(s) will appear in the table list field in the Parameter box.

Enter any SQL where clause that constrains the attributes of the layers selected in the layer list (for example, NUMLANES=2).

Checking this box allows the reader to parse MapInfo style and index columns.

This optional generation parameter specifies the name of the MapInfo symbology style column. If a column by this name is found, it will be omitted from the schema of the generated source feature type, and the oracle_mapinfo_symbology_style_column DEF line parameter will be set to the name of this column. The default column name is MI_STYLE.

This optional generation parameter specifies the name of the MapInfo symbology index column. If a column by this name is found, it will be omitted from the schema of the generated source feature type. The default column name is MI_PRINX.

This parameter exposes Format Attributes in Workbench when you create a workspace:

• In a dynamic scenario, it means these attributes can be passed to the output dataset at runtime.
• In a non-dynamic scenario where you have multiple feature types, it is convenient to expose additional attributes from one parameter. For example, if you have ten feature types and want to expose the same attribute in each one, it is easier to define it once than it is to set each feature type individually in the workspace.

Using the minimum and maximum x and y parameters, define a bounding box that will be used to filter the input features. Only features that interact with the bounding box are returned.

If all four coordinates of the search envelope are specified as 0, the search envelope will be disabled.

Select this option to remove any portions of exported features outside the area of interest.