Failure

Use the Failure transform to handle exceptions that might be raised by the configured database server when your message map runs SQL statements to implement the action of a database transform.

If you want the message map to handle exceptions that are returned from the database server when the SQL operation is run, instead of such exceptions stopping the message map and being reported, you can add a Failure transform to the transform group.

The Failure transform is an optional transform that can be added or removed as required.

The Failure transform does not perform any transformation. You must transform the input and output elements within the nested map.

Handling database warnings

When you create a database transform, select Treat warning as error if you want the database warnings to be treated as errors.

If this option is selected, the first SQL operation that results in a warning from the selected database raises an exception.

Run time behavior

The way that database exceptions are handled is determined by the configuration of the corresponding Failure transform in a message map:
  1. If the Failure transform is present in the message map, and is connected to one or more output objects, then the exception is caught and processed by the Failure transform.
  2. If the Failure transform is present in the message map, but is not connected, then the exception is caught by the Failure transform, and is ignored.
  3. If the Failure transform has been deleted from the message 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.
  4. If you want the message map to stop running when the database transform receives an SQL exception, remove the Failure transform. For more information, see Handling database exceptions in a graphical data map.