Specifying a Site's Purge Schedule

A scheduled purge determines how a master or materialized view site purges applied transactions from its deferred transaction queue. When you used the Replication Setup Wizard to create a master or materialized view site, Oracle created a job in each site's local job queue to purge the local deferred transaction queue on a regular basis. Consider the following options for a site's purge schedule.

• You can synchronize the pushing (scheduled links) and purging of a site's deferred transaction queue.

  For example, you can configure continuous pushing and purging of the transaction queue. This type of configuration might offer performance advantages because it is likely that information about recently pushed transactions is already in the server's buffer cache for the corresponding purge operation.

  See Oracle Database Advanced Replication for information about configuring continuous pushing and purging of the transaction queue.

• When a server is not CPU bound, you can schedule continuous purging of the deferred transaction queue to keep the size of the queue as small as possible.

• For servers that experience a high-volume of transaction throughput during normal business hours, you can schedule purges to occur during off-peak hours.

If you want to modify a site's purge schedule, complete the following steps:

1. In Enterprise Manager, connect to the Database Instance Home page as the replication administrator.

2. Click Data Movement.

3. Under the Advanced Replication section, click Manage.

   The Administration Overview page appears.

4. Click Purge Schedule.

5. Modify the purge schedule for the site. If you need more information about the controls, click Help.

6. Click Apply when you have completed your modifications.