1. Microservices Architecture Documentation
  2. Administer
  3. Error Management
  4. Overview of Oracle GoldenGate Error Handling
  5. Handling Replicat Errors during DML Operations
  6. Handling Errors as Exceptions
  7. About the Exceptions Table

About the Exceptions Table

Use an exceptions table to capture information about an error that can be used for such purposes as troubleshooting your applications or configuring them to handle the error. At minimum, an exceptions table should contain enough columns to receive the entire row image from the failed operation. You can define extra columns to contain other information that is captured by means of column-conversion functions, SQLEXEC, or other external means.

To ensure that the trail record contains values for all of the columns that you map to the exceptions table, you can use either the LOGALLSUPCOLS parameter or the following parameters in the Extract parameter file:

  • Use the NOCOMPRESSDELETES parameter so that all columns of a row are written to the trail for DELETE operations.

  • Use the GETUPDATEBEFORES parameter so that Extract captures the before image of a row and writes them to the trail.