Oracle Non-Spatial Reader Parameters
Database Connections
Database formats include a Database Connection parameter that defines and stores authentication information. For general information about sharing database connections, please see Using Database Connections. Note that Database Connection parameters may differ slightly, depending on context and/or database format. |
Select an existing connection, or Add Database Connection to define a new connection.
The new connection can be made visible only to the current user, or can be shared among multiple users.
Connection Parameters
Select the database to be used. Depending on your database, you may also have to enter a username and password.
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 to access the Oracle database.
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.
Constraints
Specifies whether to keep the table qualifier. The full name of a table in a database is of the format:
<prefix>.<table_name>
Depending on the database format, the prefix can be <database_name>.<owner_name>, <owner_name>, or <schema_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, or performing a translation to another database format but with a different user name.
When this parameter is selected during workspace generation, 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: Even when this parameter is selected, if the table is owned by a user other than the current user, the 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.
An SQL WHERE clause can be applied to the selected tables, to constrain the the row selection in tables chosen in the table list (for example, NUMLANES=2).
Schema Attributes
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, you can use this parameter to expose additional attributes on multiple feature types.
Advanced
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.
The default is 200.
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.
For detailed information about SQL functions, click the corresponding menu item in the
.Available menu options depend on the format.
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 or writer (depending on where the SQL statement is executed) 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.
For detailed information about SQL functions, click the corresponding menu item in the
.Available menu options depend on the format.
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 or writer (depending on where the SQL statement is executed) with an error. If the specified statement is preceded by a hyphen (“-”), such errors are ignored.