Previous |
Next |
After you have resolved the problem that caused an error transaction, you can re-execute the error transaction. If the error transaction executes successfully, Oracle automatically removes the transaction from the replication catalog at the local site.
To re-execute an error transaction:
In Enterprise Manager, connect to the Database Instance Home page as the replication administrator.
Click Data Movement.
Under the Advanced Replication section, click Manage.
The Administration Overview page appears.
Under the General section, click the number link next to Error Transactions to open the Error Transactions page.
Select the individual error transaction.
Click Retry.
When Oracle re-executes an error transaction at the receiving site, Oracle executes the transaction in the security context of the original receiver. If the original receiver is no longer a valid user (that is, if the user was dropped), the deferred transaction can be re-executed under the security context of a different user using the DBMS_ DEFER_SYS.EXECUTE_ERROR_AS_USER
procedure.
For detailed information about this procedure, see Oracle Database Advanced Replication Management API Reference.
Note: If you re-execute a single error transaction, Oracle does not commit the transaction, even if it executes successfully. If you are satisfied with the results of the transaction, you should issue the SQL command COMMIT
. If EXECUTE_ERROR
re-executes multiple transactions, each transaction is committed as it completes.
API Equivalent: DBMS_DEFER_SYS.EXECUTE_ERROR