1. Microservices Architecture Documentation
  2. Administer
  3. Error Management
  4. Overview of Oracle GoldenGate Error Handling
  5. Handling Replicat Errors during DML Operations

Handling Replicat Errors during DML Operations

To control the way that Replicat responds to an error during one of its DML statements, use the REPERROR parameter in the Replicat parameter file. You can use REPERROR as a global parameter or as part of a MAP statement. You can handle most errors in a default fashion (for example, to cease processing) with DEFAULT and DEFAULT2 options, and also handle other errors in a specific manner.

The following comprise the range of REPERROR responses:

  • ABEND: roll back the transaction and stop processing.

  • DISCARD: log the error to the discard file and continue processing.

  • EXCEPTION: send the error for exceptions processing.

  • IGNORE: ignore the error and continue processing.

  • RETRYOP [MAXRETRIES n]: retry the operation, optionally up to a specific number of times.

  • TRANSABORT [, MAXRETRIES n] [, DELAY[C]SECS n]: abort the transaction and reposition to the beginning, optionally up to a specific number of times at specific intervals.

  • RESET: remove all previous REPERROR rules and restore the default of ABEND.

  • TRANSDISCARD: discard the entire replicated source transaction if any operation within that transaction, including the commit, causes a Replicat error that is listed in the error specification. This option is useful when integrity constraint checking is disabled on the target.

  • TRANSEXCEPTION: perform exceptions mapping for every record in the replicated source transaction, according to its exceptions-mapping statement, if any operation within that transaction (including the commit) causes a Replicat error that is listed in the error specification.

Most options operate on the individual record that generated an error, and Replicat processes the other, successful operations in the transaction. The exceptions are TRANSDISCARD and TRANSEXCEPTION: These options affect all records in a transaction if any record in that transaction generates an error. (The ABEND option also applies to the entire transaction, but does not apply error handling.)

See REPERROR for syntax and usage.