name
|
Unique name used to identify the refresh group. Refresh groups must follow the same naming conventions as tables. |
list
|
Comma-separated list of snapshots that you want to refresh. (Synonyms are not supported.) These snapshots can be located in different schemas and have different master tables; however, all of the listed snapshots must be in your current database. |
tab
|
Instead of a comma separated list, you can supply a PL/SQL table of names of snapshots that you want to refresh using the datatype DBMS_UTILITY .UNCL_ARRAY . If the table contains the names of n snapshots, then the first snapshot should be in position 1 and the n + 1 position should be set to NULL . |
next_date
|
Next date that you want a refresh to occur. |
interval
|
Function used to calculate the next time to refresh the snapshots in the group. This field is used with the NEXT_DATE value.
For example, if you specify NEXT_DAY(SYSDATE+1, "MONDAY") as your interval, and if your NEXT_DATE evaluates to Monday, then Oracle refreshes the snapshots every Monday. 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. |
implicit_destroy
|
Set this to TRUE if you want to delete the refresh group automatically when it no longer contains any members. Oracle checks this flag only when you call the SUBTRACT procedure. That is, setting this flag still allows you to create an empty refresh group. |
lax
|
A snapshot can belong to only one refresh group at a time. If you are moving a snapshot from an existing group to a new refresh group, then you must set this to TRUE to succeed. Oracle then automatically removes the snapshot from the other refresh group and updates its refresh interval to be that of its new group. Otherwise, the call to MAKE generates an error message. |
job
|
Needed by the Import utility. Use the default value, 0. |
rollback_seg
|
Name of the rollback segment to use while refreshing snapshots. The default, NULL , uses the default rollback segment. |
push_deferred_rpc
|
Used by updatable snapshots only. Use the default value, 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. |
refresh_after_errors
|
Used by updatable snapshots only. Set this to 0 if you want the refresh to proceed even if there are outstanding conflicts logged in the DEFERROR view for the snapshot's master. |
purge_option
|
If you are using the parallel propagation mechanism (in other words, 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 this unless so directed by Oracle Worldwide Support. |