34
DBMS_REPCAT

DBMS_REPCAT provides routines to administer and update the replication catalog and environment.

Summary of Subprograms

Table 34-1 DBMS_REPCAT Package Subprograms

Subprogram	Description
ADD_GROUPED_COLUMN procedure	Adds members to an existing column group.
ADD_MASTER_DATABASE procedure	Adds another master site to your replicated environment.
ADD_PRIORITY_datatype procedure	Adds a member to a priority group.
ADD_SITE_PRIORITY_SITE procedure	Adds a new site to a site priority group.
ADD_conflicttype_RESOLUTION procedure	Designates a method for resolving an update, delete, or uniqueness conflict.
ALTER_MASTER_PROPAGATION procedure	Alters the propagation method for a given object group at a given master site.
ALTER_MASTER_REPOBJECT procedure	Alters an object in your replicated environment.
ALTER_PRIORITY procedure	Alters the priority level associated with a given priority group member.
ALTER_PRIORITY_datatype procedure	Alters the value of a member in a priority group.
ALTER_SITE_PRIORITY procedure	Alters the priority level associated with a given site.
ALTER_SITE_PRIORITY_SITE procedure	Alters the site associated with a given priority level.
ALTER_SNAPSHOT_PROPAGATION procedure	Alters the propagation method for a given object group at the current snapshot site.
CANCEL_STATISTICS procedure	Stops collecting statistics about the successful resolution of update, uniqueness, and delete conflicts for a table.
COMMENT_ON_COLUMN_GROUP procedure	Updates the comment field in the `RepColumn_Group` view for a column group.
COMMENT_ON_PRIORITY_ GROUP/PRIORITY procedure	Updates the comment field in the `REPPRIORITY_GROUP` view for a (site) priority group.
COMMENT_ON_REPGROUP procedure	Updates the comment field in the `REPGROUP` view for a replicated object group.
COMMENT_ON_REPSITES procedure	Updates the comment field in the `RepSite` view for a replicated site.
COMMENT_ON_REPOBJECT procedure	Updates the comment field in the `RepObject` view for a replicated object.
COMMENT_ON_conflicttype_ RESOLUTION procedure	Updates the comment field in the `RepResolution` view for a conflict resolution routine.
CREATE_MASTER_REPGROUP procedure	Creates a new, empty, quiesced master replication object group.
CREATE_MASTER_REPOBJECT procedure	Indicates that an object is a replicated object.
CREATE_SNAPSHOT_REPGROUP procedure	Creates a new, empty snapshot replication object group in your local database.
CREATE_SNAPSHOT_REPOBJECT procedure	Adds a replicated object to your snapshot site.
DEFINE_COLUMN_GROUP procedure	Creates an empty column group
DEFINE_PRIORITY_GROUP procedure	Creates a new priority group for a replicated object group.
DEFINE_SITE_PRIORITY procedure	Creates a new site priority group for a replicated object group.
DO_DEFERRED_REPCAT_ADMIN procedure	Executes the local outstanding deferred administrative procedures for the given replicated object group at the current master site, or for all master sites.
DROP_COLUMN_GROUP procedure	Drops a column group.
DROP_GROUPED_COLUMN procedure	Removes members from a column group.
DROP_MASTER_REPGROUP procedure	Drops a replicated object group from your current site.
DROP_MASTER_REPOBJECT procedure	Drops a replicated object from a replicated object group.
DROP_PRIORITY procedure	Drops a member of a priority group by priority level.
DROP_PRIORITY_GROUP procedure	Drops a priority group for a given replicated object group.
DROP_PRIORITY_datatype procedure	Drops a member of a priority group by value.
DROP_SITE_PRIORITY procedure	Drops a site priority group for a given replicated object group.
DROP_SITE_PRIORITY_SITE procedure	Drops a given site, by name, from a site priority group.
DROP_SNAPSHOT_REPGROUP procedure	Drops a snapshot site from your replicated environment.
DROP_SNAPSHOT_REPOBJECT procedure	Drops a replicated object from a snapshot site.
DROP_conflicttype_ RESOLUTION procedure	Drops an update, delete, or uniqueness conflict resolution routine.
EXECUTE_DDL procedure	Supplies DDL that you want to have executed at each master site.
GENERATE_REPLICATION_ SUPPORT procedure	Generates the triggers, packages, and procedures needed to support replication.
GENERATE_SNAPSHOT_SUPPORT procedure	Activates triggers and generate packages needed to support the replication of updatable snapshots or procedural replication.
MAKE_COLUMN_GROUP procedure	Creates a new column group with one or more members.
PURGE_MASTER_LOG procedure	Removes local messages in the `RepCatLog` associated with a given identification number, source, or replicated object group.
PURGE_STATISTICS procedure	Removes information from the `RepResolution_Statistics` view.
REFRESH_SNAPSHOT_REPGROUP procedure	Refreshes a snapshot site object group with the most recent data from its associated master site.
REGISTER_SNAPSHOT_REPGROUP procedure	Facilitates the administration of snapshots at their respective master sites by inserting/modifying/deleting from `repcat_repsite`.
REGISTER_STATISTICS procedure	Collects information about the successful resolution of update, delete and uniqueness conflicts for a table.
RELOCATE_MASTERDEF procedure	Changes your master definition site to another master site in your replicated environment.
REMOVE_MASTER_DATABASES procedure	Removes one or more master databases from a replicated environment.
REPCAT_IMPORT_CHECK procedure	Ensures that the objects in the replicated object group have the appropriate object identifiers and status values after you perform an export/import of a replicated object or an object used by the advanced replication facility.
RESUME_MASTER_ACTIVITY procedure	Resumes normal replication activity after quiescing a replicated environment.
SUSPEND_MASTER_ACTIVITY procedure	Suspends replication activity for an object group
SWITCH_SNAPSHOT_MASTER procedure	Changes the master database of a snapshot replicated object group to another master site.
UNREGISTER_SNAPSHOT_ REPGROUP procedure	Facilitates the administration of snapshots at their respective master sites by inserting/modifying/deleting from `repcat$_repsite`.
VALIDATE function	Validates the correctness of key conditions of a multiple master replication environment.
WAIT_MASTER_LOG procedure	Determines whether changes that were asynchronously propagated to a master site have been applied.

ADD_GROUPED_COLUMN procedure

This procedure adds members to an existing column group. You must call this procedure from the master definition site.

Syntax

DBMS_REPCAT.ADD_GROUPED_COLUMN ( 
   sname                 IN   VARCHAR2,
   oname                 IN   VARCHAR2,
   column_group          IN   VARCHAR2,
   list_of_column_names  IN   VARCHAR2 | DBMS_REPCAT.VARCHAR2S);

Parameters

Table 34-2 ADD_GROUPED_COLUMN Procedure Parameters

Parameter	Description
sname	Schema in which the replicated table is located.
oname	Name of the replicated table with which the column group is associated.
column_group	Name of the column group to which you are adding members.
list_of_column_names	Names of the columns that you are adding to the designated column group. This can either be a comma-separated list or a PL/SQL table of column names. The PL/SQL table must be of type `dbms_repcat`.`varchar2s`. Use the single value '*' to create a column group that contains all of the columns in your table.

Exceptions

Table 34-3 ADD_GROUPED_COLUMN Procedure Exceptions

Exception	Description
nonmasterdef	Invocation site is not the masterdef site.
missingobject	Given table does not exist.
missinggroup	Given column group does not exist.
missingcolumn	Given column does not exist in the designated table.
duplicatecolumn	Given column is already a member of another column group.
missingschema	Given schema does not exist.
notquiesced	Object group that the given table belongs to is not quiesced.

ADD_MASTER_DATABASE procedure

This procedure adds another master site to your replicated environment. This procedure regenerates all the triggers and their associated packages at existing master sites. You must call this procedure from the master definition site.

Syntax

DBMS_REPCAT.ADD_MASTER_DATABASE (
   gname                 IN   VARCHAR2,
   master                IN   VARCHAR2, 
   use_existing_objects  IN   BOOLEAN  := TRUE, 
   copy_rows             IN   BOOLEAN  := TRUE,
   comment               IN   VARCHAR2 := '',
   propagation_mode      IN   VARCHAR2 := 'ASYNCHRONOUS',
   fname                 IN   VARCHAR2 := NULL);

Parameters

Table 34-4 ADD_MASTER_DATABASE Procedure Parameters

Parameter	Description
gname	Name of the object group being replicated. This object group must already exist at the master definition site.
master	Fully qualified database name of the new master database.
use_existing_objects	Indicate `TRUE` if you want to reuse any objects of the same type and shape that already exist in the schema at the new master site. See "Using Multimaster Replication" in the Oracle8i Replication manual for more information on how these changes are applied.
copy_rows	Indicate `TRUE` if you want the initial contents of a table at the new master site to match the contents of the table at the master definition site.
comment	This is added to the `MASTER_COMMENT` field of the `RepSites` view.
propagation_mode	Method of forwarding changes to and receiving changes from new master database. Accepted values are `SYNCHRONOUS` and `ASYNCHRONOUS`.
fname	This system parameter is for internal use only. Do not set the parameter unless so directed by Oracle Worldwide Support.

Exceptions

Table 34-5 ADD_MASTER_DATABASE Procedure Exceptions

Exception	Description
nonmasterdef	Invocation site is not the master definition site.
notquiesced	Replicated object group has not been suspended.
missingrepgroup	Object group does not exist at the given database site.
commfailure	New master is not accessible.
typefailure	An incorrect propagation mode was specified.
notcompat	Compatibility mode must be 7.3.0.0 or greater.
duplrepgrp	Master site already exists.

ADD_PRIORITY_datatype procedure

This procedure adds a member to a priority group. You must call this procedure from the master definition site. The procedure that you must call is determined by the datatype of your priority column. You must call this procedure once for each of the possible values of the priority column.

See Also:
For additional information, see "Conflict Resolution" in the Oracle8i Replication manual.

Syntax

DBMS_REPCAT.ADD_PRIORITY_datatype (
   gname              IN   VARCHAR2, 
   pgroup             IN   VARCHAR2, 
   value              IN   datatype, 
   priority           IN   NUMBER);

where datatype:

{ NUMBER
| VARCHAR2
| CHAR
| DATE
| RAW
| NCHAR
| NVARCHAR2 }

Parameters

Table 34-6 ADD_PRIORITY_datatype Procedure Parameters

Parameter	Description
gname	Replicated object group for which you are creating a priority group.
pgroup	Name of the priority group.
value	Value of the priority group member. This would be one of the possible values of the associated `priority` column of a table using this priority group.
priority	Priority of this value. The higher the number, the higher the priority.

Exceptions

Table 34-7 ADD_PRIORITY_datatype Procedure Exceptions

Exception	Description
nonmasterdef	Invocation site is not the masterdef site.
duplicatevalue	Given value already exists in the priority group.
duplicatepriority	Given priority already exists in the priority group.
missingrepgroup	Given replicated object group does not exist.
missingprioritygroup	Given priority group does not exist.
typefailure	Given value has the incorrect datatype for the priority group.
notquiesced	Given replicated object group is not quiesced.

ADD_SITE_PRIORITY_SITE procedure

This procedure adds a new site to a site priority group. You must call this procedure from the master definition site.

See Also:
For additional information, see "Conflict Resolution" in the Oracle8i Replication manual.

Syntax

DBMS_REPCAT.ADD_SITE_PRIORITY_SITE (
   gname          IN   VARCHAR2, 
   name           IN   VARCHAR2,
   site           IN   VARCHAR2,
   priority       IN   NUMBER);

Parameters

Table 34-8 ADD_SITE_PRIORITY_SITE Procedure Parameters

Parameter	Description
gname	Replicated object group for which you are adding a site to a group.
name	Name of the site priority group to which you are adding a member.
site	Global database name of the site that you are adding.
priority	Priority level of the site that you are adding. A higher number indicates a higher priority level.

Exceptions

Table 34-9 ADD_SITE_PRIORITY_SITE Procedure Exceptions

Exception	Description
nonmasterdef	Invocation site is not the masterdef site.
missingrepgroup	Given replicated object group does not exist.
missingpriority	Given site priority group does not exist.
duplicatepriority	Given priority level already exists for another site in the group.
duplicatevalue	Given site already exists in the site priority group.
notquiesced	Replicated object group is not quiesced.

ADD_conflicttype_RESOLUTION procedure

This procedure designates a method for resolving an update, delete, or uniqueness conflict. You must call these procedures from the master definition site. The procedure that you need to call is determined by the type of conflict that the routine resolves.

Conflict Type	Procedure Name
update	ADD_UPDATE_RESOLUTION
uniqueness	ADD_UNIQUE_RESOLUTION
delete	ADD_DELETE_RESOLUTION

See Also:
For more information about designating methods to resolve update conflicts, selecting uniqueness conflict resolution methods, and, assigning delete conflict resolution methods see "Conflict Resolution" in the Oracle8i Replication manual.

Syntax

DBMS_REPCAT.ADD_UPDATE_RESOLUTION (
   sname                  IN   VARCHAR2, 
   oname                  IN   VARCHAR2, 
   column_group           IN   VARCHAR2,
   sequence_no            IN   NUMBER,
   method                 IN   VARCHAR2, 
   parameter_column_name  IN   VARCHAR2 | DBMS_REPCAT.VARCHAR2S, 
   priority_group         IN   VARCHAR2     := NULL,
   function_name          IN   VARCHAR2     := NULL,
   comment                IN   VARCHAR2     := NULL);

DBMS_REPCAT.ADD_DELETE_RESOLUTION (
   sname                  IN   VARCHAR2, 
   oname                  IN   VARCHAR2, 
   sequence_no            IN   NUMBER,
   parameter_column_name  IN   VARCHAR2 | DBMS_REPCAT.VARCHAR2S, 
   function_name          IN   VARCHAR2,
   comment                IN   VARCHAR2     := NULL,
   method                 IN   VARCHAR2     := 'USER FUNCTION');

DBMS_REPCAT.ADD_UNIQUE_RESOLUTION(
   sname                 IN   VARCHAR2, 
   oname                 IN   VARCHAR2, 
   constraint_name       IN   VARCHAR2,
   sequence_no           IN   NUMBER,
   method                IN   VARCHAR2, 
   parameter_column_name IN   VARCHAR2 | DBMS_REPCAT.VARCHAR2S, 
   function_name         IN   VARCHAR2     := NULL,
   comment               IN   VARCHAR2     := NULL);

Parameters

Table 34-10 ADD_conflicttype_RESOLUTION Procedure Parameters

Parameter	Description
sname	Name of the schema containing the table to be replicated.
oname	Name of the table for which you are adding a conflict resolution routine.
column_group	Name of the column group for which you are adding a conflict resolution routine. Column groups are required for update conflict resolution routines only.
constraint_name	Name of the unique constraint or unique index for which you are adding a conflict resolution routine. Use the name of the unique index if it differs from the name of the associated unique constraint. Constraint names are required for uniqueness conflict resolution routines only.
sequence_no	Order in which the designated conflict resolution methods should be applied.
method	Type of conflict resolution routine that you want to create. This can be the name of one of the standard routines provided with advanced replication, or, if you have written your own routine, you should choose `USER` `FUNCTION`, and provide the name of your routine as the `FUNCTION_NAME` argument. The methods supported in this release are: `MINIMUM`, `MAXIMUM`, `LATEST` `TIMESTAMP`, `EARLIEST` `TIMESTAMP`, `ADDITIVE`, `AVERAGE`, `PRIORITY` `GROUP`, `SITE` `PRIORITY`, `OVERWRITE`, and `DISCARD` (for update conflicts) and `APPEND` `SITE` `NAME`, `APPEND` `SEQUENCE` `NUMBER`, and `DISCARD` (for uniqueness conflicts). There are no standard methods for delete conflicts.
parameter_column_ name	Name of the columns used to resolve the conflict. The standard methods operate on a single column. For example, if you are using the `LATEST` `TIMESTAMP` method for a column group, then you should pass the name of the column containing the timestamp value as this argument. If your are using a `USER` `FUNCTION`, then you can resolve the conflict using any number of columns. This argument accepts either a comma separated list of column names, or a PL/SQL table of type dbms_repcat.varchar2s. The single value '' indicates that you want to use all of the columns in the table (or column group, for update conflicts) to resolve the conflict. If you specify '', then the columns are passed to your function in alphabetical order.
priority_group	If you are using the `PRIORITY` `GROUP` or `SITE` `PRIORITY` update conflict resolution method, then you must supply the name of the priority group that you have created. See "Conflict Resolution" in the Oracle8i Replication manual. If you are using a different method, then you can use the default value for this argument, `NULL`. This argument is applicable to update conflicts only.
function_name	If you selected the `USER` `FUNCTION` method, or if you are adding a delete conflict resolution routine, then you must supply the name of the conflict resolution routine that you have written. If you are using one of the standard methods, then you can use the default value for this argument, `NULL`.
comment	This user comment is added to the `RepResolution` view.

Exceptions

Table 34-11 ADD_conflicttype_RESOLUTION Procedure Exceptions

Exception	Description
nonmasterdef	Invocation site is not the masterdef site.
missingobject	Given object does not exist as a table in the given schema using row-level replication.
missingschema	Given schema does not exist.
missingcolumn	Column that you specified as part of the `PARAMETER_COLUMN_NAME` argument does not exist.
missinggroup	Given column group does not exist.
missingprioritygroup	priority group that you specified does not exist for the table.
invalidmethod	Resolution method that you specified is not recognized.
invalidparameter	Number of columns that you specified for the `PARAMETER_COLUMN_NAME` argument is invalid. (The standard routines take only one column name.)
missingfunction	User function that you specified does not exist.
missingconstraint	Constraint that you specified for a uniqueness conflict does not exist.
notquiesced	Object group that the given table belongs to is not quiesced.
duplicateresolution	Given conflict resolution method is already registered.
paramtype	Type is different from the type assigned to the priority group.

ALTER_MASTER_PROPAGATION procedure

This procedure alters the propagation method for a given object group at a given master site. This object group must be quiesced. You must call this procedure from the master definition site. If the master appears in the dblink_list or dblink_table, then ALTER_MASTER_PROPAGATION ignores that database link. You cannot change the propagation mode from a master to itself.

Syntax

DBMS_REPCAT.ALTER_MASTER_PROPAGATION (
   gname               IN   VARCHAR2, 
   master              IN   VARCHAR2,
   { dblink_list       IN   VARCHAR2
   | dblink_table      IN   dbms_utility.dblink_array,}
   propagation_mode    IN   VARCHAR2 : ='asynchronous',
   comment             IN   VARCHAR2 := '');

Note:
This procedure is overloaded. The dblink_list and dblink_table parameters are mutually exclusive.

Parameters

Table 34-12 ALTER_MASTER_PROPAGATION Procedure Parameters

Parameter	Description
gname	Name of the object group to which to alter the propagation mode.
master	Name of the master site at which to alter the propagation mode.
dblink_list	A comma-separated list of database links for which to alter propagation. If `NULL`, then all masters except the master site being altered are used by default.
dblink_table	A PL/SQL table, indexed from position 1, of database links for which to alter propagation.
propagation_mode	Determines the manner in which changes from the given master site are propagated to the sites identified by the list of database links. Appropriate values are `SYNCHRONOUS` and `ASYNCHRONOUS`.
comment	This comment is added to the `RepProp` view.

Exceptions

Table 34-13 ALTER_MASTER_PROPAGATION Procedure Exceptions

Exception	Description
nonmasterdef	Local site is not the master definition site.
notquiesced	Local site is not quiesced.
typefailure	Propagation mode specified was not recognized.
nonmaster	List of database links includes a site that is not a master site.

ALTER_MASTER_REPOBJECT procedure

This procedure alters an object in your replicated environment. You must call this procedure from the master definition site.

Syntax

DBMS_REPCAT.ALTER_MASTER_REPOBJECT (
   sname        IN   VARCHAR2, 
   oname        IN   VARCHAR2, 
   type         IN   VARCHAR2, 
   ddl_text     IN   VARCHAR2, 
   comment      IN   VARCHAR2     := '', 
   retry        IN   BOOLEAN      := FALSE);

Parameters

Table 34-14 ALTER_MASTER_REPOBJECT Procedure Parameters

Parameter	Description
sname	Schema containing the object that you want to alter.
oname	Name of the object that you want to alter.
type	Type of the object that you are altering. The types supported are: `TABLE`, `INDEX`, `SYNONYM`, `TRIGGER`, `VIEW`, `PROCEDURE`, `FUNCTION`, `PACKAGE`, and `PACKAGE` `BODY`.
ddl_text	The DDL text that you want used to alter the object. Oracle does not parse this DDL before applying it; therefore, you must ensure that your DDL text provides the appropriate schema and object name for the object being altered.
comment	If not `NULL`, then this comment is added to the `COMMENT` field of the `RepObject` view.
retry	If retry is `TRUE`, then `ALTER_MASTER_REPOBJECT` alters the object only at masters whose object status is not `VALID`.

Exceptions

Table 34-15 ALTER_MASTER_REPOBJECT Procedure Exceptions

Exception	Description
nonmasterdef	Invocation site is not the master definition site.
notquiesced	Associated object group has not been suspended.
missingobject	Object identified by `SNAME` and `ONAME` does not exist.
typefailure	Given type parameter is not supported.
ddlfailure	DDL at the master definition site did not succeed.
commfailure	At least one master site is not accessible.

Usage Notes

ALTER_PRIORITY procedure

This procedure alters the priority level associated with a given priority group member. You must call this procedure from the master definition site.

See Also:
See "Conflict Resolution" in the Oracle8i Replication manual.

Syntax

DBMS_REPCAT.ALTER_PRIORITY (
   gname            IN   VARCHAR2, 
   pgroup           IN   VARCHAR2, 
   old_priority     IN   NUMBER, 
   new_priority     IN   NUMBER);

Parameters

Table 34-16 ALTER_PRIORITY Procedure Parameters

Parameter	Description
gname	Replicated object group with which the priority group is associated.
pgroup	Name of the priority group containing the priority that you want to alter.
old_priority	Current priority level of the priority group member.
new_priority	New priority level that you want assigned to the priority group member.

Exceptions

Table 34-17 ALTER_PRIORITY Procedure Exceptions

Exception	Description
nonmasterdef	Invocation site is not the masterdef site.
duplicatepriority	New priority level already exists in the priority group.
missingrepgroup	Given replicated object group does not exist.
missingvalue	Value was not registered by a call to `DBMS_REPCAT`.`ADD_PRIORITY_datatype`.
missingprioritygroup	Given priority group does not exist.
notquiesced	Given replicated object group is not quiesced.

ALTER_PRIORITY_datatype procedure

This procedure alters the value of a member in a priority group. You must call this procedure from the master definition site. The procedure that you must call is determined by the datatype of your priority column.

See Also:
For additional information, see "Conflict Resolution" in the Oracle8i Replication manual.

Syntax

DBMS_REPCAT.ALTER_PRIORITY_datatype (
   gname        IN   VARCHAR2, 
   pgroup       IN   VARCHAR2, 
   old_value    IN   datatype, 
   new_value    IN   datatype);

where datatype:

{ NUMBER
| VARCHAR2
| CHAR
| DATE
| RAW
| NCHAR
| NVARCHAR2 }

Parameters

Table 34-18 ALTER_PRIORITY_datatype Procedure Parameters

Parameter	Description
gname	Replicated object group with which the priority group is associated.
pgroup	Name of the priority group containing the value that you want to alter.
old_value	Current value of the priority group member.
new_value	New value that you want assigned to the priority group member.

Exceptions

Table 34-19 ALTER_PRIORITY_datatype Procedure Exceptions

Exception	Description
nonmasterdef	Invocation site is not the masterdef site.
duplicatevalue	New value already exists in the priority group.
missingrepgroup	Given replicated object group does not exist.
missingprioritygroup	Given priority group does not exist.
missingvalue	Old value does not exist.
paramtype	New value has the incorrect datatype for the priority group.
typefailure	Given value has the incorrect datatype for the priority group.
notquiesced	Given replicated object group is not quiesced.

ALTER_SITE_PRIORITY procedure

This procedure alters the priority level associated with a given site. You must call this procedure from the master definition site.

See Also:
See "Conflict Resolution" in the Oracle8i Replication manual.

Syntax

DBMS_REPCAT.ALTER_SITE_PRIORITY (
   gname         IN   VARCHAR2,
   name          IN   VARCHAR2,
   old_priority  IN   NUMBER,
   new_priority  IN   NUMBER);

Parameters

Table 34-20 ALTER_SITE_PRIORITY Procedure Parameters

Parameter	Description
gname	Replicated object group with which the site priority group is associated.
name	Name of the site priority group whose member you are altering.
old_priority	Current priority level of the site whose priority level you want to change.
new_priority	New priority level for the site. A higher number indicates a higher priority level.

Exceptions

Table 34-21 ALTER_SITE_PRIORITY Procedure Exceptions

Exception	Description
nonmasterdef	Invocation site is not the masterdef site.
missingrepgroup	Given replicated object group does not exist.
missingpriority	Old priority level is not associated with any group members.
duplicatepriority	New priority level already exists for another site in the group.
missingvalue	Old value does not already exist.
paramtype	New value has the incorrect datatype for the priority group.
notquiesced	Replicated object group is not quiesced.

ALTER_SITE_PRIORITY_SITE procedure

This procedure alters the site associated with a given priority level. You must call this procedure from the master definition site.

See Also:
See "Conflict Resolution" in the Oracle8i Replication manual.

Syntax

DBMS_REPCAT.ALTER_SITE_PRIORITY_SITE (
   gname     IN   VARCHAR2,
   name      IN   VARCHAR2,
   old_site  IN   VARCHAR2,
   new_site  IN   VARCHAR2);

Parameters

Table 34-22 ALTER_SITE_PRIORITY_SITE Procedure Parameters

Parameter	Description
gname	Replicated object group with which the site priority group is associated.
name	Name of the site priority group whose member you are altering.
old_site	Current global database name of the site to dissociate from the priority level.
new_site	New global database name that you want to associate with the current priority level.

Exceptions

Table 34-23 ALTER_SITE_PRIORITY_SITE Procedure Exceptions

Exception	Description
nonmasterdef	Invocation site is not the masterdef site.
missingrepgroup	Given replicated object group does not exist.
missingpriority	Given site priority group does not exist.
missingvalue	Old site is not a group member.
notquiesced	Replicated object group is not quiesced

ALTER_SNAPSHOT_PROPAGATION procedure

This procedure alters the propagation method for a given object group at the current snapshot site. This procedure pushes the deferred transaction queue at the snapshot site, locks the snapshot base tables, and regenerates any triggers and their associated packages. You must call this procedure from the snapshot site.

Syntax

DBMS_REPCAT.ALTER_SNAPSHOT_PROPAGATION (
   gname                IN  VARCHAR2, 
   propagation_mode     IN  VARCHAR2,
   comment              IN  VARCHAR2   := '');

Parameters

Table 34-24 ALTER_SNAPSHOT_PROPAGATION Procedure Parameters

Parameter	Description
gname	Name of the object group for which to alter propagation mode.
propagation_mode	Manner in which changes from the current snapshot site are propagated to its associated master site. Appropriate values are `SYNCHRONOUS` and `ASYNCHRONOUS`.
comment	This comment is added to the `RepProp` view.

Exceptions

Table 34-25 ALTER_SNAPSHOT_PROPAGATION Procedure Exceptions

Exception	Description
missingrepgroup	Given replicated object group does not exist.
typefailure	Propagation mode was specified incorrectly.
nonsnapshot	Current site is not a snapshot site for the given object group.
commfailure	Cannot contact master.

CANCEL_STATISTICS procedure

This procedure stops collecting statistics about the successful resolution of update, uniqueness, and delete conflicts for a table.

Syntax

DBMS_REPCAT.CANCEL_STATISTICS (
   sname    IN   VARCHAR2,
   oname    IN   VARCHAR2);

Parameters

Table 34-26 CANCEL_STATISTICS Procedure Parameters

Parameter	Description
sname	Name of the schema in which the table is located.
oname	Name of the table for which you do not want to gather conflict resolution statistics.

Exceptions

Table 34-27 CANCEL_STATISTICS Procedure Exceptions

Exception	Description
missingschema	Given schema does not exist.
missingobject	Given table does not exist.
statnotreg	Given table is not currently registered to collect statistics.

COMMENT_ON_COLUMN_GROUP procedure

This procedure updates the comment field in the RepColumn_Group view for a column group. This comment is not added at all master sites until the next call to DBMS_REPCAT.GENERATE_REPLICATION_SUPPORT.

Syntax

DBMS_REPCAT.COMMENT_ON_COLUMN_GROUP (
   sname           IN   VARCHAR2, 
   oname           IN   VARCHAR2, 
   column_group    IN   VARCHAR2, 
   comment         IN   VARCHAR2);

Parameters

Table 34-28 COMMENT_ON_COLUMN_GROUP Procedure Parameters

Parameter	Description
sname	Name of the schema in which the object is located.
oname	Name of the replicated table with which the column group is associated.
column_group	Name of the column group.
comment	Text of the updated comment that you want included in the `GROUP_COMMENT` field of the `RepColumn_Group` view.

Exceptions

Table 34-29 COMMENT_ON_COLUMN_GROUP Procedure Exceptions

Exception	Description
nonmasterdef	Invocation site is not the master definition site.
missinggroup	Given column group does not exist.
missingobj	Object is missing.

COMMENT_ON_PRIORITY_GROUP/PRIORITY procedure

COMMENT_ON_PRIORITY_GROUP updates the comment field in the REPPRIORITY_GROUP view for a priority group. This comment is not added at all master sites until the next call to GENERATE_REPLICATION_SUPPORT.

COMMENT_ON_SITE_PRIORITY updates the comment field in the REPPRIORITY_GROUP view for a site priority group. This procedure is a wrapper for the COMMENT_ON_COLUMN_GROUP procedure and is provided as a convenience only. This procedure must be issued at the master definition site.

Syntax

DBMS_REPCAT.COMMENT_ON_PRIORITY_GROUP (
   gname       IN   VARCHAR2, 
   pgroup      IN   VARCHAR2, 
   comment     IN   VARCHAR2);

DBMS_REPCAT.COMMENT_ON_SITE_PRIORITY (
   gname       IN   VARCHAR2, 
   name        IN   VARCHAR2, 
   comment     IN   VARCHAR2);

Parameters

Table 34-30 COMMENT_ON_PRIORITY_GROUP/COMMENT_ON_SITE_PRIORITY Parameters

Parameter	Description
gname	Name of the replicated object group.
pgroup/name	Name of the priority or site priority group.
comment	Text of the updated comment that you want included in the `PRIORITY_COMMENT` field of the `RepPriority_Group` view.

Exceptions

Table 34-31 COMMENT_ON_PRIORITY_GROUP/COMMENT_ON_SITE_PRIORITY Exceptions

Exception	Description
nonmasterdef	Invocation site is not the master definition site.
missingrepgroup	Given replicated object group does not exist.
missingprioritygroup	Given priority group does not exist.

COMMENT_ON_REPGROUP procedure

This procedure updates the comment field in the REPGROUP view for a replicated object group. This procedure must be issued at the master definition site.

Syntax

DBMS_REPCAT.COMMENT_ON_REPGROUP (
   gname     IN   VARCHAR2,
   comment   IN   VARCHAR2);

Parameters

Table 34-32 COMMENT_ON_REPGROUP Procedure Parameters

Parameter	Description
gname	Name of the object group that you want to comment on.
comment	Updated comment to include in the `SCHEMA_COMMENT` field of the `RepGroup` view.

Exceptions

Table 34-33 COMMENT_ON_REPGROUP Procedure Exceptions

Exception	Description
nonmasterdef	Invocation site is not the master definition site.
commfailure	At least one master site is not accessible.

COMMENT_ON_REPSITES procedure

This procedure updates the comment field in the RepSite view for a replicated site. This procedure must be issued at the master definition site.

Syntax

DBMS_REPCAT.COMMENT_ON_REPSITES ( 
   gname       IN   VARCHAR2, 
   [ master    IN   VARCHAR,] 
   comment     IN   VARCHAR2);

Parameters

Table 34-34 COMMENT_ON_REPSITES Procedure Parameters

Parameter	Description
gname	Name of the object group. This avoids confusion if a database is a master site in more than one replicated environment.
master	(Optional) The fully qualified database name of the master site that you want to comment on. To update comments at a snapshot site, omit this parameter.
comment	Text of the updated comment that you want to include in the `MASTER_COMMENT` field of the `RepSites` view.

Exceptions

Table 34-35 COMMENT_ON_REPSITES Procedure Exceptions

Exception	Description
nonmasterdef	Invocation site is not the master definition site.
nonmaster	Invocation site is not a master site.
commfailure	At least one master site is not accessible.

COMMENT_ON_REPOBJECT procedure

This procedure updates the comment field in the RepObject view for a replicated object. This procedure must be issued at the master definition site.

Syntax

DBMS_REPCAT.COMMENT_ON_REPOBJECT (
   sname    IN   VARCHAR2, 
   oname    IN   VARCHAR2, 
   type     IN   VARCHAR2, 
   comment  IN   VARCHAR2);

Parameters

Table 34-36 COMMENT_ON_REPOBJECT Procedure Parameters

Parameter	Description
sname	Name of the schema in which the object is located.
oname	Name of the object that you want to comment on.
type	Type of the object.
comment	Text of the updated comment that you want to include in the `OBJECT_COMMENT` field of the `RepObject` view.

Exceptions

Table 34-37 COMMENT_ON_REPOBJECT Procedure Exceptions

Exception	Description
nonmasterdef	Invocation site is not the master definition site.
missingobject	Given object does not exist.
typefailure	Given type parameter is not supported.
commfailure	At least one master site is not accessible.

COMMENT_ON_conflicttype_RESOLUTION procedure

This procedure updates the comment field in the RepResolution view for a conflict resolution routine. The procedure that you need to call is determined by the type of conflict that the routine resolves. These procedures must be issued at the master definition site.

Conflict Type	Procedure Name
update	COMMENT_ON_UPDATE_RESOLUTION
uniqueness	COMMENT_ON_UNIQUE_RESOLUTION
delete	COMMENT_ON_DELETE_RESOLUTION

The comment is not added at all master sites until the next call to GENERATE_REPLICATION_SUPPORT.

Syntax

DBMS_REPCAT.COMMENT_ON_UPDATE_RESOLUTION (
   sname                 IN   VARCHAR2,
   oname                 IN   VARCHAR2,
   column_group          IN   VARCHAR2,
   sequence_no           IN   NUMBER, 
   comment               IN   VARCHAR2);

DBMS_REPCAT.COMMENT_ON_UNIQUE_RESOLUTION (
   sname                 IN   VARCHAR2,
   oname                 IN   VARCHAR2,
   constraint_name       IN   VARCHAR2,
   sequence_no           IN   NUMBER, 
   comment               IN   VARCHAR2);

DBMS_REPCAT.COMMENT_ON_DELETE_RESOLUTION (
   sname                 IN   VARCHAR2,
   oname                 IN   VARCHAR2,
   sequence_no           IN   NUMBER, 
   comment               IN   VARCHAR2);

Parameters

Table 34-38 COMMENT_ON_conflicttype_RESOLUTION Procedure Parameters

Parameter	Description
sname	Name of the schema.
oname	Name of the replicated table with which the conflict resolution routine is associated.
column_group	Name of the column group with which the update conflict resolution routine is associated.
constraint_name	Name of the unique constraint with which the uniqueness conflict resolution routine is associated.
sequence_no	Sequence number of the conflict resolution procedure.
comment	The text of the updated comment that you want included in the `RESOLUTION_COMMENT` field of the `RepResolution` view.

Exceptions

Table 34-39 COMMENT_ON_conflicttype_RESOLUTION Procedure Exceptions

Exception	Description
nonmasterdef	Invocation site is not the master definition site.
missingobject	Given object does not exist.
missingresolution	Specified conflict resolution routine is not registered.

COMPARE_OLD_VALUES procedure

You have the option of comparing old column values for each non-key column of a replicated table for updates and deletes. The default is to compare old values for all columns. You can change this behavior at all master and snapshot sites by invoking DBMS_REPCAT.COMPARE_OLD_VALUES at the master definition site.

Syntax

DBMS_REPCAT.COMPARE_OLD_VALUES(
   sname           IN  VARCHAR2,
   oname           IN  VARCHAR2,
   { column_list   IN  VARCHAR2
   | column_table  IN  DBMS_REPCAT.VARCHAR2s,}
   operation       IN  VARCHAR2 := `UPDATE',
   compare         IN  BOOLEAN := TRUE );

Note:
This procedure is overloaded. The column_list and column_table parameters are mutually exclusive.

Parameters

Table 34-40 COMPARE_OLD_VALUES Procedure Parameters

Parameter	Description
sname	Schema in which the table is located.
oname	Name of the replicated table.
column_list	A comma-separated list of the columns in the table. There must be no white space between entries.
column_table	Instead of a list, you can use a PL/SQL table of type `DBMS_REPCAT`.`VARCHAR2S` to contain the column names. The first column name should be at offset 1, the second at offset 2, and so on.
operation	Possible values are: `UPDATE`, `DELETE`, or the asterisk wildcard '*', which means update and delete.
compare	If compare is `TRUE`, then the old values of the specified columns are compared when sent. If compare is `FALSE`, then the old values of the specified columns are not compared when sent. Unspecified columns and unspecified operations are not affected. The specified change takes effect at the master definition site as soon as `min_communication` is `TRUE` for the table. The change takes effect at a master site or at a snapshot site the next time replication support is generated at that site with `min_communication` `TRUE`.

Note:
The operation parameter allows you to decide whether to transmit old values for non-key columns when rows are deleted or when non-key columns are updated. If you do not send the old value, then Oracle sends a NULL in place of the old value and assumes the old value is equal to the current value of the column at the target side when the update or delete is applied.
Read "Minimizing Data Propagation for Update Conflict Resolution" in the Oracle8i Replication manual before changing the default behavior of Oracle.

Exceptions

Table 34-41 COMPARE_OLD_VALUES Procedure Exceptions

Exception	Description
nonmasterdef	Invocation site is not the master definition site.
missingobject	Given object does not exist as a table in the given schema awaiting row-level replication information.
missingcolumn	At least one column is not in the table.
notquiesced	Replicated object group has not been suspended.
typefailure	An illegal operation is given.

CREATE_MASTER_REPGROUP procedure

This procedure creates a new, empty, quiesced master replication object group.

Syntax

DBMS_REPCAT.CREATE_MASTER_REPGROUP (
   gname            IN   VARCHAR2, 
   group_comment    IN   VARCHAR2     := '', 
   master_comment   IN   VARCHAR2     := ''),
   qualifier        IN   VARCHAR2     := '');

Parameters

Table 34-42 CREATE_MASTER_REPGROUP Procedure Parameters

Parameter	Description
gname	Name of the object group that you want to create.
group_comment	This comment is added to the `RepGroup` view.
master_comment	This comment is added to the `RepSites` view.
qualifier	Connection qualifier for object group. Be sure to use the @ sign, as shown in the example: See "Managing Master Groups" in the Oracle8i Replication manual.

Exceptions

Table 34-43 CREATE_MASTER_REPGROUP Procedure Exceptions

Exception	Description
duplicaterepgroup	Object group already exists.
norepopt	Advanced replication option is not installed.
missingrepgroup	Object group name was not specified.
qualifiertoolong	Connection qualifier is too long.

CREATE_MASTER_REPOBJECT procedure

This procedure indicates that an object is a replicated object.

Syntax

DBMS_REPCAT.CREATE_MASTER_REPOBJECT (
   sname                IN   VARCHAR2,
   oname                IN   VARCHAR2, 
   type                 IN   VARCHAR2,
   use_existing_object  IN   BOOLEAN     := TRUE, 
   ddl_text             IN   VARCHAR2    := NULL, 
   comment              IN   VARCHAR2    := '', 
   retry                IN   BOOLEAN     := FALSE,
   copy_rows            IN   BOOLEAN     := TRUE,
   gname                IN   VARCHAR2    := '');

Parameters

Table 34-44 CREATE_MASTER_REPOBJECT Procedure Parameters

Parameters	Description
sname	Name of the schema in which the object that you want to replicate is located.
oname	Name of the object you are replicating. If `DDL_TEXT` is `NULL`, then this object must already exist in the given schema. To ensure uniqueness, table names should be a maximum of 27 bytes long, and package names should be no more than 24 bytes.
type	Type of the object that you are replicating. The types supported are: `TABLE`, `INDEX`, `SYNONYM`, `TRIGGER`, `VIEW`, `PROCEDURE`, `FUNCTION`, `PACKAGE`, and `PACKAGE` `BODY`.
use_existing_object	Indicate `TRUE` if you want to reuse any objects of the same type and shape at the current master sites. See Table 34-46 for more information.
ddl_text	If the object does not already exist at the master definition site, then you must supply the DDL text necessary to create this object. PL/SQL packages, package bodies, procedures, and functions must have a trailing semicolon. SQL statements do not end with trailing semicolon. Oracle does not parse this DDL before applying it; therefore, you must ensure that your DDL text provides the appropriate schema and object name for the object being created.
comment	This comment is added to the `OBJECT_COMMENT` field of the `RepObject` view.
retry	Indicate `TRUE` if you want Oracle to reattempt to create an object that it was previously unable to create. Use this if the error was transient or has since been rectified; for example, if you previously had insufficient resources. If this is `TRUE`, then Oracle creates the object only at master sites whose object status is not `VALID`.
copy_rows	Indicate `TRUE` if you want the initial contents of a newly replicated object to match the contents of the object at the master definition site. See Table 34-46 for more information.
gname	Name of the object group in which you want to create the replicated object. The schema name is used as the default object group name if none is specified.

Table 34-45 CREATE_MASTER_REPOBJECT Procedure Exceptions

Exceptions	Description
nonmasterdef	Invocation site is not the master definition site.
notquiesced	Replicated object group has not been suspended.
duplicateobject	Given object already exists in the replicated object group and retry is `FALSE`, or if a name conflict occurs.
missingobject	Object identified by `SNAME` and `ONAME` does not exist and appropriate DDL has not been provided.
typefailure	Objects of the given type cannot be replicated.
ddlfailure	DDL at the master definition site did not succeed.
commfailure	At least one master site is not accessible.
notcompat	Not all remote masters in 7.3 compatibility mode.

Object Creations

Table 34-46 Object Creation at Master Sites

Object Already Exists?	COPY_ROWS	USE_EXISTING_OBJECTS	Result
yes	TRUE	TRUE	`duplicatedobject` message if objects do not match. For tables, use data from master definition site.
yes	FALSE	TRUE	`duplicatedobject` message if objects do not match. For tables, DBA must ensure contents are identical.
yes	TRUE/FALSE	FALSE	`duplicatedobject` message.
no	TRUE	TRUE/FALSE	Object is created. Tables populated using data from master definition site.
no	FALSE	TRUE/FALSE	Object is created. DBA must populate tables and ensure consistency of tables at all sites.

Usage Notes

CREATE_SNAPSHOT_REPGROUP procedure

This procedure creates a new, empty snapshot replication object group in your local database.

Syntax

DBMS_REPCAT.CREATE_SNAPSHOT_REPGROUP (
   gname              IN   VARCHAR2, 
   master             IN   VARCHAR2, 
   comment            IN   VARCHAR2     := '',
   propagation_mode   IN   VARCHAR2     := 'ASYNCHRONOUS',
   fname              IN   VARCHAR2     := NULL);

Parameters

Table 34-47 CREATE_SNAPSHOT_REPGROUP Procedure Parameters

Parameter	Description
gname	Name of the replicated object group. This object group must exist at the given master site.
master	Fully qualified database name of the database in the replicated environment to use as the master.
comment	This comment is added to the `RepGroup` view.
propagation_mode	Method of propagation for all updatable snapshots in the object group. Acceptable values are `SYNCHRONOUS` and `ASYNCHRONOUS`.
fname	This system parameter is for internal use only. Do not set the parameter unless so directed by Oracle Worldwide Support.

Exceptions

Table 34-48 CREATE_SNAPSHOT_REPGROUP Procedure Exceptions

Exception	Description
duplicaterepgroup	Object group already exists at the invocation site.
nonmaster	Given database is not a master site.
commfailure	Given database is not accessible.
norepopt	Advanced replication option is not installed.
typefailure	Propagation mode was specified incorrectly.
missingrepgroup	If replicated object group not at master site.

Usage Notes

CREATE_SNAPSHOT_REPGROUP automatically calls REGISTER_SNAPSHOT_REPGROUP, but ignores any errors that may have happened during registration.

CREATE_SNAPSHOT_REPOBJECT procedure

This procedure adds a replicated object to your snapshot site.

Syntax

DBMS_REPCAT.CREATE_SNAPSHOT_REPOBJECT (
   sname                   IN   VARCHAR2,
   oname                   IN   VARCHAR2, 
   type                    IN   VARCHAR2, 
   ddl_text                IN   VARCHAR2  := '',
   comment                 IN   VARCHAR2  := '',
   gname                   IN   VARCHAR2  := '',
   gen_objs_owner          IN   VARCHAR2 := '',
   min_communication       IN   BOOLEAN  := TRUE ,
   generate_80_compatible  IN   BOOLEAN  := TRUE);

Parameters

Table 34-49 CREATE_SNAPSHOT_REPOBJECT Procedure Parameters

Parameter	Description
sname	Name of the schema in which the object is located.
oname	Name of the object that you want to add to the replicated snapshot object group. `ONAME` must exist at the associated master site.
type	Type of the object that you are replicating. The types supported for snapshot sites are: `PACKAGE`, `PACKAGE` `BODY`, `PROCEDURE`, `FUNCTION`, `SNAPSHOT`, `SYNONYM`, `TRIGGER`, and `VIEW`.
ddl_text	For objects of type `SNAPSHOT`, the DDL text needed to create the object; for other types, use the default, ('' (an empty string). If a snapshot with the same name already exists, then Oracle ignores the DDL and registers the existing snapshot as a replicated object. If the master table for a snapshot does not exist in the replicated object group of the master site designated for this schema, then Oracle raises a `missingobject` `error`.
comment	This comment is added to the `OBJECT_COMMENT` field of the `RepObject` view.
gname	Name of the replicated object group to which you are adding an object. The schema name is used as the default group name if none is specified.
gen_objs_owner	Name of the user you want to assign as owner of the transaction.
min_communication	Set to `FALSE` if any master site is running Oracle7 release 7.3. Set to `TRUE` to minimize new and old values of propagation. The default is `TRUE`. For more information, see "Conflict Resolution" in the Oracle8i Replication manual.
generate_80_ compatible	Set to `TRUE` if any master site is running a version of Oracle Server prior to Oracle8i release 8.1.5. Set to `FALSE` if replicated environment is a pure Oracle8i release 8.1.5 or greater environment.

Exceptions

Table 34-50 CREATE_SNAPSHOT_REPOBJECT Procedure Exceptions

Exception	Description
nonsnapshot	Invocation site is not a snapshot site.
nonmaster	Master is no longer a master site.
missingobject	Given object does not exist in the master's replicated object group.
duplicateobject	Given object already exists with a different shape.
typefailure	Type is not an allowable type.
ddlfailure	DDL did not succeed.
commfailure	Master site is not accessible.
missingschema	Schema does not exist as a database schema.
badsnapddl	DDL was executed but snapshot does not exist.
onlyonesnap	Only one snapshot for master table can be created.
badsnapname	Snapshot base table differs from master table.
missingrepgroup	Replicated object group does not exist.

Usage Notes

DEFINE_COLUMN_GROUP procedure

This procedure creates an empty column group. You must call this procedure from the master definition site.

See Also:
For more information, see "Conflict Resolution" in the Oracle8i Replication manual.

Syntax

DBMS_REPCAT.DEFINE_COLUMN_GROUP ( 
   sname            IN   VARCHAR2,
   oname            IN   VARCHAR2,
   column_group     IN   VARCHAR2,
   comment          IN   VARCHAR2 := NULL);

Parameters

Table 34-51 DEFINE_COLUMN_GROUP Procedure Parameters

Parameter	Description
sname	Schema in which the replicated table is located.
oname	Name of the replicated table for which you are creating a column group.
column_group	Name of the column group that you want to create.
comment	This user text is displayed in the `RepColumn_Group` view.

Exceptions

Table 34-52 DEFINE_COLUMN_GROUP Procedure Exceptions

Exception	Description
nonmasterdef	Invocation site is not the masterdef site.
missingobject	Given table does not exist.
duplicategroup	Given column group already exists for the table.
notquiesced	Object group that the given table belongs to is not quiesced.

DEFINE_PRIORITY_GROUP procedure

This procedure creates a new priority group for a replicated object group. You must call this procedure from the master definition site.

See Also:
See "Conflict Resolution" in the Oracle8i Replication manual.

Syntax

DBMS_REPCAT.DEFINE_PRIORITY_GROUP (
   gname         IN   VARCHAR2, 
   pgroup        IN   VARCHAR2, 
   datatype      IN   VARCHAR2, 
   fixed_length  IN   INTEGER := NULL,
   comment       IN   VARCHAR2 := NULL);

Parameters

Table 34-53 DEFINE_PRIORITY_GROUP Procedure Parameters

Parameter	Description
gname	Replicated object group for which you are creating a priority group.
pgroup	Name of the priority group that you are creating.
datatype	Datatype of the priority group members. The datatypes supported are: `CHAR`, `VARCHAR2`, `NUMBER`, `DATE`, `RAW`, `NCHAR`, and `NVARCHAR2`.
fixed_length	You must provide a column length for the `CHAR` datatype. All other types can use the default, `NULL`.
comment	This user comment is added to the `RepPriority` view.

Exceptions

Table 34-54 DEFINE_PRIORITY_GROUP Procedure Exceptions

Exception	Description
nonmasterdef	Invocation site is not the masterdef site.
missingrepgroup	Given replicated object group does not exist.
duplicatepriority group	Given priority group already exists in the replicated object group.
typefailure	Given datatype is not supported.
notquiesced	Replicated object group is not quiesced.

DEFINE_SITE_PRIORITY procedure

This procedure creates a new site priority group for a replicated object group. You must call this procedure from the master definition site.

See Also:
See "Conflict Resolution" in the Oracle8i Replication manual.

Syntax

DBMS_REPCAT.DEFINE_SITE_PRIORITY (
   gname        IN   VARCHAR2, 
   name         IN   VARCHAR2,
   comment      IN   VARCHAR2 := NULL);

Parameters

Table 34-55 DEFINE_SITE_PRIORITY Procedure Parameters

Parameter	Description
gname	The replicated object group for which you are creating a site priority group.
name	Name of the site priority group that you are creating.
comment	This user comment is added to the `RepPriority` view.

Exceptions

Table 34-56 DEFINE_SITE_PRIORITY Procedure Exceptions

Exception	Description
nonmasterdef	Invocation site is not the masterdef site.
missingrepgroup	Given replicated object group does not exist.
duplicate prioritygroup	Given site priority group already exists in the replicated object group.
notquiesced	Replicated object group is not quiesced.

DO_DEFERRED_REPCAT_ADMIN procedure

This procedure executes the local outstanding deferred administrative procedures for the given replicated object group at the current master site, or (with assistance from job queues) for all master sites.

Syntax

DBMS_REPCAT.DO_DEFERRED_REPCAT_ADMIN (
   gname          IN   VARCHAR2,
   all_sites      IN   BOOLEAN := FALSE);

Parameters

Table 34-57 DO_DEFERRED_REPCAT_ADMIN Procedure Parameters

Parameter	Description
gname	Name of the replicated object group.
all_sites	If this is `TRUE`, then use a job to execute the local administrative procedures at each master.

Exceptions

Table 34-58 DO_DEFERRED_REPCAT_ADMIN Procedure Exceptions

Exception	Description
nonmaster	Invocation site is not a master site.
commfailure	At least one master site is not accessible and `all_sites` is `TRUE`.

Usage Notes

DO_DEFERRED_REPCAT_ADMIN executes only those administrative requests submitted by the connected user that called DO_DEFERRED_REPCAT_ADMIN. Requests submitted by other users are ignored.

DROP_COLUMN_GROUP procedure

This procedure drops a column group. You must call this procedure from the master definition site.

See Also:
See "Conflict Resolution" in the Oracle8i Replication manual.

Syntax

DBMS_REPCAT.DROP_COLUMN_GROUP (
   sname        IN   VARCHAR2,
   oname        IN   VARCHAR2,
   column_group IN   VARCHAR2);

Parameters

Table 34-59 DROP_COLUMN_GROUP Procedure Parameters

Parameter	Description
sname	Schema in which the replicated table is located.
oname	Name of the replicated table whose column group you are dropping.
column_group	Name of the column group that you want to drop.

Exceptions

Table 34-60 DROP_COLUMN_GROUP Procedure Exceptions

Exception	Description
nonmasterdef	Invocation site is not the masterdef site.
referenced	Given column group is being used in conflict detection and resolution.
missingobject	Given table does not exist.
missinggroup	Given column group does not exist.
notquiesced	Replicated object group that the table belongs to is not quiesced.

DROP_GROUPED_COLUMN procedure

This procedure removes members from a column group. You must call this procedure from the master definition site.

See Also:
For more information, see "Conflict Resolution" in the Oracle8i Replication manual.

Syntax

DBMS_REPCAT.DROP_GROUPED_COLUMN (
   sname                 IN   VARCHAR2,
   oname                 IN   VARCHAR2,
   column_group          IN   VARCHAR2,
   list_of_column_names  IN   VARCHAR2 | DBMS_REPCAT.VARCHAR2S);

Parameters

Table 34-61 DROP_GROUPED_COLUMN Procedure Parameters

Parameter	Description
sname	Schema in which the replicated table is located.
oname	Name of the replicated table in which the column group is located.
column_group	Name of the column group from which you are removing members.
list_of_column_names	Names of the columns that you are removing from the designated column group. This can either be a comma-separated list or a PL/SQL table of column names. The PL/SQL table must be of type dbms_repcat.varchar2s.

Exceptions

Table 34-62 DROP_GROUPED_COLUMN Procedure Exceptions

Exception	Description
nonmasterdef	Invocation site is not the masterdef site.
missingobject	Given table does not exist.
notquiesced	Replicated object group that the table belongs to is not quiesced.

DROP_MASTER_REPGROUP procedure

This procedure drops a replicated object group from your current site. To drop the replicated object group from all master sites, including the master definition site, you can call this procedure at the master definition site, and set the final argument to TRUE.

Syntax

DBMS_REPCAT.DROP_MASTER_REPGROUP (
   gname             IN VARCHAR2,
   drop_contents     IN BOOLEAN    := FALSE,
   all_sites         IN BOOLEAN    := FALSE);

Parameters

Table 34-63 DROP_MASTER_REPGROUP Procedure Parameters

Parameter	Description
gname	Name of the replicated object group that you want to drop from the current master site.
drop_contents	By default, when you drop the object group at a master site, all of the objects remain in the database. They simply are no longer replicated; that is, the replicated objects in the object group no longer send changes to, or receive changes from, other master sites. If you set this to `TRUE`, then any replicated objects in the replicated object group are dropped from their associated schemas.
all_sites	If this is `TRUE` and if the invocation site is the master definition site, then the procedure synchronously multicasts the request to all masters. In this case, execution is immediate at the master definition site and may be deferred at all other master sites.

Exceptions

Table 34-64 DROP_MASTER_REPGROUP Procedure Exceptions

Exception	Description
nonmaster	Invocation site is not a master site.
nonmasterdef	Invocation site is not the master definition site and `ALL_SITES` is `TRUE`.
commfailure	At least one master site is not accessible and `ALL_SITES` is `TRUE`.
fullqueue	Deferred RPC queue has entries for the replicated object group.
masternotremoved	Master does not recognize the masterdef and `ALL_SITES` is `TRUE`.

DROP_MASTER_REPOBJECT procedure

This procedure drops a replicated object from a replicated object group. You must call this procedure from the master definition site.

Syntax

DBMS_REPCAT.DROP_MASTER_REPOBJECT (
   sname          IN   VARCHAR2, 
   oname          IN   VARCHAR2, 
   type           IN   VARCHAR2, 
   drop_objects   IN   BOOLEAN     := FALSE);

Parameters

Table 34-65 DROP_MASTER_REPOBJECT Procedure Parameters

Parameter	Description
sname	Name of the schema in which the object is located.
oname	Name of the object that you want to remove from the replicated object group.
type	Type of object that you want to drop.
drop_objects	By default, the object remains in the schema, but is dropped from the replicated object group; that is, any changes to the object are no longer replicated to other master and snapshot sites. To completely remove the object from the replicated environment, set this argument to `TRUE`.

Exceptions

Table 34-66 DROP_MASTER_REPOBJECT Procedure Exceptions

Exception	Description
nonmasterdef	Invocation site is not the master definition site.
missingobject	Given object does not exist.
typefailure	Given type parameter is not supported.
commfailure	At least one master site is not accessible.

DROP_PRIORITY procedure

This procedure drops a member of a priority group by priority level. You must call this procedure from the master definition site.

See Also:
See "Conflict Resolution" in the Oracle8i Replication manual.

Syntax

DBMS_REPCAT.DROP_PRIORITY(
      gname          IN   VARCHAR2,
      pgroup         IN   VARCHAR2, 
      priority_num   IN   NUMBER);

Parameters

Table 34-67 DROP_PRIORITY Procedure Parameters

Parameter	Description
gname	Replicated object group with which the priority group is associated.
pgroup	Name of the priority group containing the member that you want to drop.
priority_num	Priority level of the priority group member that you want to remove from the group.

Exceptions

Table 34-68 DROP_PRIORITY Procedure Exceptions

Exception	Description
nonmasterdef	Invocation site is not the masterdef site.
missingrepgroup	Given replicated object group does not exist.
missingprioritygroup	Given priority group does not exist.
notquiesced	Replicated object group is not quiesced.

DROP_PRIORITY_GROUP procedure

This procedure drops a priority group for a given replicated object group. You must call this procedure from the master definition site.

See Also:
See "Conflict Resolution" in the Oracle8i Replication manual.

Syntax

DBMS_REPCAT.DROP_PRIORITY_GROUP (
   gname     IN   VARCHAR2,
   pgroup    IN   VARCHAR2);

Parameters

Table 34-69 DROP_PRIORITY_GROUP Procedure Parameters

Parameter	Description
gname	Replicated object group with which the priority group is associated.
pgroup	Name of the priority group that you want to drop.

Exceptions

Table 34-70 DROP_PRIORITY_GROUP Procedure Exceptions

Exception	Description
nonmasterdef	Invocation site is not the masterdef site.
missingrepgroup	Given replicated object group does not exist.
referenced	Given priority group is being used in conflict resolution.
notquiesced	Given replicated object group is not quiesced.

DROP_PRIORITY_datatype procedure

This procedure drops a member of a priority group by value. You must call this procedure from the master definition site. The procedure that you must call is determined by the datatype of your priority column.

See Also:
See "Conflict Resolution" in the Oracle8i Replication manual.

Syntax

DBMS_REPCAT.DROP_PRIORITY_datatype (
   gname    IN   VARCHAR2,
   pgroup   IN   VARCHAR2, 
   value    IN   datatype);

where datatype:

{ NUMBER
| VARCHAR2
| CHAR
| DATE
| RAW
| NCHAR
| NVARCHAR2 }

Parameters

Table 34-71 DROP_PRIORITY_datatype Procedure Parameters

Parameter	Description
gname	Replicated object group with which the priority group is associated.
pgroup	Name of the priority group containing the member that you want to drop.
value	Value of the priority group member that you want to remove from the group.

Exceptions

Table 34-72 DROP_PRIORITY_datatype Procedure Exceptions

Exception	Description
nonmasterdef	Invocation site is not the masterdef site.
missingrepgroup	Given replicated object group does not exist.
missingprioritygroup	Given priority group does not exist.
paramtype, typefailure	Value has the incorrect datatype for the priority group.
notquiesced	Given replicated object group is not quiesced

DROP_SITE_PRIORITY procedure

This procedure drops a site priority group for a given replicated object group. You must call this procedure from the master definition site.

See Also:
See "Conflict Resolution" in the Oracle8i Replication manual.

Syntax

DBMS_REPCAT.DROP_SITE_PRIORITY (
   gname      IN   VARCHAR2,
   name       IN   VARCHAR2);

Parameters

Table 34-73 DROP_SITE_PRIORITY Procedure Parameters

Parameter	Description
gname	Replicated object group with which the site priority group is associated.
name	Name of the site priority group that you want to drop.

Exceptions

Table 34-74 DROP_SITE_PRIORITY Procedure Exceptions

Exception	Description
nonmasterdef	Invocation site is not the masterdef site.
missingrepgroup	Given replicated object group does not exist.
referenced	Given site priority group is being used in conflict resolution.
notquiesced	Given replicated object group is not quiesced

DROP_SITE_PRIORITY_SITE procedure

This procedure drops a given site, by name, from a site priority group. You must call this procedure from the master definition site.

See Also:
See "Conflict Resolution" in the Oracle8i Replication manual.

Syntax

DBMS_REPCAT.DROP_SITE_PRIORITY_SITE (
   gname      IN   VARCHAR2, 
   name       IN   VARCHAR2,
   site       IN   VARCHAR2);

Parameters

Table 34-75 DROP_SITE_PRIORITY_SITE Procedure Parameters

Parameter	Description
gname	Replicated object group with which the site priority group is associated.
name	Name of the site priority group whose member you are dropping.
site	Global database name of the site you are removing from the group.

Exceptions

Table 34-76 DROP_SITE_PRIORITY_SITE Procedure Exceptions

Exception	Description
nonmasterdef	Invocation site is not the masterdef site.
missingrepgroup	Given replicated object group does not exist.
missingpriority	Given site priority group does not exist.
notquiesced	Given replicated object group is not quiesced.

DROP_SNAPSHOT_REPGROUP procedure

This procedure drops a snapshot site from your replicated environment.

Syntax

DBMS_REPCAT.DROP_SNAPSHOT_REPGROUP (
   gname                 IN   VARCHAR2, 
   drop_contents         IN   BOOLEAN   := FALSE);

Parameters

Table 34-77 DROP_SNAPSHOT_REPGROUP Procedure Parameters

Parameter	Description
gname	Name of the replicated object group that you want to drop from the current snapshot site. All objects generated to support replication, such as triggers and packages, are dropped.
drop_contents	By default, when you drop the replicated object group at a snapshot site, all of the objects remain in their associated schemas; they simply are no longer replicated. If you set this to `TRUE`, then any replicated objects in the replicated object group are dropped from their schemas.

Exceptions

Table 34-78 DROP_SNAPSHOT_REPGROUP Procedure Exceptions

Exception	Description
nonsnapshot	Invocation site is not a snapshot site.
missingrepgroup	Specified object group does not exist.

Usage Notes

DROP_SNAPSHOT_REPGROUP automatically calls UNREGISTER_SNAPSHOT_REPGROUP to unregister the snapshot, but ignores any errors that may have occurred during unregistration.

DROP_SNAPSHOT_REPOBJECT procedure

This procedure drops a replicated object from a snapshot site.

Syntax

DBMS_REPCAT.DROP_SNAPSHOT_REPOBJECT ( 
   sname          IN   VARCHAR2, 
   oname          IN   VARCHAR2, 
   type           IN   VARCHAR2, 
   drop_objects   IN   BOOLEAN  := FALSE);

Parameters

Table 34-79 DROP_SNAPSHOT_REPOBJECT Procedure Parameters

Parameter	Description
sname	Name of the schema in which the object is located.
oname	Name of the object that you want to drop from the replicated object group.
type	Type of the object that you want to drop.
drop_objects	By default, the object remains in its associated schema, but is dropped from its associated object group. To completely remove the object from its schema at the current snapshot site, set this argument to `TRUE`.

Exceptions

Table 34-80 DROP_SNAPSHOT_REPOBJECT Procedure Exceptions

Exception	Description
nonsnapshot	Invocation site is not a snapshot site.
missingobject	Given object does not exist.
typefailure	Given type parameter is not supported.

DROP_conflicttype_RESOLUTION procedure

This procedure drops an update, delete, or uniqueness conflict resolution routine. You must call these procedures from the master definition site. The procedure that you must call is determined by the type of conflict that the routine resolves.

Conflict Type	Procedure Name
update	DROP_UPDATE_RESOLUTION
uniqueness	DROP_UNIQUE_RESOLUTION
delete	DROP_DELETE_RESOLUTION

Syntax

DBMS_REPCAT.DROP_UPDATE_RESOLUTION (
   sname              IN   VARCHAR2, 
   oname              IN   VARCHAR2, 
   column_group       IN   VARCHAR2, 
   sequence_no        IN   NUMBER);

DBMS_REPCAT.DROP_DELETE_RESOLUTION (
   sname              IN   VARCHAR2, 
   oname              IN   VARCHAR2, 
   sequence_no        IN   NUMBER);

DBMS_REPCAT.DROP_UNIQUE_RESOLUTION (
   sname              IN   VARCHAR2, 
   oname              IN   VARCHAR2, 
   constraint_name    IN   VARCHAR2, 
   sequence_no        IN   NUMBER);

Parameters

Table 34-81 DROP_conflicttype_RESOLUTION Procedure Parameters

Parameter	Description
sname	Schema in which the table is located.
oname	Name of the table for which you want to drop a conflict resolution routine.
column_group	Name of the column group for which you want to drop an update conflict resolution routine.
constraint_name	Name of the Unique constraint for which you want to drop a unique conflict resolution routine.
sequence_no	Sequence number assigned to the conflict resolution method that you want to drop. This number uniquely identifies the routine.

Exceptions

Table 34-82 DROP_conflicttype_RESOLUTION Procedure Exceptions

Exception	Description
nonmasterdef	Invocation site is not the masterdef site.
missingobject	Given object does not exist as a table in the given schema, or a conflict resolution routine with the given sequence number is not registered.
notquiesced	Replicated object group is not quiesced.

EXECUTE_DDL procedure

This procedure supplies DDL that you want to have executed at some or all master sites. You can call this procedure only from the master definition site.

Syntax

DBMS_REPCAT.EXECUTE_DDL (
   gname           IN   VARCHAR2,
   { master_list   IN   VARCHAR2     := NULL
   | master_table  IN   DBMS_UTILITY.DBLINK_ARRAY,}
   DDL_TEXT        IN   VARCHAR2);

Parameters

Table 34-83 EXECUTE_DDL Procedure Parameters

Parameter	Description
gname	Name of the replicated object group.
master_list	A comma-separated list of master sites at which you want to execute the supplied DDL. There must be no extra white space between site names. The default value, `NULL`, indicates that the DDL should be executed at all sites, including the master definition site.
master_table	A table of master sites at which you want to execute the supplied DDL. The first master should be at offset 1, the second at offset 2, and so on.
ddl_text	The DDL that you want to have executed at each of the given master sites.

Exceptions

Table 34-84 EXECUTE_DDL Procedure Exceptions

Exception	Description
nonmasterdef	Invocation site is not the master definition site.
nonmaster	At least one site is not a master site.
ddlfailure	DDL at the master definition site did not succeed.
commfailure	At least one master site is not accessible.

Usage Notes

If the DDL is supplied without specifying a schema, then the default schema is the replication administrator's schema. Be sure to specify the schema if it is other than the replication administrator's schema. This procedure is overloaded. The MASTER_LIST and MASTER_TABLE parameters are mutually exclusive.

GENERATE_REPLICATION_SUPPORT procedure

This procedure generates the triggers and packages needed to support replication. You must call this procedure from the master definition site.

Syntax

DBMS_REPCAT.GENERATE_REPLICATION_SUPPORT (
  sname                     IN    VARCHAR2, 
  oname                     IN    VARCHAR2, 
  type                      IN    VARCHAR2, 
  package_prefix            IN    VARCHAR2   := NULL, 
  procedure_prefix          IN    VARCHAR2   := NULL, 
  distributed               IN    BOOLEAN    := TRUE,
  gen_objs_owner            IN    VARCHAR2   := NULL,
  min_communication         IN    BOOLEAN    := TRUE,
  generate_80_compatible    IN    BOOLEAN    := TRUE);

Parameters

Table 34-85 GENERATE_REPLICATION_SUPPORT Procedure Parameters

Parameter	Description
sname	Schema in which the object is located.
oname	Name of the object for which you are generating replication support.
type	Type of the object. The types supported are: `TABLE`, `PACKAGE`, and `PACKAGE` `BODY`.
package_prefix	For objects of type `PACKAGE` or `PACKAGE` `BODY` this value is prepended to the generated wrapper package name. The default is `DEFER_`.
procedure_prefix	For objects of type `PACKAGE` or `PACKAGE` `BODY`, this value is prepended to the generated wrapper procedure names. By default, no prefix is assigned.
distributed	This must be set to `TRUE`.
gen_objs_owner	For objects of type `PACKAGE` or `PACKAGE BODY`, the schema in which the generated object should be created. If `NULL`, then the objects will be created in `sname`.
min_communication	Set to `FALSE` if any master site is running Oracle7 release 7.3. Set to `TRUE` when you want propagation of new and old values to be minimized. The default is `TRUE`. For more information, see "Conflict Resolution' in the Oracle8i Replication manual.
generate_80_ compatible	Set to `TRUE` if any master site is running a version of Oracle Server prior to Oracle8i release 8.1.5. Set to `FALSE` if replicated environment is a pure Oracle8i release 8.1.5 or greater environment.

Exceptions

Table 34-86 GENERATE_REPLICATION_SUPPORT Procedure Exceptions

Exception	Description
nonmasterdef	Invocation site is not the master definition site.
missingobject	Given object does not exist as a table in the given schema awaiting row-level replication information or as a package (body) awaiting wrapper generation.
typefailure	Given type parameter is not supported.
notquiesced	Replicated object group has not been suspended.
commfailure	At least one master site is not accessible.
missingschema	Schema does not exist.
dbnotcompatible	One of the masters is not 7.3 compatible.
duplicateobject	Object already exists.

GENERATE_SNAPSHOT_SUPPORT procedure

This procedure activates triggers and generate packages needed to support the replication of updatable snapshots or procedural replication.You must call this procedure from the snapshot site.

Syntax

DBMS_REPCAT.GENERATE_SNAPSHOT_SUPPORT (
   sname                    IN VARCHAR2,
   oname                    IN VARCHAR2,
   type                     IN VARCHAR2,
   gen_objs_owner           IN VARCHAR2 := '',
   min_communication        IN BOOLEAN  := TRUE,
   generate_80_compatible   IN BOOLEAN  := TRUE);

Parameters

Table 34-87 GENERATE_SNAPSHOT_SUPPORT Procedure Parameters

Parameter	Description
sname	Schema in which the object is located.
oname	The name of the object that you are generating support for.
type	Type of the object. The types supported are `SNAPSHOT`, `PACKAGE`, and `PACKAGE` `BODY`.
gen_objs_owner	For objects of type `PACKAGE` or `PACKAGE BODY`, the schema in which the generated object should be created. If `NULL`, then the objects will be created in `sname`.
min_communication	If `TRUE`, then the update trigger sends the new value of a column only if the update statement modifies the column. The update trigger sends the old value of the column only if it is a key column or a column in a modified column group.
generate_80_ compatible	Set to `TRUE` if any master site is running a version of Oracle Server prior to Oracle8i release 8.1.5. Set to `FALSE` if replicated environment is a pure Oracle8i release 8.1.5 or greater environment.

Exceptions

Table 34-88 GENERATE_SNAPSHOT_SUPPORT Procedure Exceptions

Exceptions	Descriptions
nonsnapshot	Invocation site is not a snapshot site.
missingobject	Given object does not exist as a snapshot in the replicated schema awaiting row/column-level replication information or as a package (body) awaiting wrapper generation.
typefailure	Given type parameter is not supported.
missingschema	Specified owner of generated objects does not exist.
missingremoteobject	Master object has not yet generated replication support.
commfailure	Master is not accessible.

Usage Notes

CREATE_SNAPSHOT_REPOBJECT automatically generates snapshot support for updatable snapshots.

MAKE_COLUMN_GROUP procedure

This procedure creates a new column group with one or more members. You must call this procedure from the master definition site.

See Also:
For more information, see "Conflict Resolution" in the Oracle8i Replication manual.

Syntax

DBMS_REPCAT.MAKE_COLUMN_GROUP ( 
   sname                 IN   VARCHAR2,
   oname                 IN   VARCHAR2,
   column_group          IN   VARCHAR2,
   list_of_column_names  IN   VARCHAR2 | DBMS_REPCAT.VARCHAR2S);

Parameters

Table 34-89 MAKE_COLUMN_GROUP Procedure Parameters

Parameter	Description
sname	Schema in which the replicated table is located.
oname	Name of the replicated table for which you are creating a new column group.
column_group	Name that you want assigned to the column group that you are creating.
list_of_column_names	Names of the columns that you are grouping. This can either be a comma-separated list or a PL/SQL table of column names. The PL/SQL table must be of type `dbms_repcat`.`varchar2s`. Use the single value '*' to create a column group that contains all of the columns in your table.

Exceptions

Table 34-90 MAKE_COLUMN_GROUP Procedure Exceptions

Exception	Description
nonmasterdef	Invocation site is not the masterdef site.
duplicategroup	Given column group already exists for the table.
missingobject	Given table does not exist.
missingcolumn	Given column does not exist in the designated table.
duplicatecolumn	Given column is already a member of another column group.
notquiesced	Replicated object group is not quiesced.

PURGE_MASTER_LOG procedure

This procedure removes local messages in the RepCatLog associated with a given identification number, source, or replicated object group.

Syntax

DBMS_REPCAT.PURGE_MASTER_LOG (
   id      IN   NATURAL, 
   source  IN   VARCHAR2, 
   gname   IN   VARCHAR2);

Parameters

Table 34-91 PURGE_MASTER_LOG Procedure Parameters

Parameter	Description
id	Identification number of the request, as it appears in the `RepCatLog` view.
source	Master site from which the request originated.
gname	Name of the replicated object group for which the request was made.

Exceptions

Table 34-92 PURGE_MASTER_LOG Procedure Exceptions

Exception	Description
nonmaster	`gname` is not `NULL`, and the invocation site is not a master site.

PURGE_STATISTICS procedure

This procedure removes information from the RepResolution_Statistics view.

Syntax

DBMS_REPCAT.PURGE_STATISTICS (
   sname      IN   VARCHAR2, 
   oname      IN   VARCHAR2, 
   start_date IN   DATE,
   end_date   IN   DATE);

Parameters

Table 34-93 PURGE_STATISTICS Procedure Parameters

Parameter	Description
sname	Name of the schema in which the replicated table is located.
oname	Name of the table whose conflict resolution statistics you want to purge.
start_date/end_date	Range of dates for which you want to purge statistics. If `START_DATE` is `NULL`, then purge all statistics up to the `END_DATE`. If `END_DATE` is `NULL`, then purge all statistics after the `START_DATE`.

Exceptions

Table 34-94 PURGE_STATISTICS Procedure Exceptions

Exception	Description
missingschema	Given schema does not exist.
missingobject	Given table does not exist.
statnotreg	Table not registered to collect statistics.

REFRESH_SNAPSHOT_REPGROUP procedure

This procedure refreshes a snapshot site object group with the most recent data from its associated master site.

Syntax

DBMS_REPCAT.REFRESH_SNAPSHOT_REPGROUP (
   gname                  IN   VARCHAR2,
   drop_missing_contents  IN   BOOLEAN    := FALSE,
   refresh_snapshots      IN   BOOLEAN    := FALSE,
   refresh_other_objects  IN   BOOLEAN    := FALSE);

Parameters

Table 34-95 REFRESH_SNAPSHOT_REPGROUP Procedure Parameters

Parameter	Description
gname	Name of the replicated object group.
drop_missing_ contents	If an object was dropped from the replicated object group, then it is not automatically dropped from the schema at the snapshot site. It is simply no longer replicated; that is, changes to this object are no longer sent to its associated master site. Snapshots can continue to be refreshed from their associated master tables; however, any changes to an updatable snapshot are lost. When an object is dropped from the object group, you can choose to have it dropped from the schema entirely by setting this argument to `TRUE`.
refresh_snapshots	Set this to `TRUE` to refresh the contents of the snapshots in the replicated object group.
refresh_other_ objects	Set this to `TRUE` to refresh the contents of the non-snapshot objects in the replicated object group.

Exceptions

Table 34-96 REFRESH_SNAPSHOT_REPGROUP Procedure Exceptions

Exception	Description
nonsnapshot	Invocation site is not a snapshot site.
nonmaster	Master is no longer a master site.
commfailure	Master is not accessible.
missingrepgroup	Object group name not specified.

REGISTER_SNAPSHOT_REPGROUP procedure

This procedure facilitates the administration of snapshots at their respective master sites by inserting/modifying/deleting from registered_snapshot_groups.

Syntax

DBMS_REPCAT.REGISTER_SNAPSHOT_REPGROUP (
   gname            IN   VARCHAR2,
   snapsite         IN   VARCHAR2,
   comment          IN   VARCHAR2  := NULL,
   rep_type         IN   NUMBER    := reg_unknown,
   fname            IN   VARCHAR2  := NULL);

Parameters

Table 34-97 REGISTER_SNAPSHOT_REPGROUP Procedure Parameters

Parameter	Description
gname	Name of the snapshot object group to be registered.
snapsite	Global name of the snapshot site.
comment	Comment for the snapshot site or update for an existing comment.
rep_type	Version of the snapshot group. Valid constants that can be assigned include `reg_uknown` (the default), `reg_v7_group`, `reg_v8_group`, and `reg_repapi_group`.
fname	This system parameter is for internal use only. Do not set the parameter unless so directed by Oracle Worldwide Support.

Exceptions

Table 34-98 REGISTER_SNAPSHOT_REPGROUP Procedure Exceptions

Exception Description

missingrepgroup

Object group name not specified.

nullsitename

A snapshot site was not specified.

nonmaster

Procedure must be executed at the snapshot's master site.

duplicaterepgroup

Object already exists.

REGISTER_STATISTICS procedure

This procedure collects information about the successful resolution of update, delete, and uniqueness conflicts for a table.

Syntax

DBMS_REPCAT.REGISTER_STATISTICS (
   sname IN   VARCHAR2,
   oname IN   VARCHAR2);

Parameters

Table 34-99 REGISTER_STATISTICS Procedure Parameters

Parameter	Description
sname	Name of the schema in which the table is located.
oname	Name of the table for which you want to gather conflict resolution statistics.

Exceptions

Table 34-100 REGISTER_STATISTICS Procedure Exceptions

Exception	Description
missingschema	Given schema does not exist.
missingobject	Given table does not exist.

RELOCATE_MASTERDEF procedure

This procedure changes your master definition site to another master site in your replicated environment.

Syntax

DBMS_REPCAT.RELOCATE_MASTERDEF (
   gname                  IN   VARCHAR2, 
   old_masterdef          IN   VARCHAR2, 
   new_masterdef          IN   VARCHAR2, 
   notify_masters         IN   BOOLEAN    := TRUE,
   include_old_masterdef  IN   BOOLEAN    := TRUE,
   require_flavor_change  IN   BOOLEAN    := FALSE);

Parameters

Table 34-101 RELOCATE_MASTERDEF Procedure Parameters

Parameter	Description
gname	Name of the object group whose master definition you want to relocate.
old_masterdef	Fully qualified database name of the current master definition site.
new_masterdef	Fully qualified database name of the existing master site that you want to make the new master definition site.
notify_masters	If this is `TRUE`, then the procedure synchronously multicasts the change to all masters (including `OLD_MASTERDEF` only if `INCLUDE_OLD_MASTERDEF` is `TRUE`). If any master does not make the change, then roll back the changes at all masters.
include_old_ masterdef	If `NOTIFY_MASTERS` is `TRUE` and if `INCLUDE_OLD_MASTERDEF` is also `TRUE`, then the old master definition site is also notified of the change.
require_flavor_ change	This system parameter is for internal use only. Do not set the parameter unless so directed by Oracle Worldwide Support.

Exceptions

Table 34-102 RELOCATE_MASTERDEF Procedure Exceptions

Exception	Description
nonmaster	`NEW_MASTERDEF` is not a master site or the invocation site is not a master site.
nonmasterdef	`OLD_MASTERDEF` is not the master definition site.
commfailure	At least one master site is not accessible and `NOTIFY_MASTERS` is `TRUE`.

Usage Notes

It is not necessary for either the old or new master definition site to be available when you call RELOCATE_MASTERDEF. In a planned reconfiguration, you should invoke RELOCATE_MASTERDEF with NOTIFY_MASTERS TRUE and INCLUDE_OLD_MASTERDEF TRUE.

If just the master definition site fails, then you should invoke RELOCATE_MASTERDEF with NOTIFY_MASTERS TRUE and INCLUDE_OLD_MASTERDEF FALSE. If several master sites and the master definition site fail, then the administrator should invoke RELOCATE_MASTERDEF at each operational master with NOTIFY_MASTERS FALSE.

REMOVE_MASTER_DATABASES procedure

This procedure removes one or more master databases from a replicated environment. This procedure regenerates the triggers and their associated packages at the remaining master sites. You must call this procedure from the master definition site.

Syntax

DBMS_REPCAT.REMOVE_MASTER_DATABASES (
   gname           IN   VARCHAR2,
   master_list     IN   VARCHAR2 |
   master_table    IN   DBMS_UTILITY.DBLINK_ARRAY);

Parameters

Table 34-103 REMOVE_MASTER_DATABASES Procedure Parameters

Parameter	Description
gname	Name of the object group associated with the replicated environment. This prevents confusion if a master database is involved in more than one replicated environment.
master_list	A comma-separated list of fully qualified master database names that you want to remove from the replicated environment. There must be no white space between names in the list.
master_table	In place of a list, you may also specify the database names in a PL/SQL table of type `DBMS_UTILITY`.`DBLINK_ARRAY`.

Exceptions

Table 34-104 REMOVE_MASTER_DATABASES Procedure Exceptions

Exception	Description
nonmasterdef	Invocation site is not the master definition site.
nonmaster	At least one of the given databases is not a master site.
reconfigerror	One of the given databases is the master definition site.
commfailure	At least one remaining master site is not accessible.

REPCAT_IMPORT_CHECK procedure

This procedure ensures that the objects in the replicated object group have the appropriate object identifiers and status values after you perform an export/import of a replicated object or an object used by the advanced replication facility.

Syntax

DBMS_REPCAT.REPCAT_IMPORT_CHECK (
   gname      IN   VARCHAR2,
   master     IN   BOOLEAN);

Parameters

Table 34-105 REPCAT_IMPORT_CHECK Procedure Parameters

Parameter	Description
gname	Name of the replicated object group. If you omit both parameters, then the procedure checks all replicated object groups at your current site.
master	Set this to `TRUE` if you are checking a master site or `FALSE` if you are checking a snapshot site.

Exceptions

Table 34-106 REPCAT_IMPORT_CHECK Procedure Exceptions

Exception	Description
nonmaster	`MASTER` is `TRUE` and either the database is not a master site for the object group or the database is not the expected database.
nonsnapshot	`MASTER` is `FALSE` and the database is not a snapshot site for the object group.
missingobject	A valid replicated object in the object group does not exist.
missingrepgroup	The given group name does not exist.

RESUME_MASTER_ACTIVITY procedure

This procedure resumes normal replication activity after quiescing a replicated environment.

Syntax

DBMS_REPCAT.RESUME_MASTER_ACTIVITY (
   gname       IN  VARCHAR2, 
   override    IN  BOOLEAN := FALSE);

Parameters

Table 34-107 RESUME_MASTER_ACTIVITY Procedure Parameters

Parameter Description

gname

Name of the replicated object group.

override

If this is TRUE, then it ignores any pending RepCat administration requests and restores normal replication activity at each master as quickly as possible. This should be considered only in emergency situations.

If this is FALSE, then it restores normal replication activity at each master only when there is no pending RepCat administration request for gname at that master.

Exceptions

Table 34-108 RESUME_MASTER_ACTIVITY Procedure Exceptions

Exception	Description
nonmasterdef	Invocation site is not the master definition site.
notquiesced	Replicated object group is not quiescing or quiesced.
commfailure	At least one master site is not accessible.

SEND_OLD_VALUES procedure

You have the option of sending old column values for each non-key column of a replicated table for updates and deletes. The default is to send old values for all columns. You can change this behavior at all master and snapshot sites by invoking DBMS_REPCAT.SEND_OLD_VALUES at the master definition site.

Syntax

DBMS_REPCAT.SEND_OLD_VALUES(
   sname           IN  VARCHAR2,
   oname           IN  VARCHAR2,
   { column_list   IN  VARCHAR2
   | column_table  IN  DBMS_REPCAT.VARCHAR2s,}
   operation       IN  VARCHAR2 := `UPDATE',
   send            IN  BOOLEAN  := TRUE );

Note:
This procedure is overloaded. The column_list and column_table parameters are mutually exclusive.

Parameters

Table 34-109 SEND_OLD_VALUES Procedure Parameters

Parameter	Description
sname	Schema in which the table is located.
oname	Name of the replicated table.
column_list	A comma-separated list of the columns in the table. There must be no white space between entries.
column_table	Instead of a list, you can use a PL/SQL table of type `DBMS_REPCAT`.`VARCHAR2S` to contain the column names. The first column name should be at offset 1, the second at offset 2, and so on.
operation	Possible values are: `UPDATE`, `DELETE`, or the asterisk wildcard '*', which means update and delete.
send	If `TRUE`, then the old values of the specified columns are sent. If `FALSE`, then the old values of the specified columns are not sent. Unspecified columns and unspecified operations are not affected. The specified change takes effect at the master definition site as soon as `min_communication` is `TRUE` for the table. The change takes effect at a master site or at a snapshot site the next time replication support is generated at that site with `min_communication` `TRUE`.

Note:
The operation parameter allows you to decide whether or not to transmit old values for non-key columns when rows are deleted or when non-key columns are updated. If you do not send the old value, then Oracle sends a NULL in place of the old value and assumes the old value is equal to the current value of the column at the target side when the update or delete is applied.
Read "Minimizing Data Propagation for Update Conflict Resolution" in the Oracle8i Replication manual before changing the default behavior of Oracle.

Exceptions

Table 34-110 SEND_OLD_VALUES Procedure Exceptions

Exception	Description
nonmasterdef	Invocation site is not the master definition site.
missingobject	Given object does not exist as a table in the given schema awaiting row-level replication information.
missingcolumn	At least one column is not in the table.
notquiesced	Replicated object group has not been suspended.
typefailure	An illegal operation is given.

SET_COLUMNS procedure

To use an alternate column or group of columns, instead of the primary key, to determine which columns of a table to compare when using row-level replication. You must call this procedure from the master definition site.

See Also:
See "Using Multimaster Replication" in the Oracle8i Replication manual.

Syntax

DBMS_REPCAT.SET_COLUMNS (
   sname           IN    VARCHAR2,
   oname           IN    VARCHAR2,
   { column_list   IN    VARCHAR2
   | column_table  IN    DBMS_UTILITY.NAME_ARRAY } );

Note:
This procedure is overloaded. The column_list and column_table parameters are mutually exclusive.

Parameters

Table 34-111 SET_COLUMNS Procedure Parameters

Parameter	Description
sname	Schema in which the table is located.
oname	Name of the table.
column_list	A comma-separated list of the columns in the table that you want to use as a primary key. There must be no white space between entries.
column_table	Instead of a list, you can use a PL/SQL table of type `DBMS_UTILITY`.`NAME_ARRAY` to contain the column names. The first column name should be at offset 1, the second at offset 2, and so on.

Exceptions

Table 34-112 SET_COLUMNS Procedure Exceptions

Exception	Description
nonmasterdef	Invocation site is not the master definition site.
missingobject	Given object does not exist as a table in the given schema awaiting row-level replication information.
missingcolumn	At least one column is not in the table.

SUSPEND_MASTER_ACTIVITY procedure

This procedure suspends replication activity for an object group. You must call this procedure from the master definition site.

Syntax

DBMS_REPCAT.SUSPEND_MASTER_ACTIVITY (
   gname   IN   VARCHAR2);

Parameters

Table 34-113 SUSPEND_MASTER_ACTIVITY Procedure Parameters

Parameter	Description
gname	Name of the object group for which you want to suspend activity.

Exceptions

Table 34-114 SUSPEND_MASTER_ACTIVITY Procedure Exceptions

Exception	Description
nonmasterdef	Invocation site is not the master definition site.
notnormal	Replicated object group is not in normal operation.
commfailure	At least one master site is not accessible.

Usage Notes

The current implementation of SUSPEND_MASTER_ACTIVITY quiesces all replicated object groups at each master site.

SWITCH_SNAPSHOT_MASTER procedure

This procedure changes the master database of a snapshot replicated object group to another master site. This procedure does a full refresh of the affected snapshots and regenerates the triggers and their associated packages as needed. This procedure does not push the queue to the old master site before changing masters.

Syntax

DBMS_REPCAT.SWITCH_SNAPSHOT_MASTER (
   gname              IN   VARCHAR2, 
   master             IN   VARCHAR2);

Parameters

Table 34-115 SWITCH_SNAPSHOT_MASTER Procedure Parameters

Parameter	Description
gname	Name of the snapshot object group for which you want to change master sites.
master	Fully qualified database name of the new master database to use for the snapshot site.

Exceptions

Table 34-116 SWITCH_SNAPSHOT_MASTER Procedure Exceptions

Exception	Description
nonsnapshot	Invocation site is not a snapshot site.
nonmaster	Given database is not a master site.
commfailure	Given database is not accessible.

UNREGISTER_SNAPSHOT_REPGROUP procedure

This procedure facilitates the administration of snapshots at their respective master sites by inserting/modifying/deleting from registered_snapshot_groups.

Syntax

DBMS_REPCAT.UNREGISTER_SNAPSHOT_REPGROUP (
   gname     IN   VARCHAR2,
   snapsite  IN   VARCHAR2);

Parameters

Table 34-117 UNREGISTER_SNAPSHOT_REPGROUP Procedure Parameters

Parameter	Description
gname	Name of the snapshot object group to be unregistered.
snapsite	Global name of the snapshot site.

VALIDATE function

This function validates the correctness of key conditions of a multiple master replication environment. This is overloaded.

Syntax

DBMS_REPCAT.VALIDATE (
   gname               IN  VARCHAR2, 
   check_genflags      IN  BOOLEAN := FALSE,
   check_valid_objs    IN  BOOLEAN := FALSE,
   check_links_sched   IN  BOOLEAN := FALSE,
   check_links         IN  BOOLEAN := FALSE,
   error_table         OUT dbms_repcat.validate_err_table )
  RETURN BINARY_INTEGER;

DBMS_REPCAT.VALIDATE (
   gname               IN  VARCHAR2, 
   check_genflags      IN  BOOLEAN := FALSE,
   check_valid_objs    IN  BOOLEAN := FALSE,
   check_links_sched   IN  BOOLEAN := FALSE,
   check_links         IN  BOOLEAN := FALSE,
   error_msg_table     OUT DBMS_UTILITY.UNCL_ARRAY,
   error_num_table     OUT DBMS_UTILITY.NUMBER_ARRAY )
  RETURN BINARY_INTEGER;

Parameters

Table 34-118 VALIDATE Function Parameters

Parameter	Description
gname	Name of the master group to validate.
check_genflags	Check whether all the objects in the group are generated. This must be done at the masterdef site only.
check_valid_objs	Check that the underlying objects for objects in the group valid. This must be done at the masterdef site only. The masterdef site goes to all other sites and checks that the underlying objects are valid. The validity of the objects is checked within the schema of the connected user.
check_links_sched	Check whether the links are scheduled for execution. This should be invoked at each master site.
check_links	Check whether the connected user (repadmin), as well as the propagator, have correct links for replication to work properly. Checks that the links exist in the database and are accessible. This should be invoked at each master site.
error_table	Returns the message and numbers of all errors that are found.
error_msg_table	Returns the messages of all errors that are found.
error_num_table	Returns the numbers of all errors that are found.

Exceptions

Table 34-119 VALIDATE Function Exceptions

Exception	Description
missingdblink	Database link does not exist in the schema of the replication propagator or has not been scheduled. Ensure that the database link exists in the database, is accessible, and is scheduled for execution.
dblinkmismatch	Database link name at the local node does not match the global name of the database that the link accesses. Ensure that global names is set to true and the link name matches the global name.
dblinkuidmismatch	User name of the replication administration user at the local node and the user name at the node corresponding to the database link are not the same. Advanced replication expects the two users to be the same. Ensure that the user ID of the replication administration user at the local node and the user ID at the node corresponding to the database link are the same.
objectnotgenerated	Object has not been generated at other master sites or is still being generated. Ensure that the object is generated by calling `generate_replication_support` and `do_deferred_repcat_admin` for the object at the masterdef site.
opnotsupported	Operation is not supported if the object group is replicated at a pre-V8 node. Ensure that all nodes of the replicated object group are V8.

Usage Notes

The return value of VALIDATE is the number of errors found. The function's OUT parameter(s) returns any errors that are found. In the first interface function, the ERROR_TABLE consists of an array of records. Each record has a VARCHAR2 and a NUMBER in it. The string field contains the error message and the number field contains the Oracle error number.

The second interface is similar except that there are two OUT arrays. A VARCHAR2 array with the error messages and a NUMBER array with the error numbers.

WAIT_MASTER_LOG procedure

This procedure determines whether changes that were asynchronously propagated to a master site have been applied.

Syntax

DBMS_REPCAT.WAIT_MASTER_LOG (
   gname          IN    VARCHAR2, 
   record_count   IN    NATURAL, 
   timeout        IN    NATURAL, 
   true_count     OUT   NATURAL);

Parameters

Table 34-120 WAIT_MASTER_LOG Procedure Parameters

Parameter	Description
gname	Name of the replicated object group.
record_count	Procedure returns whenever the number of incomplete activities is at or below this threshold.
timeout	Maximum number of seconds to wait before the procedure returns.
true_count (out parameter)	Returns the number of incomplete activities.

Exceptions

Table 34-121 WAIT_MASTER_LOG Procedure Exceptions

Exception	Description
nonmaster	Invocation site is not a master site.

Exception	Description
missingrepgroup	Object group name not specified.
nullsitename	A snapshot site was not specified.
nonmaster	Procedure must be executed at the snapshot's master site.
duplicaterepgroup	Object already exists.

34DBMS_REPCAT

Summary of Subprograms

Table 34-1 DBMS_REPCAT Package Subprograms

ADD_GROUPED_COLUMN procedure

Syntax

Parameters

Table 34-2 ADD_GROUPED_COLUMN Procedure Parameters

Exceptions

Table 34-3 ADD_GROUPED_COLUMN Procedure Exceptions

ADD_MASTER_DATABASE procedure

Syntax

Parameters

Table 34-4 ADD_MASTER_DATABASE Procedure Parameters

Exceptions

Table 34-5 ADD_MASTER_DATABASE Procedure Exceptions

ADD_PRIORITY_datatype procedure

Syntax

Parameters

Table 34-6 ADD_PRIORITY_datatype Procedure Parameters

Exceptions

Table 34-7 ADD_PRIORITY_datatype Procedure Exceptions

ADD_SITE_PRIORITY_SITE procedure

Syntax

Parameters

Table 34-8 ADD_SITE_PRIORITY_SITE Procedure Parameters

Exceptions

Table 34-9 ADD_SITE_PRIORITY_SITE Procedure Exceptions

ADD_conflicttype_RESOLUTION procedure

Syntax

Parameters

Table 34-10 ADD_conflicttype_RESOLUTION Procedure Parameters

Exceptions

Table 34-11 ADD_conflicttype_RESOLUTION Procedure Exceptions

ALTER_MASTER_PROPAGATION procedure

Syntax

Parameters

Table 34-12 ALTER_MASTER_PROPAGATION Procedure Parameters

Exceptions

Table 34-13 ALTER_MASTER_PROPAGATION Procedure Exceptions

ALTER_MASTER_REPOBJECT procedure

Syntax

Parameters

Table 34-14 ALTER_MASTER_REPOBJECT Procedure Parameters

Exceptions

Table 34-15 ALTER_MASTER_REPOBJECT Procedure Exceptions

Usage Notes

ALTER_PRIORITY procedure

Syntax

Parameters

Table 34-16 ALTER_PRIORITY Procedure Parameters

Exceptions

Table 34-17 ALTER_PRIORITY Procedure Exceptions

ALTER_PRIORITY_datatype procedure

Syntax

Parameters

Table 34-18 ALTER_PRIORITY_datatype Procedure Parameters

Exceptions

Table 34-19 ALTER_PRIORITY_datatype Procedure Exceptions

ALTER_SITE_PRIORITY procedure

Syntax

Parameters

Table 34-20 ALTER_SITE_PRIORITY Procedure Parameters

Exceptions

Table 34-21 ALTER_SITE_PRIORITY Procedure Exceptions

ALTER_SITE_PRIORITY_SITE procedure

Syntax

Parameters

Table 34-22 ALTER_SITE_PRIORITY_SITE Procedure Parameters

Exceptions

Table 34-23 ALTER_SITE_PRIORITY_SITE Procedure Exceptions

ALTER_SNAPSHOT_PROPAGATION procedure

Syntax

Parameters

Table 34-24 ALTER_SNAPSHOT_PROPAGATION Procedure Parameters

Exceptions

Table 34-25 ALTER_SNAPSHOT_PROPAGATION Procedure Exceptions

CANCEL_STATISTICS procedure

Syntax

Parameters

Table 34-26 CANCEL_STATISTICS Procedure Parameters

34
DBMS_REPCAT