IBM DB2 Spatial Writer Parameters

This is the data source name as configured using the DB2 client software.

Enter the username and password to access the database, user account, or wherever authentication is required.

When enabled, the database connection persists for the duration of an FME session.

For example, it may be desirable to maintain a connection when running a batch of 100 workspaces on the same database connection, which saves the processing time required to make and break a database connection.

FME considers the database connection to be the same when the database name, the username, and password are the same.

The time (seconds) after which to terminate a query to the database if it has not yet returned a connection/result.

If it is set to 0, there is no timeout. The default is 30.

These parameters are used only when creating new tables. They can be conveniently used to set Min X, Min Y, and Scale Factor for all feature types in a writer. However, you can override these writer defaults by specifying non-default values for Min X, Min Y, and Scale Factor in the writer format parameters.

Please see documentation for db2_offset_x, db2_offset_y, and db2_scale_x for further details.

Some features’ geometries may fail DB2 Spatial Extender’s check constraints based on the offset, scale, and coordinate system values. These features, as well as others with out-of-range or invalid attribute values, will be rejected and cannot be written to the database. If Yes, the translation will abort immediately after encountering such a problem. If No, the translation will continue, but the rejected features will not be written to the database.

This parameter allows users to tune the performance of the reader. It specifies how many rows are read from the database at a time.

Features can be read from the DB2 Spatial database using a bulk reading technique to maximize performance. Normally, 1000 rows of data are read from the database at a time. However, when reading LOB (BLOBs or CLOBs) data, FME is restricted to a transaction interval of size 1. Since geometry columns are normally BLOB types, reading of spatial features will not be affected by this directive.

This parameter allows for the execution of SQL statements before opening a table for writing. For example, it may be necessary to drop a constraint before attempting to write to it. The statements will be executed only when the first feature arrives at the writer.

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 written. For example, it may be necessary to clean up a temporary view after creating 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 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.

Sets the global finest grid size for the spatial grid index. If a dataset contains many different tables, but the same finest grid size applies to all of them, then this is a convenient way of setting the finest grid size value.

Sets the global middle grid size for the spatial grid index. If a dataset contains many different tables but the same middle grid size applies to all of them, then this is a convenient way of setting the middle grid size value.

Sets the global coarsest grid size for the spatial grid index. If a dataset contains many different tables but the same coarsest grid size applies to all of them, then this is a convenient way of setting the coarsest grid size value.