Rules and guidelines for Oracle sources and targets in tasks
Rules and guidelines for Oracle sources
and targets
in tasks
Use the following rules and guidelines for Oracle sources
and targets
in a task:
You can use database tables, synonyms, or views as sources
and targets
.
When you create a saved query to read data from an Oracle database, you must omit the final semicolon from the SQL statement.
You can't use the
select * from <TABLE_NAME>
SQL command in a saved query. You must provide the explicit column list.
If there is an error row when you run a task to write data to an Oracle target in bulk mode, the Secure Agent writes the batch that contains the error row in normal mode.
Ensure that the Oracle target table name does not contain mixed case identifiers.
When you run a mapping task to create a target, the target is successfully created at runtime. If you drop the created target table and run the task again, the task fails.
When you add objects with a hyphen in the column names in the Source and Target transformations, consider the following rules and guidelines:
When the source column name that you read has hyphens and you use the
Create New at Runtime
option to create a target, the hyphens in the table name are converted to underscores in the target column.
If you add a new column to the object in an existing mapping and the column name has a hyphen, manually adding these columns in the mapping is not applicable.
If you parameterize the target object, the manual field map option in the
Field Mapping
tab is not applicable. You must select Automatic, Completely Parameterized, or Partially Parameterized as the field map options for the mapping to work successfully.
To write data in a sequence to an Oracle target in bulk mode, you can specify the following query syntax while creating an Oracle table:
CREATE TABLE <TABLE_NAME> (<COLUMN_NAME> <COLUMN_DATATYPE GENERATED BY DEFAULT ON NULL AS COLUMN_ALIAS_NAME>, <COLUMN_NAME2> <COLUMN_DATATYPE2>,...<COLUMN_NAME30> <COLUMN_DATATYPE30>)
Ensure that the columns that you want to use in bulk mode must be of the integer data type.
You can't write data to an Oracle target when you configure a source partitioning and run the mapping in bulk mode.
When you read from Oracle, ensure that the Oracle table name or column name does not contain Unicode characters.
Consider the following rules and guidelines when you use Oracle Autonomous Database sources and targets:
When you configure partitioning in bulk mode to write to Oracle Autonomous Database, use an existing target instead of creating a new target at run time. Otherwise, performance issue occurs.
To run a mapping that contains more than three source partitions, you must set the
Service Name
property value to
low
.
For more information about service names for Oracle Autonomous Database, see the Oracle Autonomous Database documentation.