Handling Exceptions

Exception handling policies and logging options are defined for an RPS mapping, as follows.

• Halt on exception

  The offending transaction is aborted and database tracking ceases. When database tracking is halted, the tracker process causes an event to which applications executing on the primary database can subscribe. When tracking halts, this is represented as an alarm condition by the JADE SDS Administration application.

• Take a specified alternative action for the operation

  The alternative action exception policy applies only to certain benign exceptions, which are listed in the following table.

  SQL Statement	Exception	Alternative Action
  INSERT	Row exists	Convert to UPDATE
  UPDATE	Updates zero rows	Convert to INSERT
  DELETE	Deletes zero rows	Ignore

  An UPDATE or DELETE operation that affects more than one row is always fatal. Any unexpected exception is considered fatal. Fatal exceptions trigger the halt on exception policy. The alternative action policy does not apply to historical tables. As there are no defined benign exceptions for historical tables, any exception is considered fatal.

You can override these values by using the Configure RPS Node dialog on the RPS node, which provides error and log mapping override options. For details about these exception-related mapping override options, see step 3 under "Configuring Your RPS Node", later in this chapter.

For details about:

• Specifying RPS database map create, update, and delete statement exception policies, see "Setting Up the RPS Options", in Chapter 15 of the JADE Development Environment User’s Guide.

• Disabling automatic process dumps generated when the Datapump application encounters an exception replicating the effects of a transactions, see "Disabling Datapump Application Automatic Process Dumps", later in this chapter.

• Automatically restarting the Datapump application after connection or timeout errors, see "Automatic Restart on Connection or Timeout Errors", later in this chapter.

• Controlling the handling exceptions in column-mapping methods, see "Handling Exceptions in Column-Mapping Methods", earlier in this chapter.