drop_apply Procedure

For example, to drop the Apply process named LN1_APPLY and remove all the rule sets and rules, the following statement can be used:

PROMPT dropping the Apply Process
BEGIN
DBMS_APPLY_ADM.DROP_APPLY(
 APPLY_NAME => 'LN_APPLY',
 drop_unused_rule_sets => true);
END;
/

The following section outlines how error transactions can be re-executed.

execute_all_errors Procedure

The execute_all_errors procedure re-executes the error transactions for the specified Apply process. The transactions are re-executed in commit SCN order. Error re-execution stops if an error is raised. In many situations, when the error condition arises, administrators analyze and rectify the problem. For example, rows are being inserted with a dependent foreign key. Since the row in the parent table is missing, there will be an integrity violation which results in errors. Once the row is made good in the parent table, the errors can be re-executed to insert the failed rows. The following is the syntax for the execute_all_errors procedure: