Click a star to rate this topic

Click a star to rate this topic

Click a star to rate this topic

Click a star to rate this topic

Click a star to rate this topic

Oracle

Read and Write Support

Data Store Type	As standard		Using FME Desktop
Data Store Type	Write	Read	Read	Write
Oracle

Commit Support

Data Store Type

Task Supported

Commit

Copy-to

Oracle

Input and Output Connection

Input Connection

Parameter	Description
Username	Schema containing the required data.
Password	Password for the selected Username.
Net Service Name	The identifier with which Oracle or JBoss identifies this database.
Host	The name of the machine in which the metadata store is created.
Port	The port number of the host.
Service Name	The Oracle system ID (SID).
JNDI Location	Location of the JNDI Java API (Java Naming and Directory Interface).
Schema Name	Name of the schema to be used.
Allow Invalid Geometries	Allows features with invalid geometries (e.g. duplicate vertices, self-intersections) to be imported. This is necessary if they need to be imported in order to be validated or corrected. If not ticked then features with invalid geometries are not imported and are logged as feature errors in the open data task.
Enable full 3D Geometries	Select to enable full 3D geometries. Note: This parameter will only appear with an additional license enabling 3D support within 1Integrate. For more information on full 3D in 1Integrate, please see 3D Support.
Scale for Coordinate Data	Scale determines how 1Integrate will round coordinates when writing to Oracle, using the number of digits to the right of the decimal point (e.g. 1.23456 at a scale of 3 is 1.234, and at a scale of 1 is 1.2). Note: Rounding the data can cause valid data to become invalid. To be safe, we advise you keep two more decimal places than your geometric tolerance. By default, scale is null and coordinate data is not rounded.
For X, Y, Z, M data:	If you have data that is recorded as X,Y,Z,M, you must opt to ignore either Z or M values by choosing to use X, Y and M or X, Y and Z only. Note: If the default is left on and X,Y,Z,M is uploaded then an exception will be thrown as 1Integrate only supports X,Y,M or X,Y,Z.
Write ignored Z or M values as zero	Select to write ignored values as zero in place of null.

Output Connection

Parameter	Description
Username	Schema containing the required data.
Password	Password for the selected Username.
Net Service Name	The identifier with which Oracle or JBoss identifies this database.
Host	The name of the machine in which the metadata store is created.
Port	The port number of the host.
Service Name	The Oracle system ID (SID).
JNDI Location	Location of the JNDI Java API (Java Naming and Directory Interface).
Schema Name	Name of the schema to be used.
Scale for Coordinate Data	Scale determines how 1Integrate will round coordinates when writing to Oracle, using the number of digits to the right of the decimal point (e.g. 1.23456 at a scale of 3 is 1.234, and at a scale of 1 is 1.2). Note: Rounding the data can cause valid data to become invalid. To be safe, we advise you keep two more decimal places than your geometric tolerance. By default, scale is null and coordinate data is not rounded.
Force geometry to be written with X, Y, Z, M	Select to output a fourth z or m ordinate for objects. Only takes effect if the geometry to be written has 3 coordinates.
For X, Y, Z, M data: Use zero rather than Null or NaN when writing ignored ordinate	Select to write ignored values as zero in place of null/NaN (NaN is used for the PostGIS data store)

Copyright © 2021 1Spatial
US Patent Number 9542416 B2 (2017-01-10)