ITPub博客

首页 > Linux操作系统 > Linux操作系统 > 刷新組 參數

刷新組 參數

原创 Linux操作系统 作者:golden_zhou 时间:2011-08-05 15:53:01 0 删除 编辑
刷新組:主要是保證是刷新組中的表的一致性。

DBMS_REFRESH.MAKE (
   name                  IN    VARCHAR2
   { list                IN    VARCHAR2,
   | tab                 IN    DBMS_UTILITY.UNCL_ARRAY,}
   next_date             IN    DATE,
   interval              IN    VARCHAR2,
   implicit_destroy      IN    BOOLEAN         := false,
   lax                   IN    BOOLEAN         := false,
   job                   IN    BINARY INTEGER  := 0,
   rollback_seg          IN    VARCHAR2        := NULL,
   push_deferred_rpc     IN    BOOLEAN         := true,
   refresh_after_errors  IN    BOOLEAN         := false
   purge_option          IN    BINARY_INTEGER  := NULL,
   parallelism           IN    BINARY_INTEGER  := NULL,
   heap_size             IN    BINARY_INTEGER  := NULL);



Parameter     Description

name

    

Unique name used to identify the refresh group, specified as [schema_name.]refresh_group_name. If the schema is not specified, then the current user is the default. Refresh groups must follow the same naming conventions as tables.

list

   

Comma-delimited list of materialized views that you want to refresh. Synonyms are not supported. These materialized views can be located in different schemas and have different master tables or master materialized views. However, all of the listed materialized views must be in your current database.

Each materialized view is specified as [schema_name.]materialized_view_name. If the schema is not specified, then the refresh group owner is the default.

tab

   

Instead of a comma-delimited list, you can supply a PL/SQL index-by table of names of materialized views that you want to refresh using the datatype DBMS_UTILITY.UNCL_ARRAY. If the table contains the names of n materialized views, then the first materialized view should be in position 1 and the n + 1 position should be set to NULL.

Each materialized view is specified as [schema_name.]materialized_view_name. If the schema is not specified, then the refresh group owner is the default.

next_date

   

Next date that you want a refresh to occur.

interval

   

Function used to calculate the next time to refresh the materialized views 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 materialized views 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 enables you to create an empty refresh group.

lax

   

A materialized view can belong to only one refresh group at a time. If you are moving a materialized view from an existing group to a new refresh group, then you must set this to true to succeed. Oracle then automatically removes the materialized view 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 materialized views. The default, NULL, uses the default rollback segment.

push_deferred_rpc

   

Used by updatable materialized views only. Use the default value, true, if you want to push changes from the materialized view to its associated master table or master materialized view before refreshing the materialized view. Otherwise, these changes might appear to be temporarily lost.

refresh_after_errors

   

Used by updatable materialized views 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 materialized view's master table or master materialized view.

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 processes.

1 specifies parallel propagation using only one parallel process.

heap_size

   

Maximum number of transactions to be examined simultaneously for parallel propagation scheduling. Oracle automatically calculates the default setting for optimal performance.

Note: Do not set this parameter unless directed to do so by Oracle Support Services.
 

来自 “ ITPUB博客 ” ,链接:http://blog.itpub.net/25198367/viewspace-704214/,如需转载,请注明出处,否则将追究法律责任。

请登录后发表评论 登录
全部评论

注册时间:2011-03-09

  • 博文量
    238
  • 访问量
    301801