9
Data Dictionary Views

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

• Replication Catalog Views.

• Deferred Transaction Views.

• Snapshots and Snapshot Refresh Group Views.

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 9-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 among these views.

This section contains information about the following views:

• REPGROUP View

• REPCATLOG View

• REPCAT_REFRESH_TEMPLATES View

• REPCAT_TEMPLATE_OBJECTS View

• REPCAT_TEMPLATE_PARMS View

• REPCAT_TEMPLATE_SITES View

• REPCAT_USER_AUTHORIZATIONS View

• REPCAT_USER_PARM_VALUES View

• REPCOLUMN View

• REPCOLUMN_GROUP View

• REPCONFLICT View

• REPDDL View

• REPGROUP_PRIVILEGES View

• REPGROUPED_COLUMN View

• REPKEY_COLUMNS View

• REPOBJECT View

• REPPARAMETER_COLUMN View

• REPPRIORITY View

• REPPRIORITY_GROUP View

• REPPROP View

• REPRESOLUTION View

• REPRESOL_STATS_CONTROL View

• REPRESOLUTION_METHOD View

• REPRESOLUTION_STATISTICS View

• REPSITES View

• REPGENOBJECTS View

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 9-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.
fname	Flavor name.
rpc_processing_disabled	'N' indicates that this site can receive and apply deferred RPCs. 'Y' indicates that this site can NOT receive and apply deferred RPCs.

Figure 9-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 9-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	Name of the user 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.

REPCAT_REFRESH_TEMPLATES View

This view contains global information about the template, such as the template name, template owner, what refresh group the template objects will belong to, and the type of template (private vs. public).

When the DBA adds snapshot definitions to the template container, the DBA will reference the appropriate refresh_template_name. Any snapshots added to a specific template will be added to the refresh group specified in the REFRESH_GROUP_NAME parameter.

Furthermore, deployment templates created with the public parameter will be available to all users who can connect to the master site. Deployment templates created as private will be limited to those users listed in the DBA_REPCAT_USER_AUTHORIZATIONS table.

Table 9-3 REPCAT_REFRESH_TEMPLATES View

Column	Description
refresh_template_name	Name of the deployment template.
owner	Owner of the deployment template.
refresh_group_name	Name of the refresh group that template objects will be added to during the instantiation process.
template_comment	User supplied comment.
public_template	'Y' if the deployment template is public. 'N' if the deployment template is private.

REPCAT_TEMPLATE_OBJECTS View

The DBA_REPCAT_TEMPLATE_OBJECTS view contains the individual object definitions that are contained in a deployment template. Individual objects are added to a template by specifying the target template in the REFRESH_TEMPLATE_NAME parameter.

DDL_TEXT can contain variables to create parameterized templates. Variables are created by placing an ampersand (&) at the beginning of the variable name (i.e. &region). Parameterized templates allow for greater flexibility during the template instantiation process (i.e. in defining data sets specific for a snapshot site).

When the object is added to the template, the specified DDL is examined and if any parameters have been defined, Oracle will automatically add the parameter to the DBA_REPCAT_TEMPLATE_PARMS table.

Table 9-4 REPCAT_TEMPLATE_OBJECTS View

Column	Description
refresh_template_name	The name of the deployment template.
object_name	The name of the deployment template object.
object_type	The object type of the deployment template object.
ddl_text	The DDL that is executed to create the deployment template object. Object DDL is stored as a CLOB (see the notes below).
master_rollback_seg	The name of the rollback segment that is used during the instantiation of the deployment template object.
flavor_id	The flavor ID of the deployment template object.
derived_from_sname	If applicable, displays the schema that contains the object that the template object was created from.
derived_from_oname	If applicable, displays the name of the object that the template object was created from.

Note: Since the ddl_text parameter is defined as a CLOB, you will receive an error if you simply try to perform a SELECT on the DBA_REPCAT_TEMPLATE_OBJECTS view. If you don't need to see the object DDL, use the following select statement (be sure to exclude the ddl_text parameter):

SELECT refresh_template_name, object_name, object_type, master_rollback_seg, 
flavor_id FROM dba_repcat_template_objects;

The following script uses cursors and the DBMS_LOB package to view the entire contents of the DBA_REPCAT_TEMPLATE_OBJECTS view. For more information on using cursors see Oracle8i Application Developer's Guide - Fundamentals. For more information on using the DBMS_LOB package and LOBs in general, also see Oracle8i Application Developer's Guide - Fundamentals.

Use the following script to view the entire contents of DBA_REPCAT_TEMPLATE_OBJECTS view, including the ddl_text column:

SET SERVEROUTPUT ON

DECLARE
  CURSOR mycursor IS
        SELECT refresh_template_name, object_name, object_type, ddl_text,
          master_rollback_seg, flavor_id
          FROM dba_repcat_template_objects;
  tempstring VARCHAR2(1000);
  len NUMBER;
BEGIN
  FOR myrec IN mycursor LOOP
        len := DBMS_LOB.GETLENGTH(myrec.ddl_text);
        DBMS_LOB.READ(myrec.ddl_text, len, 1, tempstring);
        DBMS_OUTPUT.PUT_LINE(myrec.refresh_template_name||' '||
          myrec.object_name||' '||myrec.object_type||' '||tempstring||' '||
          myrec.master_rollback_seg||' '||myrec.flavor_id);
  END LOOP;
END;
/

REPCAT_TEMPLATE_PARMS View

Parameters defined in the object DDL (see above) for a specific template are stored in the DBA_REPCAT_TEMPLATE_PARMS table. As previously stated, when an object is added to a template, the DDL is examined for variables; any found parameters are automatically added to this view.

You can also define default parameter values and a prompt string in this view (these make the templates more user friendly during the instantiation process).

Table 9-5 REPCAT_TEMPLATE_PARMS View

Column	Description
refresh_template_name	The name of the deployment template.
owner	The owner of the deployment template.
refresh_group_name	Name of the refresh group that template objects will be added to during the instantiation process.
template_comment	User specified comments.
public_template	'Y' if the deployment template is public. 'N' if the deployment template is private.
parameter_name	The name of the parameter.
default_parm_value	The default parameter value. The default_parm_value is stored as a CLOB (see the notes below).
prompt_string	The prompt string for the parameter (under certain conditions, this prompt string will be displayed to the user when requesting a parameter value).
user_override	'Y' if the user can override the default parameter value. 'N' if the user can not override the default parameter value.

Note: Since the default_parm_value parameter is defined as a CLOB, you will receive an error if you simply try to perform a SELECT on the DBA_REPCAT_TEMPLATE_PARMS view. If you don't need to see the default parameter value, use the following select statement (be sure to exclude the default_parm_value parameter):

SELECT refresh_template_name, owner, refresh_group_name, template_comment, 
public_template, parameter_name, prompt_string, user_override FROM dba_repcat_
template_parms;

The following script uses cursors and the DBMS_LOB package to view the entire contents of the DBA_REPCAT_TEMPLATE_PARMS view. For more information on using cursors see Oracle8i Application Developer's Guide - Fundamentals. For more information on using the DBMS_LOB package and LOBs in general, also see Oracle8i Application Developer's Guide - Fundamentals.

Use the following script to view the entire contents of DBA_REPCAT_TEMPLATE_PARMS view, including the default_parm_value column:

SET SERVEROUTPUT ON

DECLARE
  CURSOR mycursor IS
        SELECT refresh_template_name, owner, refresh_group_name,
          template_comment, public_template, parameter_name, default_parm_value,
          prompt_string, user_override
          FROM dba_repcat_template_parms;
  tempstring VARCHAR2(1000);
  len NUMBER;
BEGIN
  FOR myrec IN mycursor LOOP
        len := DBMS_LOB.GETLENGTH(myrec.default_parm_value);
        DBMS_LOB.READ(myrec.default_parm_value, len, 1, tempstring);
        DBMS_OUTPUT.PUT_LINE(myrec.refresh_template_name||' '||
          myrec.owner||' '||myrec.refresh_group_name||' '||
          myrec.template_comment||' '||myrec.public_template||' '||
          myrec.parameter_name||' '||tempstring||' '||myrec.prompt_string||' '||
          myrec.user_override);
  END LOOP;
END;
/

REPCAT_TEMPLATE_SITES View

The DBA_REPCAT_TEMPLATE_SITES view provides the DBA with information about the current status of template instantiation amongst the sites of a enterprise network. Specifically, the DBA will be able to monitor the installation and deletion of templates at specific sites.

Table 9-6 REPCAT_TEMPLATE_SITES View

Column	Description
refresh_template_name	The name of the deployment template.
refresh_group_name	Name of the refresh group that template objects will be added to during the instantiation process.
template_owner	Name of the user that is considered the owner of the deployment template.
user_name	The name of the user that instantiated the deployment template.
site_name	Target snapshot site of the deployment template.
repapi_site_id	The ID of the REPAPI site that has instantiated the displayed deployment template.
status	Displays the status of the deployment template at the target snapshot site: 0 = Not Installed 1 = Installed -1 = Installed with errors

REPCAT_USER_AUTHORIZATIONS View

If a template has been specified for private use, the authorized user list is displayed in the DBA_REPCAT_USER_AUTHORIZATIONS view. Users contained in this view will have the ability to instantiate the specified table, while users not on the list will not be able to instantiate the template.

Table 9-7 REPCAT_USER_AUTHORIZATIONS View

Column	Description
refresh_template_name	The name of the deployment template that a user has been authorized to instantiate.
owner	The name of the owner of the deployment template.
refresh_group_name	Name of the refresh group that template objects will be added to during the instantiation process.
template_comment	User specified comment.
public_template	'Y' if the deployment template is public. 'N' if the deployment template is private.
user_name	The name of the user that has been authorized to instantiate the specified deployment template.

REPCAT_USER_PARM_VALUES View

The DBA has the option of building a table of user parameters prior to distributing the template for instantiation. When a template is instantiated by a specified user, the values stored in the DBA_REPCAT_USER_PARM_VALUES table for the specified user will automatically be used.

Table 9-8 REPCAT_USER_PARM_VALUES View

Column	Description
refresh_template_name	The name of the deployment template that a user parameter value has been defined for.
owner	The name of the owner of the deployment template.
refresh_group_name	Name of the refresh group that the template objects will be added to during the instantiation process.
template_comment	User specified comment.
public_template	'Y' if the deployment template is public. 'N' if the deployment template is private.
parameter_name	The name of the parameter that a user parameter value has been defined for.
default_parm_value	The default value for the parameter. The default_parm_value is stored as a CLOB (see the notes below).
prompt_string	The prompt string for the parameter.
parm_value	The parameter value that has been defined for the specified user. The parm_value is stored as a CLOB (see the notes below).
user_name	The name of the user that the specified parameter value has been defined for.

Note: Since the default_parm_value and the parm_value parameters are defined as CLOBs, you will receive an error if you simply try to perform a SELECT on the DBA_REPCAT_USER_PARM_VALUES view. If you don't need to see the default or user parameter values, use the following select statement (be sure to exclude the default_parm_value and the parm_value parameters):

SELECT refresh_template_name, owner, refresh_group_name, template_comment, 
public_template, parameter_name, prompt_string, user_name FROM dba_repcat_user_
parm_values;

The following script uses cursors and the DBMS_LOB package to view the entire contents of the DBA_REPCAT_USER_PARM_VALUES view. For more information on using cursors see Oracle8i Application Developer's Guide - Fundamentals. For more information on using the DBMS_LOB package and LOBs in general, also see Oracle8i Application Developer's Guide - Fundamentals.

Use the following script to view the entire contents of DBA_REPCAT_TEMPLATE_PARMS view, including the default_parm_value column:

SET SERVEROUTPUT ON

DECLARE
  CURSOR mycursor IS
        SELECT refresh_template_name, owner, refresh_group_name,
          template_comment, public_template, parameter_name, default_parm_value,
          prompt_string, parm_value, user_name
          FROM dba_repcat_user_parm_values;
  tempstring VARCHAR2(1000);
  tempstring2 varchar2(1000);
  len NUMBER;
BEGIN
  FOR myrec IN mycursor LOOP
        len := DBMS_LOB.GETLENGTH(myrec.default_parm_value);
        DBMS_LOB.READ(myrec.default_parm_value, len, 1, tempstring);
        DBMS_OUTPUT.PUT_LINE(myrec.refresh_template_name||' '||
          myrec.owner||' '||myrec.refresh_group_name||' '||
          myrec.template_comment||' '||myrec.public_template||' '||
          myrec.parameter_name||' '||tempstring||' '||myrec.prompt_string||' '||
          tempstring2||' '||myrec.user_name);
  END LOOP;
END;
/

REPCOLUMN View

The REPCOLUMN view lists the replicated columns for a table.

Table 9-9 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 compares the old value of the column in replicated deletes.
compare_old_on_update	Indicates whether Oracle compares the old value of the column in replicated updates.
send_old_on_delete	Indicates whether Oracle sends the old value of the column in replicated deletes.
send_old_on_update	Indicates whether Oracle sends the old value of the column in replicated updates.
ctype	Displays the column type.
data_length	Displays the length of the column in bytes.
data_precision	Displays the column precision in terms of decimal digits for NUMBER columns or binary digits for FLOAT columns.
data_scale	Displays the digits to right of decimal point in a number.
nullable	Indicates if the column allow NULL values.
character_set_name	If applicable, displays the name of character set for the column.

REPCOLUMN_GROUP View

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

Table 9-10 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 9-11 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 9-12 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.

REPGROUP_PRIVILEGES View

The REPGROUP_PRIVILEGES view lists information about users who are registered for object group privileges.

Table 9-13 REPGENERATED View

Column	Description
username	Displays the name of the user.
gname	Displays the name of the replicated object group.
created	Displays the date that the object group was registered.
receiver	Indicates whether the user has receiver privileges.
proxy_snapadmin	Indicates whether the user has proxy_snapadmin privileges.

REPGROUPED_COLUMN View

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

Table 9-14 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 9-15 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 9-16 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.
internal_package_exists	Y = internal package exists N = internal package does not exist
replication_trigger_exists	Y = internal replication trigger exists N = internal replication trigger does not exist

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 9-17 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	Displays the name of the table that the parameter column belongs to.
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 9-18 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 9-19 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 9-20 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 9-21 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 9-22 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 9-23 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 9-24 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 9-25 Columns in USER, ALL, and DBA REPSITES View

Column	Description
gname	The name of the replicated object group.
dblink	The database link to a 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	Encoding of propagating technique 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 9-26 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	The procedure prefix for the package wrapper.
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

• DEFDEFAULTDEST View

• DEFERRCOUNT View

• DEFCALLDEST View

• DEFERROR View

• DEFLOB View

• DEFPROPAGATOR View

• DEFSCHEDULE View

• DEFTRAN View

• DEFTRANDEST View

DEFCALL View

The DEFCALL view records all deferred remote procedure calls.

Table 9-27 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. For a replicated table, this may refer to the table name.
procname	The procedure name of the deferred call. For a replicated table, this may refer to an operation name.
argcount	The number of arguments to the deferred call.

DEFCALLDEST View

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

Table 9-28 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 9-29 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 9-30 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 9-31 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 9-32 DEFLOB View

Column	Description
id	Identifier of the LOB parameter.
deferred_tran_id	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 9-33 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 9-34 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_PUSH. 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 9-35 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 transaction.
destination_list	'R' or 'D'. 'R' indicates that the destinations are determined by the REPSITES view. 'D' indicates that the destinations were determined by the DEFDEFAULTDEST view or the NODE_LIST argument to the TRANSACTION or CALL procedures.
start_time	The time that the original transaction was enqueued.

DEFTRANDEST View

The DEFTRANDEST view lists the destinations for a deferred transaction.

Table 9-36 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 transaction.

Snapshots and Snapshot Refresh Group Views

The following views provide information about snapshots and snapshot refresh groups.

• SNAPSHOTS View

• REGISTERED_SNAPSHOTS View

• SNAPSHOT_LOGS View

• SNAPSHOT_REFRESH_TIMES View

• REFRESH View

• REFRESH_CHILDREN View

SNAPSHOTS View

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

Table 9-37 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.
STATUS	Displays the status of the snapshot. Valid values are: VALID: Snapshot is a read-consistent replica of the target master table from a specific point-in-time. INVALID: Snapshot is NOT a read-consistent replica of the target master table from a specific point-in-time. UNKNOWN: The read-consistent status of the snapshot is not known.
REFRESH_MODE	Displays how the snapshot will be refreshed. Valid values are PERIODIC and DEMAND.

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

REGISTERED_SNAPSHOTS View

This view describes local or remote snapshots of local tables.

Table 9-38 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.

SNAPSHOT_LOGS View

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

Table 9-39 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.

SNAPSHOT_REFRESH_TIMES View

The REFRESH_TIMES view lists the date and time of the last refresh.

Table 9-40 SNAPSHOT_REFRESH _TIMES View

Column	Description
OWNER	Owner of the snapshot.
NAME	Name of the snapshot view.
MASTER_OWNER	Owner of the master table.
MASTER	Name of the master table.
LAST_REFRESH	The date and time of the last refresh.

REFRESH View

The REFRESH view lists each refresh group in the database, and describes refresh intervals for each group.

Table 9-41 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 9-42 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.

---