name
|
Name of the refresh group for which you want to alter the refresh interval. |
next_date
|
Next date that you want a refresh to occur. By default, this date remains unchanged. |
interval
|
Function used to calculate the next time to refresh the snapshots in the refresh group. This interval is evaluated immediately before the refresh. Thus, you should select an interval that is greater than the time it takes to perform a refresh. By default, the interval remains unchanged. |
implicit_destroy
|
Allows you to reset the value of the implicit_destroy flag. If this flag is set, then Oracle automatically deletes the group if it no longer contains any members. By default, this flag remains unchanged. |
rollback_seg
|
Allows you to change the rollback segment used. By default, the rollback segment remains unchanged. To reset this parameter to use the default rollback segment, specify NULL , including the quotes. Specifying NULL without quotes indicates that you do not want to change the rollback segment currently being used. |
push_deferred_rpc
|
Used by updatable snapshots only. Set this parameter to TRUE if you want to push changes from the snapshot to its associated master before refreshing the snapshot. Otherwise, these changes may appear to be temporarily lost. By default, this flag remains unchanged. |
refresh_after_
errors
|
Used by updatable snapshots only. Set this parameter to TRUE if you want the refresh to proceed even if there are outstanding conflicts logged in the DEFERROR view for the snapshot's master. By default, this flag remains unchanged. |
purge_option
|
If you are using the parallel propagation mechanism (that is, parallelism is set to 1 or greater), then:
- 0 = do not purge
- 1 = lazy (default)
- 2 = aggressive
In most cases, lazy purge is the optimal setting. Set purge to aggressive to trim back the queue if multiple master replication groups are pushed to different target sites, and updates to one or more replication groups are infrequent and infrequently pushed. If all replication groups are infrequently updated and pushed, then set purge to do not purge and occasionally execute PUSH with purge set to aggressive to reduce the queue. |
parallelism
|
0 specifies serial propagation; n > 1 specifies parallel propagation with n parallel server processes; 1 specifies parallel propagation using only one parallel server process. |
heap_size
|
Maximum number of transactions to be examined simultaneously for parallel propagation scheduling. Oracle automatically calculates the default setting for optimal performance. Do not set the parameter unless so directed by Oracle Worldwide Support. |