SCHEDULE_PURGE Procedure

This procedure schedules a job to purge pushed transactions from the deferred transaction queue at your current master site or materialized view site. You should schedule one purge job.

See Also:

Oracle Database Advanced Replication for information about using this procedure to schedule continuous or periodic purge of your deferred transaction queue

Syntax

DBMS_DEFER_SYS.SCHEDULE_PURGE (
   interval             IN  VARCHAR2,
   next_date            IN  DATE,
   reset                IN  BOOLEAN        := NULL,
   purge_method         IN  BINARY_INTEGER := NULL,
   rollback_segment     IN  VARCHAR2       := NULL,
   startup_seconds      IN  BINARY_INTEGER := NULL,
   execution_seconds    IN  BINARY_INTEGER := NULL,
   delay_seconds        IN  BINARY_INTEGER := NULL,
   transaction_count    IN  BINARY_INTEGER := NULL,
   write_trace          IN  BOOLEAN        := NULL);

Parameters

Table 14-26 SCHEDULE_PURGE Procedure Parameters

Parameter	Description
interval	Allows you to provide a function to calculate the next time to purge. This value is stored in the `interval` field of the `DEFSCHEDULE` view and calculates the `next_date` field of this view. If you use the default value for this parameter, `NULL`, then the value of this field remains unchanged. If the field had no previous value, it is created with a value of `NULL`. If you do not supply a value for this field, you must supply a value for `next_date`.
next_date	Allows you to specify a time to purge pushed transactions from the site's queue. This value is stored in the `next_date` field of the `DEFSCHEDULE` view. If you use the default value for this parameter, `NULL`, then the value of this field remains unchanged. If this field had no previous value, it is created with a value of `NULL`. If you do not supply a value for this field, then you must supply a value for `interval`.
reset	Set to `true` to reset `LAST_TXN_COUNT`, `LAST_ERROR`, and `LAST_MSG` to `NULL`.
purge_method	Controls how to purge the deferred transaction queue: `purge_method_quick` costs less, while `purge_method_precise` offers better precision. Specify the following for this parameter to use `purge_method_quick`: `dbms_defer_sys.purge_method_quick` Specify the following for this parameter to user `purge_method_precise`: `dbms_defer_sys.purge_method_precise` If you use `purge_method_quick`, deferred transactions and deferred procedure calls that have been successfully pushed may remain in the `DEFTRAN` and `DEFCALL` data dictionary views for longer than expected before they are purged. For more information, see "Usage Notes". These usage notes are for the `DBMS_DEFER_SYS.PURGE` function, but they also apply to the `DBMS_DEFER_SYS.SCHEDULE_PURGE` procedure.
rollback_segment	Name of rollback segment to use for the purge, or `NULL` for default.
startup_seconds	Maximum number of seconds to wait for a previous purge of the same deferred transaction queue.
execution_seconds	If >0, then stop purge cleanly after the specified number of seconds of real time.
delay_seconds	Stop purge cleanly after the deferred transaction queue has no transactions to purge for `delay_seconds`.
transaction_count	If > 0, then shut down cleanly after purging `transaction_count` number of transactions.
write_trace	When set to `true`, Oracle records the result value returned by the `PURGE` function in the server's trace file.