When you import multiple source objects, ensure that the table and column names do not contain Unicode characters.

Ensure that the source or target table names and field names do not contain special characters.

When you import a JDBC V2 object and search for special characters, the search results do not display the objects.

The mapping fails when the target table name contains double quotes.

If you change the schema name in the connection, the updated schema name does not reflect in the user interface in the existing mapping object. However, the updated schema reflects at runtime.

When you join multiple Azure SQL Database tables, the schemas must have different table names.

When you preview the data for time(4), time(5) and time(6) data types, the data is truncated beyond precision 3.

Do not specify a filter in a mapping for the Azure SQL Database source that contains the Datetime data type.

When you read or write data that contains time(4), time(5), and time(6) data types, the data is truncated beyond precision 3.

When you write data that contains the Timestamp data type to a PostgreSQL or Azure SQL Database target using the

Create New at Runtime

option, the Timestamp data type value is appended with the time zone.

When you create a new Azure SQL or PostgreSQL Database target at runtime and the source data contains the Time data type, the Secure Agent writes the date time value until microseconds.

When you read from or write to an Oracle table that contains the Number data type, even though the precision does not exceed the maximum allowed value of 38, the mapping adds additional digits to the data. To avoid issues with the Number data type precision, select the

Apply Custom Schema

advanced property in the Source or Target transformations, based on the operation that you configure.

When you configure the field mapping and the source or target object is parameterized, set the field mapping to

Automap

. If you set the field mapping to

Manual

, the mapping does not run in advance mode.

You can't parameterize multiple JDBC V2 source objects.

The number of fields in the source and target must be identical when you configure the update mode in the Target transformation.

To perform an update, upsert, delete, or data driven operation on the target, you must specify a column in the

Update Columns

field even though you define a primary key in the target table.

When you specify a column in the

Update Columns

field, the Secure Agent inserts rows that contain duplicate data and also updates or upserts data in the target table when both of the following conditions are true:

The source table contains columns that have duplicate data.
The target table does not have a primary key.

You can't use multiple PostgreSQL sources in a mapping when you perform an update, upsert, delete, or data driven operation on the target.

You can't perform an update, upsert, delete, or data driven operation on Oracle synonyms.

To perform a data driven operation on the target, ensure that the column selected in the

Update Columns

field does not contain duplicate or null values.

When you run a mapping with an Upsert or Data Driven target operation, the number of processed and failed rows for the target operation is not displayed on the

Individual Task Results

page.

To retain the same metadata in the target table after you perform an update, upsert, delete, or data driven operation on the target, select the

Truncate Target

option in the Target transformation.