Oracle8(TM) Server Replication
Release 8.0

A54651-01

Library

Product

Contents

Index

Prev Next

11
Data Dictionary Views

This chapter describes the data dictionary views that can be useful to users of the advanced replication facility. The views are alphabetized within the following general groupings:

Replication Catalog Views

Whenever you install advanced replication capabilities at a site, Oracle installs the replication catalog, which consists of tables and views, at that site. As shown in Table 11-1, the views are used by master and snapshot sites to determine such information as what objects are being replicated, where they are being replicated, and if any errors have occurred during replication. You should not modify the replication catalog tables directly; use the procedures provided in the DBMS_REPCAT package.

Each view has three versions, which have different prefixes: USER_*, ALL_*, and SYS.DBA_* unless otherwise stated. This section ignores any differences between these views.

REPGROUP View

The REPGROUP view lists all of the object groups that are being replicated. The members of each object group are listed in a different view, REPOBJECT.

Table 11-1: REPGROUP View
Column   Description  

sname  

The name of the replicated schema. Obsolete with release 7.3 or later.  

gname  

The name of the replicated object group.  

master  

'Y' indicates that this is a master site. 'N' indicates the current site is a snapshot site.  

status  

Used at master sites only. Status can be: normal, quiescing, or quiesced.  

schema_Comment  

Any user-supplied Comments.  

Figure 11-1: Replication Catalog Views

REPCATLOG View

The REPCATLOG at each master site contains the interim status of any asynchronous administrative requests and any error messages generated. All messages encountered while executing a request are eventually transferred to the REPCATLOG at the master that originated the request. If an administrative request completes without error, ultimately all traces of this request are removed from the REPCATLOG view.

Table 11-2: REPCATLOG View
Column   Description  

id  

A sequence number. Together, the ID and SOURCE columns identify all log records at all master sites that pertain to a single administrative request.  

source  

Location that the request originated.  

userid  

Userid of person making the request.  

timestamp  

When the request was made.  

role  

Indicates if site is the 'masterdef' or a 'master' site.  

master  

If the role is 'masterdef' and the task is remote, indicates which master is performing the task.  

sname  

The name of the schema for the replicated object, if applicable.  

request  

The name of the DBMS_REPCAT administrative procedure that was run.  

oname  

The name of the replicated object, if applicable.  

type  

The type of replicated object.  

status  

The status of the administrative request: ready, do_callback, await_callback, or error.  

message  

Any error message that has been returned.  

errnum  

The Oracle error number for the message.  

gname  

The name of the replicated object group.  

REPCOLUMN View

The REPCOLUMN view lists the replicated columns for a table.

Table 11-3: REPCOLUMN View
Column   Description  

sname  

The name of the object owner.  

oname  

The name of the object.  

type  

The type of the object.  

cname  

The name of the replicated column.  

id  

The id of the replicated column.  

pos  

The ordering of the replicated column.  

compare_old_on_delete  

Indicates whether Oracle sends and compares the old value of the column in replicated deletes.  

compare_old_on_update  

Indicates whether Oracle sends and compares the old value of the column in replicated updates.  

REPCOLUMN_GROUP View

The REPCOLUMN_GROUP view lists all of the column groups that you have defined for each replicated table.

Table 11-4: REPCOLUMN_GROUP View
Column   Description  

sname  

The name of the schema containing the replicated table.  

oname  

The name of the replicated table.  

group_name  

The column group name.  

group_Comment  

Any user-supplied Comments.  

Note: The sname column is not present in the USER_ view.

REPCONFLICT View

The REPCONFLICT view displays the name of the table for which you have defined a conflict resolution method and the type of conflict that the method is used to resolve.

Table 11-5: REPCONFLICT View
Column   Description  

sname  

The name of the schema containing the replicated table.  

oname  

The name of the table for which you have defined a conflict resolution method.  

conflict_type  

The type of conflict that the conflict resolution method is used to resolve: delete, uniqueness, or update.  

reference_name  

The object to which the routine applies. For delete conflicts, this is the table name. For uniqueness conflicts, this is the constraint name. For update conflicts, this is the column group name.  

Note: The sname column is not present in the USER_ view.

RepDDL View

The REPDDL holds DDL for replication objects.

Table 11-6: REPDDL View
Column   Description  

log_id  

Identifying number of the REPCAT log record.  

source  

Name of the database at which the request originated.  

role  

'Y' if this database is the masterdef for the request;
'N' if this database is a master.  

master  

Name of the database that processes this request.  

line  

Ordering of records within a single request.  

text  

Portion of an argument or DDL text.  

RepGenerated View

The REPGENERATED view lists information about system-generated objects.

Table 11-7: REPGENERATED View
Column   Description  

sname  

Owner of the object.  

oname  

Object name.  

type  

Object type.  

base_sname  

Owner of the base object.  

base_oname  

Object name of the base object.  

base_type  

Object type of the base object.  

package_prefix  

Prefix for package wrapper name.  

procedure_prefix  

prefix for procedure wrapper for procedures within a package wrapper.  

distributed  

'Y' if generation is distributed;
'N' if generated objects are cloned.
Should always be 'Y' for Rep3 environments.  

reason  

The reason why this object was generated.  

Note: The REPGENERATED view is obsolete and is kept only for backward compatibility.

REPGROUPED_COLUMN View

The REPGROUPED_COLUMN view lists all of the columns that make up the column groups for each table.

Table 11-8: REPGROUPED_COLUMN View
Column   Description  

sname  

The name of the schema containing the replicated table.  

oname  

The name of the replicated table.  

group_name  

The name of the column group.  

column_name  

The name of the column in the column group.  

Note: The sname column is not present in the USER_ version of the view.

REPKEY_COLUMNS View

The REPKEY_COLUMNS view lists information relating to the primary key column.

Table 11-9: REPKEY_COLUMNS View
Column   Description  

sname  

Owner of the replicated table.  

oname  

Name of the replicated table.  

col  

"Primary Key" column name in the table.  

REPOBJECT View

The REPOBJECT view provides information about the objects in each replicated object group. An object can belong to only one object group. A replicated object group can span multiple schemas.

Table 11-10: REPOBJECT View
Column   Description  

sname  

The name of the schema containing the replicated object.  

oname  

The name of the replicated object.  

type  

The type of replicated object: table, view, package, package body, procedure, function, index, synonym, trigger, or snapshot.  

status  

CREATE indicates that Oracle is applying user supplied or Oracle-generated DDL to the local database in an attempt to create the object locally. When a local replica exists, Oracle COMPAREs the replica with the master definition to ensure that they are consistent. When creation or comparison complete successfully, Oracle updates the status to VALID; otherwise, it updates the status to ERROR. If you drop an object, Oracle updates its status to DROPPED before deleting the row from the REPOBJECT view.  

id  

The identifier of the local database object, if one exists.  

object_Comment  

Any user supplied Comments.  

gname  

The name of the replicated object group to which the object belongs.  

generation_status  

Status of whether the object needs to generate replication packages.  

min_communication  

N = send both OLD and NEW values for an updated view.  

trigflag  

Inline trigger flag. Y= trigger activated; N = trigger disabled.  

REPPARAMETER_COLUMN View

In addition to the information contained in the REPRESOLUTION view, the REPPARAMETER_COLUMN view also contains information about the columns that you indicated should be used to resolve the conflict. These are the column values that are passed as the LIST_OF_COLUMN_NAMES argument to the ADD_*_RESOLUTION procedures in the DBMS_REPCAT package.

Table 11-11: REPPARAMETER_COLUMN View
Column   Description  

sname  

The name of the schema containing the replicated table.  

oname  

The name of the replicated table.  

conflict_type  

The type of conflict that the routine is used to resolve: delete, uniqueness, or update.  

reference_name  

The object to which the routine applies. For delete conflicts, this is the table name. For uniqueness conflicts, this is the constraint name. For update conflicts, this is the column group name.  

sequence_no  

The order that resolution methods are applied, with 1 being applied first.  

method_name  

The name of an Oracle-supplied conflict resolution method. For user-supplied methods, this value is 'user function'.  

function_name  

For methods of type 'user function', the name of the user-supplied conflict resolution routine.  

priority_group  

For methods of type 'priority group', the name of the priority group.  

parameter_table_
name  

Defaults to object name of PL/SQL table containing columns passed to conflict resolution function.  

parameter_
column_name  

The name of the column used as the IN parameter for the conflict resolution routine.  

parameter_
sequence_no  

Ordering of column used as IN parameter.  

Note: The SNAME column is not present in the USER_ view.

REPPRIORITY View

The REPPRIORITY view displays the value and priority level of each priority group member. Priority group names must be unique within a replicated object group. Priority levels and values must each be unique within a given priority group.

Table 11-12: REPPRIORITY View
Column   Description  

sname  

The name of the replicated schema. Obsolete with release 7.3 or later.  

gname  

The name of the replicated object group.  

priority_group  

The name of the priority group or site priority group.  

priority  

The priority level of the member. The highest number has the highest priority.  

data_type  

The datatype of the values in the priority group.  

fixed_data_length  

The maximum length of values of datatype CHAR.  

char_value  

The value of the priority group member, if data_type = char.  

varchar2_value  

The value of the priority group member, if data_type = varchar2.  

number_value  

The value of the priority group member, if data_type = number.  

date_value  

The value of the priority group member, if data_type = date.  

raw_value  

The value of the priority group member, if data_type = raw.  

nchar_value  

The value of the priority group member, if data_type = nchar.  

nvarchar2_value  

The value of the priority group member, if data_type = nvarchar2.  

large_char_value  

The value of the priority group member, for blank-padded character strings over 255 characters.  

Note: The SNAME and GNAME columns are not present in the USER_ view.

REPPRIORITY_GROUP View

The REPPRIORITY_GROUP view lists the priority and site priority groups that you have defined for a replicated object group.

Table 11-13: REPPRIORITY_GROUP View
Column   Description  

sname  

The name of the replicated schema. Obsolete with release 7.3 or later. Not shown in USER views.  

gname  

The name of the replicated object group. Not shown in USER views.  

priority_group  

The name of the priority group or site priority group.  

data_type  

The datatype of the values in the priority group.  

fixed_data_length  

The maximum length for values of datatype CHAR.  

priority_Comment  

Any user-supplied Comments.  

REPPROP View

The REPPROP view indicates the technique used to propagate operations on an object to the same object at another master site. These operations may have resulted from a call to a stored procedure or procedure wrapper, or may have been issued against a table directly.

Table 11-14: REPPROP View
Column   Description  

sname  

The name of the schema containing the replicated object.  

oname  

The name of the replicated object.  

type  

The type of object being replicated.  

dblink  

The fully qualified database name of the master site to which changes are being propagated.  

how  

How propagation is performed. Values recognized are 'none' for the local master site, and 'synchronous' or 'asynchronous' for all others.  

propagate_
Comment  

Any user-supplied Comments.  

REPRESOLUTION View

The REPRESOLUTION view indicates the routines used to resolve update, unique or delete conflicts for each table replicated using row-level replication for a given schema.

Table 11-15: REPRESOLUTION View
Column   Description  

sname  

The name of the replicated schema.  

oname  

The name of the replicated table.  

conflict_type  

The type of conflict that the routine is used to resolve: delete, uniqueness, or update.  

reference_name  

The object to which the routine applies. For delete conflicts, this is the table name. For uniqueness conflicts, this is the constraint name. For update conflicts, this is the column group name.  

sequence_no  

The order that resolution methods are applied, with 1 being applied first.  

method_name  

The name of an Oracle-supplied conflict resolution method. For user-supplied methods, this value is 'user function'.  

function_name  

For methods of type 'user function', the name of the user-supplied conflict resolution routine.  

priority_group  

For methods of type 'priority group', the name of the priority group.  

resolution_
Comment  

Any user-supplied Comments.  

Note: The SNAME column is not present in the USER_ view.

REPRESOL_STATS_CONTROL View

The REPRESOL_STATS_CONTROL view lists information about statistics collection for conflict resolutions for all replicated tables in the database.

Table 11-16: REPRESOL_STATS_CONTROL View
Column   Description  

sname  

Owner of the table.  

oname  

Table name.  

created  

Timestamp for which statistics collection was first started.  

status  

Status of statistics collection: ACTIVE, CANCELLED  

status_update_date  

Timestamp for which the status was last updated.  

purged_date  

Timestamp for the last purge of statistics data.  

last_purged_start_date  

The last start date of the statistics purging date range.  

last_purged_end_date  

The last end date of the statistics purging date range.  

Note: The SNAME column is not present in the USER_ view.

REPRESOLUTION_METHOD View

The REPRESOLUTION_METHOD view lists all of the conflict resolution routines available in your current database. Initially, this view lists the standard routines provided with the advanced replication facility. As you create new user functions and add them as conflict resolution methods for an object in the database, these functions are added to this view.

Table 11-17: REPRESOLUTION_METHOD View
Column   Description  

conflict_type  

The type of conflict that the resolution routine is designed to resolve: update, uniqueness, or delete.  

method_name  

The name of the Oracle-supplied method, or the name of the user-supplied routine.  

REPRESOLUTION_STATISTICS View

The REPRESOLUTION_STATISTICS view lists information about successfully resolved update, uniqueness, and delete conflicts for all replicated tables. These statistics are only gathered for a table if you have called DBMS_REPCAT.REGISTER_STATISTICS.

Table 11-18: REPRESOLUTION_STATISTICS View
Column   Description  

sname  

The name of the replicated schema.  

oname  

The name of the replicated table.  

conflict_type  

The type of conflict that was successfully resolved: delete, uniqueness, or update.  

reference_name  

The object to which the conflict resolution routine applies. For delete conflicts, this is the table name. For uniqueness conflicts, this is the constraint name. For update conflicts, this is the column group name.  

method_name  

The name of an Oracle-supplied conflict resolution method. For user-supplied methods, this value is 'user function'.  

function_name  

For methods of type 'user function', the name of the user supplied conflict resolution routine.  

priority_group  

For methods of type 'priority group', the name of the priority group.  

primary_key_value  

A concatenated representation of the row's primary key.  

resolved_date  

Date on which the conflict for this row was resolved.  

Note: The SNAME column is not present in the USER_ view.

REPSITES View

The REPSITES view lists the members of each replicated object group.

Table 11-19: Columns in USER, ALL, and DBA REPSITES View
Column   Description  

gname  

The name of the replicated object group.  

dblink  

The database link to the master site for this object group.  

masterdef  

Indicates which of the dblinks is the master definition site.  

snapmaster  

Used by snapshot sites to indicate which of the dblinks to use when refreshing.  

master_Comment  

User-supplied Comments.  

master  

Is the site a master site for the replicated group? Y or N  

The DBA_REPSITES view has the following additional columns:

prop_updates  

Number of requested updates for master.  

my_dblink  

Used to detect problem after import. If Y, the dblink is the global name.  

REPGENOBJECTS View

The REPGENOBJECTS view describes objects generated to support replication.

Table 11-20: REPGENOBJECTS View
Column   Description  

Base_oname  

The object for which this object was generated  

Base_sname  

The base object's owner.  

Base type  

The type of the base object.  

Distributed  

Obsolete.  

Oname  

The name of the generated object  

Package-prefix  

The prefix for the package wrapper.  

Procedure-prefix  

Not used.  

Reason  

The reason the object was generated.  

Sname  

The name of the replicated schema.  

Type  

The type of the generated object.  

Deferred Transaction Views

Oracle provides several views for you to use in administering deferred transactions. These views provide information about each deferred transaction, such as the transaction destinations, the deferred calls that make up the transactions, and any errors encountered during attempted execution of the transaction. You should not modify the tables directly; use the procedures provided in the DBMS_DEFER and DBMS_DEFER_SYS packages.

DEFCALL View

The DEFCALL view records all deferred remote procedure calls.

Table 11-21: DEFCALL View
Column   Description  

callno  

Unique ID of call within a transaction.  

deferred_tran_id  

The unique ID of the associated transaction.  

schemaname  

The schema name of the deferred call.  

packagename  

The package name of the deferred call.  

procname  

The procedure name of the deferred call.  

argcount  

The number of arguments to the deferred call.  

DEFCALLDEST View

The DEFCALLDEST view lists the destinations for each deferred remote procedure call.

Table 11-22: DEFCALLDEST View
Column   Description  

callno  

Unique ID of call within a transaction.  

deferred_tran_id  

Corresponds to the deferred_tran_id in the DEFTRAN view. Each deferred transaction is made up of one or more deferred calls.  

dblink  

The fully qualified database name of the destination database.  

DEFDEFAULTDEST View

If you are not using Oracle's replication facility and do not supply a destination for a deferred transaction or the calls within that transaction, Oracle uses the DEFDEFAULTDEST view to determine the destination databases to which you want to defer a remote procedure call.

Table 11-23: DEFDEFAULTDEST View
Column   Description  

dblink  

The fully qualified database name to which to replicate a transaction.  

DEFERRCOUNT View

The DEFERRCOUNT view provides information about the error transactions for a given destination.

Table 11-24: DEFERRCOUNT View
Column   Description  

errcount  

Number of existing transactions that caused an error for the destination.  

destination  

Database link used to address destination.  

DEFERROR View

The DEFERROR view provides the ID of each transaction that could not be applied. You can use this ID to locate the queued calls associated with this transaction. These calls are stored in the DEFCALL view. You can use the procedures in the DBMS_DEFER_QUERY package to determine the arguments to the procedures listed in the DEFCALL view.

Table 11-25: DEFERROR View
Column   Description  

deferred_tran_id  

The ID of the transaction causing the error.  

callno  

Unique ID of call at deferred_tran_db.  

destination  

Database link used to address destination.  

error_number  

Oracle error number.  

error_msg  

Error message text.  

receiver  

Original receiver of the deferred transaction.  

origin_tran_db  

The database originating the deferred transaction.  

origin_tran_id  

The original ID of the transaction.  

start_time  

Time the original transaction was enqueued.  

DEFLOB View

The DEFLOB view stores the LOB parameters to deferred RPCs.

Table 11-26: DEFLOB View
Column   Description  

id  

Identifier of the LOB parameter.  

enq_tid  

Trnsaction ID for deferred RPC with this LOB parameter.  

blob_col  

The binary LOB parameter.  

clob_col  

The character LOB parameter.  

nclob_col  

The national character LOB parameter.  

DEFPROPAGATOR View

The DEFPROPAGATOR view displays information about the local propagator.

Table 11-27: DEFPROPAGATOR View
Column   Description  

username  

Username of the propagator.  

userid  

User ID of the propagator.  

status  

Status of the propagator.  

created  

Time when the propagator was registered.  

DEFSCHEDULE View

The DEFSCHEDULE view displays information about when a job is next scheduled to be executed.

Table 11-28: DEFSCHEDULE View
Column   Description  

dblink  

Fully qualified pathname to master database site for which you have scheduled periodic execution of deferred remote procedure calls.  

job  

Number assigned to job when you created it by calling DBMS_DEFER_SYS.SCHEDULE_EXECUTION. Query the WHAT column of USER_JOBS view to determine what is executed when the job is run.  

interval  

Function used to calculate the next time to push the deferred transaction queue to destination.  

next_date  

Next date that job is scheduled to be executed.  

last_date  

Last time the queue was pushed (or attempted to push) remote procedure calls to this destination.  

disabled  

Is propagation to destination disabled?  

last_txn_count  

Number of transactions pushed during last attempt.  

last_error_number  

Oracle error number from last push  

last_error_message  

Error message from last push.  

DEFTRAN View

The DEFTRAN view records all deferred transactions.

Table 11-29: DEFTRAN View
Column   Description  

deferred_tran_id  

The transaction ID that enqueued the calls.  

delivery_order  

An identifier that determines the order of deferred transactions in the queue. The identifier is derived from the system commit number of the originating or copying transaction.  

destination_list  

'R' or 'D'. 'R' indicates that the destinations are determined by the REPSCHEMA view. 'D' indicates that the destinations were determined by the DEFDEFAULTDEST view or the NODE_LIST argument to the TRANSACTION, CALL, or COPY procedures.  

start_time  

The time that the original transaction was enqueued.  

DEFTRANDEST View

The DEFTRANDEST view lists the destinations for a deferred transaction.

Table 11-30: DEFTRANDEST View
Column   Description  

deferred_tran_id  

The transaction ID of the transaction to replicate to the given database link.  

dblink  

The fully qualified database name of the destination database.  

delivery_order  

An identifier that determines the order of deferred transactions in the queue. The identifier is derived from the system commit number of the originating or copying transaction.  

Snapshot and Snapshot Refresh Group Views

Oracle provides the following views that have information about snapshots and snapshot refresh groups.

SNAPSHOTS View

The SNAPSHOTS catalog view lists information about all of the snapshots in a database.

Table 11-31: SNAPSHOTS View
Column   Description  

OWNER  

Owner of the snapshot.  

NAME  

Name of the view used by users and applications for querying and updating the snapshot.  

TABLE_NAME  

Table in which the snapshot is stored (it has an extra column for the master rowid).  

MASTER_VIEW  

View of the master table, owned by the snapshot owner, used for refreshes.  

MASTER_OWNER  

Owner of the master table.  

MASTER  

Master table that this snapshot copies.  

MASTER_LINK  

Database link name to the master site.  

CAN_USE_LOG  

YES if this snapshot can use a snapshot log, NO if this snapshot is too complex to use a log.  

UPDATABLE  

`YES' indicates snapshot is updatable; `NO' indicates read-only.  

LAST_REFRESH  

Date and time at the master site of the last refresh.  

ERROR  

Number of failed attempts since last successful attempt.  

TYPE  

Type of refresh for all automatic refreshes: COMPLETE, FAST, FORCE.  

NEXT  

Date function used to compute next refresh dates.  

START_WITH  

Date function used to compute next refresh dates.  

REFRESH_METHOD  

Values used to drive a fast or complete refresh of the snapshot.  

FR_OPERATIONS  

If 'REGENERATE', then fast refresh operations have not been generated.  

CR_OPERATIONS  

If 'REGENERATE', then complete refresh operations have not been generated.  

MASTER_ROLLBACK_SEG  

Rollback segment to be used during refresh at the master.  

REFRESH_GROUP  

Group identifier for consistent refresh.  

UPDATE_TRIG  

Name of the trigger that fills in the UPDATE_LOG for an updatable snapshot.  

UPDATE_LOG  

Name of the table that logs changes to an updatable snapshot.  

QUERY  

Query used to create the snapshot.  

Note: UPDATE_TRIG: NULL in Oracle8 because of internalized triggers; MASTER_VIEW: NULL in Oracle8, now obsolete.

REGISTERED_SNAPSHOTS View

This view describes local or remote snapshots of local tables.

Table 11-32: REGISTERED_SNAPSHOTS View
Column   Description  

OWNER  

Owner of the snapshot.  

NAME  

The name of the snapshot.  

SNAPSHOT_SITE  

Global name of the snapshot site.  

CAN_USE_LOG  

If NO, the snapshot is complex and cannot fast refresh.  

UPDATABLE  

If NO, the snapshot is read only.  

REFRESH_METHOD  

Whether the snapshot uses ROWIDs or primary key for fast refresh.  

SNAPSHOT_ID  

Identifier for the snapshot used by the master for fast refresh.  

QUERY_TXT  

Query defining the snapshot, if registered.  

VERSION  

Version of the snapshot.  

SNAPSHOTS_LOGS View

The SNAPSHOT_LOGS view describes all the snapshot logs in the database.

Table 11-33: SNAPSHOT_LOGS View
Column   Description  

LOG_OWNER  

Owner of the snapshot log  

MASTER  

Name of the master table for which changes are logged.  

LOG_TABLE  

Log table; with ROWIDs and timestamps of rows which changed in the master.  

LOG_TRIGGER  

An after-row trigger on the master which inserts rows into the log. NULL in Oracle 8 because of internalized triggers.  

ROWIDS  

If YES, the snapshot log records rowid information.  

PRIMARY_KEY  

If YES, the snapshot log records primary key information.  

FILTER_COLUMNS  

If YES, the snapshot log records filter column information.  

CURRENT_SNAPSHOTS  

One date per snapshot -- the date the snapshot of the master last refreshed.  

SNAPSHOT_ID  

Unique identifier of the snapshot.  

Note: The view shows one row for each snapshot using the log. However, there is only one for all the snapshots located at the master site. To find out which logs are used, query USER_SNAPSHOT_LOGS using unique and not selecting SNAPSHOT_ID and CURRENT_SNAPSHOTS.

REFRESH View

The REFRESH view lists each refresh group found in the database, and includes information about the refresh interval for each group.

Table 11-34: REFRESH View
Column   Description  

ROWNER  

Owner of the refresh group.  

RNAME  

Name of the refresh group.  

REFGROUP  

ID number of the refresh group.  

IMPLICIT_DESTROY  

Implicit delete flag. If this value is Y, Oracle deletes the refresh group after you have subtracted the last member from the group.  

JOB  

ID number of the job used to execute the automatic refresh of the snapshot group. You can use this information to query the USER_JOBS view for more information about the job.  

NEXT_DATE  

Date when the members of the group will next be refreshed.  

INTERVAL  

The function used to calculate the interval between refreshes.  

BROKEN  

Flag used to indicate a problem with the refresh group. If the value of the broken flag is Y, Oracle will not refresh the group, even if it is scheduled to be refreshed.  

PUSH_DEFERRED_RPC  

If Y, push changes to master before refresh.  

REFRESH_AFTER_ERRORS  

If Y, proceed with refresh despite errors when pushing deferred RPCs.  

ROLLBACK_SEG  

Name of rollback segment used at the snapshot site during refresh.  

PURGE_OPTION  

The method for purging the transaction queue after each push.  

PARALLELISM  

The level of parallelism for transaction propagation.  

HEAP_SIZE  

The heap size used for transaction propagation.  

REFRESH_CHILDREN View

The REFRESH_CHILDREN view lists the members of each refresh group owned by the user, and includes information about the refresh interval for each member.

Table 11-35: REFRESH_CHILDREN View
Column   Description  

OWNER  

Owner of the refresh group member.  

NAME  

Name of the refresh group member.  

TYPE  

Type of the refresh group member; for example, SNAPSHOT.  

ROWNER  

Owner of the refresh group.  

RNAME  

Name of the refresh group.  

REFGROUP  

ID number of the refresh group.  

IMPLICIT_DESTROY  

Implicit delete flag. If this value is Y, Oracle deletes the refresh group after you have subtracted the last member from the group.  

JOB  

ID number of the job used to execute the automatic refresh of the snapshot refresh group. You can use this information to query the USER_JOBS view for more information about the job.  

NEXT_DATE  

Date when the members of the group will next be refreshed.  

INTERVAL  

The function used to calculate the interval between refreshes.  

BROKEN  

Flag used to indicate a problem with the refresh group. If the value of the broken flag is Y, Oracle will not refresh the group, even if it is scheduled to be refreshed.  

PUSH_DEFERRED_RPC  

If Y, push changes to master before refresh.  

REFRESH_AFTER_ERRORS  

If Y, proceed with refresh despite errors when pushing deferred RPCs.  

ROLLBACK_SEG  

Name of rollback segment used at the snapshot site during refresh.  

PURGE_OPTION  

The method for purging the transaction queue after each push.  

PARALLELISM  

The level of parallelism for transaction propagation.  

HEAP_SIZE  

The heap size used for transaction propagation.  




Prev

Next
Oracle
Copyright © 1997 Oracle Corporation.

All Rights Reserved.

Library

Product

Contents

Index