DB Transaction Level (Magic xpi 4.14)
When using a database Destination in Data Mapper, and a DB transaction level for the Mapper step is defined, the following error handling behavior is performed:
|
|
|
|
|
|
Exit
|
Mapper
|
All records are rolled back.
|
All records are rolled back.
|
|
Continue
|
Mapper
|
No rollback, continue to process the records (except error record in all connected destinations).
|
No rollback, continue to process the records (except error record in all connected destinations).
|
|
Exit
|
Record
|
Save all records before error.
|
Save all records before error.
|
|
Continue
|
Record
|
No rollback, continue to process the records (except error record in all connected destinations).
|
No rollback, continue to process the records (except error record in all connected destinations).
|
|
Exit
|
Auto Commit
|
All records except the one that raised the error are committed.
|
Auto Commit is not supported at the runtime.
|
|
Continue
|
Auto Commit
|
All records except the one that raised the error are committed, and the Data Mapper continues to the next record.
|
Auto Commit is not supported at the runtime.
|
* For more information about database transaction levels, click here.
|
|
-
If an error occurs when mapping data in a flow that includes a database Destination, and the flow has an error handling flow assigned to it (even if the error occurs in a non-database step), the error flow is called immediately when the error occurs. The mapping for that Destination stops, and no further mapping occurs until the error handling flow is complete. In this case, you can choose to create a log file in the error handling flow, so that the error code and description are not lost.
-
In cases where a transaction is already open, the Data Mapper joins this transaction and ignores the DB Transaction Level value.
-
The Record Dynamic option is not supported for the JDBC schema. (Since version: 4.13.3)
|
