Oracle Non-Spatial Reader Parameters

This parameter specifies a database connection for the reader through a drop-down menu. The Add Database Connection option in the menu allows for a new connection to be created. The new connection can be made visible only to the current user, or can be shared among multiple users.

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>

The username and password.

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 parameter 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 parameter is deselected, the connection to the Oracle database is closed as soon as possible after data processing is complete.

If selected or set to Yes, the Table List (in the reader parameters dialog and in the parameter dialog for Feature Types to Read), and the Merge Filter parameter in the reader feature types dialog will include tables that live in system schemas or which contain special characters like / and $.

If deselected or set to No, the Table List and the Merge Filter will not include system tables or tables with special characters.

Note that recycled tables (names starting with BIN$) will never be included.

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 parameter 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 parameter 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 parameter after generating the workspace, because it is possible for no features to be successfully passed onto the writer (since the writer is expecting feature types with different names).

Note: Note: Even when this parameter 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.

After you have 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 tables selected in the Table List (for example, NUMLANES=2).

Use this parameter to expose 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.

Rows are read from the Oracle database using a bulk reading technique to maximize performance.

This parameter allows you to tune the performance of the reader by specifying how many rows are read from the database at a time.

This parameter allows for the execution of SQL statements before opening a table for reading. For example, it may be necessary to create a temporary view before attempting to read from it.

Multiple SQL commands can be delimited by a character specified using the FME_SQL_DELIMITER directive, embedded at the beginning of the SQL block. The single character following this directive will be used to split the SQL block into SQL statements, which will then be sent to the database for execution. Note: Include a space before the character.

For example:

FME_SQL_DELIMITER ;
DELETE FROM instructors;
DELETE FROM people
WHERE LastName='Doe' AND FirstName='John'

Multiple delimiters are not allowed and the delimiter character will be stripped before being sent to the database.

Any errors occurring during the execution of these SQL statements will normally terminate the reader with an error. If the specified statement is preceded by a hyphen (“-”), such errors are ignored.

This parameter allows for the execution of SQL statements after a set of tables has been read. For example, it may be necessary to clean up a temporary view after creating it, and before translation.

Multiple SQL commands can be delimited by a character specified using the FME_SQL_DELIMITER directive, embedded at the beginning of the SQL block. The single character following this directive will be used to split the SQL block into SQL statements, which will then be sent to the database for execution. Note: Include a space before the character.

For example:

FME_SQL_DELIMITER ;
DELETE FROM instructors;
DELETE FROM people
WHERE LastName='Doe' AND FirstName='John'

Multiple delimiters are not allowed and the delimiter character will be stripped before being sent to the database.

Any errors occurring during the execution of these SQL statements will normally terminate the reader with an error. If the specified statement is preceded by a hyphen (“-”), such errors are ignored.

Start Feature

This parameter specifies the feature number at which to start reading. This is useful if, for example, the table contains many spatial elements and only a portion of those elements are desired.

Max Features to Read

This parameter specifies the maximum number of features to read in the overall translation.

Max Features to Read Per Feature Type

This parameter specifies the maximum number of features to read per each individual feature type.

Min Features to Read

This parameter specifies the minimum features to read in the overall translation. If the specified number of features are not read, the translation will abort and fail. This is useful if, for example, the source fewer features than expected or none at all.

Feature Types To Read

This parameter specifies the features types to read from the database. It is used to limit the available and defined database tables that will be read.