Consider the following guidelines before you run a mapping:
You cannot read or write MongoDB column or table
names that have more than 225 characters.
The source tables must not be empty.
Otherwise, the mapping fails.
If the source contains binary data, the data
preview section shows jumbled text.
When you run a mapping in advanced mode, the Secure
Agent does not preserve the same order of columns in the MongoDB V2 target as in
the source.
When you perform the insert operation and
specify a collection that does not exist, MongoDB automatically creates a new
collection with that name.
You cannot fetch the details of the
rejected rows when you write data to a MongoDB V2 target.
You cannot use complex data type
columns as lookup conditions.
Avoid mapping the
_id
column to
optimize the write operation.
When you run a mapping, you might view info
logs in the session log under an error class reference. Here is an example where
you can see the information message logged as an error under the log entry
The error message
here is an informational message about the build version of the connector
and not an actual error. To view the encountered errors, refer to the error
row file.
ASK INFAPreview
