Managing Error Transactions

When Oracle pushes a deferred transaction from a materialized view or master site to another master site, Oracle ensures that the transaction is not removed from the local queue until it has been successfully propagated to the destination site. However, a transaction can be successfully propagated to a master site without being successfully applied at the destination site. An error in applying a deferred transaction may be the result of a database problem, such as a lack of available space in a table that you are attempting to update, or may be the result of an unresolvable replication conflict. If an error occurs, Oracle performs the following actions at the destination master site:

• Rolls back the transaction

• Logs the error transaction in the replication catalog of the receiving site

To learn more about monitoring and managing error transactions, refer to the following:

• Displaying Error Transactions

• Resolving Error Transactions

• Executing Error Transactions

• Removing Error Transactions