CHANGE
(name IN VARCHAR2,
next_date IN DATE := NULL,
interval IN VARCHAR2 := NULL,
implicit_destroy IN BOOLEAN := NULL,
rollback_seg IN VARCHAR2 := NULL,
push_deferred_rpc IN BOOLEAN := NULL,
refresh_after_errors IN BOOLEAN := NULL,
purge_option IN BINARY_INTEGER := NULL,
parallelism IN BINARY_INTEGER := NULL,
heap_size IN BINARY_INTEGER := NULL);
The next_date parameter is analogous to the start with clause in the create materialized view
command. For example, to change the EMP_GROUP??™s schedule so that it will be replicated every
three days, you can execute the following command (which specifies a NULL value for the next_
date parameter, leaving that value unchanged):
execute DBMS_REFRESH.CHANGE
(name => 'emp_group',
624 Oracle Database 11g DBA Handbook
next_date => null,
interval => 'SysDate+3');
After this command is executed, the refresh cycle for the EMP_GROUP refresh group will be
changed to every three days.
NOTE
Refresh operations on refresh groups may take longer than comparable
materialized view refreshes. Group refreshes may also require
significant undo segment space to maintain data consistency during
the refresh.
You can manually refresh a refresh group via the REFRESH procedure of the DBMS_REFRESH
package. The REFRESH procedure accepts the name of the refresh group as its only parameter.
The command shown here will refresh the refresh group named EMP_GROUP:
execute DBMS_REFRESH.REFRESH('emp_group');
To delete a refresh group, use the DESTROY procedure of the DBMS_REFRESH package, as
shown in the following example.
Pages:
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919