See information about the latest product version
Failure
Use the Failure transform to handle exceptions that might be raised by the configured database server when your graphical data map runs SQL statements to implement the action of a database transform.
If you want the map to handle exceptions that are returned from the database server when the SQL operation is run, instead of such exceptions stopping the map and being reported, you can add a Failure transform to the transform group. The Failure transform is an optional transform type. If an exception is raised by the configured database server, and you have not configured a corresponding Failure transform, the map operation is stopped. The Failure transform is an optional transform type. For more information, see Handling database exceptions in a graphical data map.
- If the Failure transform is present in the graphical data map, and is connected to one or more output objects, then the exception is caught and processed by the Failure transform.
- If the Failure transform is present in the graphical data map, but is not connected, then the exception is caught by the Failure transform, and is ignored.
- If the Failure transform has been deleted from the graphical data map, then the exception is handled by the Mapping node in your message flow, and is handled in the same way as other message flow exceptions.
If you want the failure to cause the execution of the map to stop when the database transform receives an SQL exception, remove the Failure from the transform.
For information about the Mapping node, see Mapping node.