Oracle8i Supplied Packages Reference Release 8.1.5 A68001-01 |
|
DBMS_REPCAT
provides routines to administer and update the replication catalog and environment.
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 |
COMMENT_ON_PRIORITY_ GROUP/PRIORITY procedure |
Updates the comment field in the |
COMMENT_ON_REPGROUP procedure |
Updates the comment field in the |
COMMENT_ON_REPSITES procedure |
Updates the comment field in the |
COMMENT_ON_REPOBJECT procedure |
Updates the comment field in the |
COMMENT_ON_conflicttype_ RESOLUTION procedure |
Updates the comment field in the |
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 |
PURGE_STATISTICS procedure |
Removes information from the |
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 |
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 |
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. |
This procedure adds members to an existing column group. You must call this procedure from the master definition site.
DBMS_REPCAT.ADD_GROUPED_COLUMN ( sname IN VARCHAR2, oname IN VARCHAR2, column_group IN VARCHAR2, list_of_column_names IN VARCHAR2 | DBMS_REPCAT.VARCHAR2S);
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.
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);
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 |
copy_rows |
Indicate |
comment |
This is added to the |
propagation_mode |
Method of forwarding changes to and receiving changes from new master database. Accepted values are |
fname |
This system parameter is for internal use only. Do not set the parameter unless so directed by Oracle Worldwide Support. |
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.
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 }
This procedure adds a new site to a site priority group. You must call this procedure from the master definition site.
DBMS_REPCAT.ADD_SITE_PRIORITY_SITE ( gname IN VARCHAR2, name IN VARCHAR2, site IN VARCHAR2, priority IN NUMBER);
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. |
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);
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
The methods supported in this release are: |
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 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
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, |
function_name |
If you selected the |
comment |
This user comment is added to the |
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.
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 := '');
This procedure alters an object in your replicated environment. You must call this procedure from the master definition site.
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);
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 alters the priority level associated with a given priority group member. You must call this procedure from the master definition site.
DBMS_REPCAT.ALTER_PRIORITY ( gname IN VARCHAR2, pgroup IN VARCHAR2, old_priority IN NUMBER, new_priority IN NUMBER);
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.
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 }
This procedure alters the priority level associated with a given site. You must call this procedure from the master definition site.
DBMS_REPCAT.ALTER_SITE_PRIORITY ( gname IN VARCHAR2, name IN VARCHAR2, old_priority IN NUMBER, new_priority IN NUMBER);
This procedure alters the site associated with a given priority level. You must call this procedure from the master definition site.
DBMS_REPCAT.ALTER_SITE_PRIORITY_SITE ( gname IN VARCHAR2, name IN VARCHAR2, old_site IN VARCHAR2, new_site IN VARCHAR2);
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.
DBMS_REPCAT.ALTER_SNAPSHOT_PROPAGATION ( gname IN VARCHAR2, propagation_mode IN VARCHAR2, comment IN VARCHAR2 := '');
This procedure stops collecting statistics about the successful resolution of update, uniqueness, and delete conflicts for a table.
DBMS_REPCAT.CANCEL_STATISTICS ( sname IN VARCHAR2, oname IN VARCHAR2);
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. |
Exception | Description |
---|---|
missingschema |
Given schema does not exist. |
missingobject |
Given table does not exist. |
statnotreg |
Given table is not currently registered to collect statistics. |
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
.
DBMS_REPCAT.COMMENT_ON_COLUMN_GROUP ( sname IN VARCHAR2, oname IN VARCHAR2, column_group IN VARCHAR2, comment IN VARCHAR2);
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
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.
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);
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.
DBMS_REPCAT.COMMENT_ON_REPGROUP ( gname IN VARCHAR2, comment IN VARCHAR2);
Parameter | Description |
---|---|
gname |
Name of the object group that you want to comment on. |
comment |
Updated comment to include in the |
Exception | Description |
---|---|
nonmasterdef |
Invocation site is not the master definition site. |
commfailure |
At least one master site is not accessible. |
This procedure updates the comment field in the RepSite
view for a replicated site. This procedure must be issued at the master definition site.
DBMS_REPCAT.COMMENT_ON_REPSITES ( gname IN VARCHAR2, [ master IN VARCHAR,] comment IN VARCHAR2);
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. |
This procedure updates the comment field in the RepObject
view for a replicated object. This procedure must be issued at the master definition site.
DBMS_REPCAT.COMMENT_ON_REPOBJECT ( sname IN VARCHAR2, oname IN VARCHAR2, type IN VARCHAR2, comment IN VARCHAR2);
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
.
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);
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.
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:
The Read "Minimizing Data Propagation for Update Conflict Resolution" in the Oracle8i Replication manual before changing the default behavior of Oracle. |
This procedure creates a new, empty, quiesced master replication object group.
DBMS_REPCAT.CREATE_MASTER_REPGROUP ( gname IN VARCHAR2, group_comment IN VARCHAR2 := '', master_comment IN VARCHAR2 := ''), qualifier IN VARCHAR2 := '');
Parameter | Description |
---|---|
gname |
Name of the object group that you want to create. |
group_comment |
This comment is added to the |
master_comment |
This comment is added to the |
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. |
This procedure indicates that an object is a replicated object.
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 | 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 |
type |
Type of the object that you are replicating. The types supported are: |
use_existing_object |
Indicate |
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 |
retry |
Indicate |
copy_rows |
Indicate |
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. |
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 creates a new, empty snapshot replication object group in your local database.
DBMS_REPCAT.CREATE_SNAPSHOT_REPGROUP ( gname IN VARCHAR2, master IN VARCHAR2, comment IN VARCHAR2 := '', propagation_mode IN VARCHAR2 := 'ASYNCHRONOUS', fname IN VARCHAR2 := NULL);
CREATE_SNAPSHOT_REPGROUP
automatically calls REGISTER_SNAPSHOT_REPGROUP
, but ignores any errors that may have happened during registration.
This procedure adds a replicated object to your snapshot site.
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);
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. |
type |
Type of the object that you are replicating. The types supported for snapshot sites are: |
ddl_text |
For objects of type |
comment |
This comment is added to the |
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 |
generate_80_ compatible |
Set to |
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 creates an empty column group. You must call this procedure from the master definition site.
DBMS_REPCAT.DEFINE_COLUMN_GROUP ( sname IN VARCHAR2, oname IN VARCHAR2, column_group IN VARCHAR2, comment IN VARCHAR2 := NULL);
This procedure creates a new priority group for a replicated object group. You must call this procedure from the master definition site.
DBMS_REPCAT.DEFINE_PRIORITY_GROUP ( gname IN VARCHAR2, pgroup IN VARCHAR2, datatype IN VARCHAR2, fixed_length IN INTEGER := NULL, comment IN VARCHAR2 := NULL);
This procedure creates a new site priority group for a replicated object group. You must call this procedure from the master definition site.
DBMS_REPCAT.DEFINE_SITE_PRIORITY ( gname IN VARCHAR2, name IN VARCHAR2, comment IN VARCHAR2 := NULL);
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.
DBMS_REPCAT.DO_DEFERRED_REPCAT_ADMIN ( gname IN VARCHAR2, all_sites IN BOOLEAN := FALSE);
Parameter | Description |
---|---|
gname |
Name of the replicated object group. |
all_sites |
If this is |
Exception | Description |
---|---|
nonmaster |
Invocation site is not a master site. |
commfailure |
At least one master site is not accessible and |
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.
This procedure drops a column group. You must call this procedure from the master definition site.
DBMS_REPCAT.DROP_COLUMN_GROUP ( sname IN VARCHAR2, oname IN VARCHAR2, column_group IN VARCHAR2);
This procedure removes members from a column group. You must call this procedure from the master definition site.
DBMS_REPCAT.DROP_GROUPED_COLUMN ( sname IN VARCHAR2, oname IN VARCHAR2, column_group IN VARCHAR2, list_of_column_names IN VARCHAR2 | DBMS_REPCAT.VARCHAR2S);
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. |
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
.
DBMS_REPCAT.DROP_MASTER_REPGROUP ( gname IN VARCHAR2, drop_contents IN BOOLEAN := FALSE, all_sites IN BOOLEAN := FALSE);
This procedure drops a replicated object from a replicated object group. You must call this procedure from the master definition site.
DBMS_REPCAT.DROP_MASTER_REPOBJECT ( sname IN VARCHAR2, oname IN VARCHAR2, type IN VARCHAR2, drop_objects IN BOOLEAN := FALSE);
This procedure drops a member of a priority group by priority level. You must call this procedure from the master definition site.
DBMS_REPCAT.DROP_PRIORITY( gname IN VARCHAR2, pgroup IN VARCHAR2, priority_num IN NUMBER);
This procedure drops a priority group for a given replicated object group. You must call this procedure from the master definition site.
DBMS_REPCAT.DROP_PRIORITY_GROUP ( gname IN VARCHAR2, pgroup IN VARCHAR2);
Parameter | Description |
---|---|
gname |
Replicated object group with which the priority group is associated. |
pgroup |
Name of the priority group that you want to drop. |
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.
DBMS_REPCAT.DROP_PRIORITY_datatype ( gname IN VARCHAR2, pgroup IN VARCHAR2, value IN datatype);
where datatype:
{ NUMBER | VARCHAR2 | CHAR | DATE | RAW | NCHAR | NVARCHAR2 }
This procedure drops a site priority group for a given replicated object group. You must call this procedure from the master definition site.
DBMS_REPCAT.DROP_SITE_PRIORITY ( gname IN VARCHAR2, name IN VARCHAR2);
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. |
This procedure drops a given site, by name, from a site priority group. You must call this procedure from the master definition site.
DBMS_REPCAT.DROP_SITE_PRIORITY_SITE ( gname IN VARCHAR2, name IN VARCHAR2, site IN VARCHAR2);
This procedure drops a snapshot site from your replicated environment.
DBMS_REPCAT.DROP_SNAPSHOT_REPGROUP ( gname IN VARCHAR2, drop_contents IN BOOLEAN := FALSE);
Exception | Description |
---|---|
nonsnapshot |
Invocation site is not a snapshot site. |
missingrepgroup |
Specified object group does not exist. |
DROP_SNAPSHOT_REPGROUP
automatically calls UNREGISTER_SNAPSHOT_REPGROUP
to unregister the snapshot, but ignores any errors that may have occurred during unregistration.
This procedure drops a replicated object from a snapshot site.
DBMS_REPCAT.DROP_SNAPSHOT_REPOBJECT ( sname IN VARCHAR2, oname IN VARCHAR2, type IN VARCHAR2, drop_objects IN BOOLEAN := FALSE);
Exception | Description |
---|---|
nonsnapshot |
Invocation site is not a snapshot site. |
missingobject |
Given object does not exist. |
typefailure |
Given type parameter is not supported. |
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 |
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);
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.
DBMS_REPCAT.EXECUTE_DDL ( gname IN VARCHAR2, { master_list IN VARCHAR2 := NULL | master_table IN DBMS_UTILITY.DBLINK_ARRAY,} DDL_TEXT IN VARCHAR2);
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.
This procedure generates the triggers and packages needed to support replication. You must call this procedure from the master definition site.
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);
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: |
package_prefix |
For objects of type |
procedure_prefix |
For objects of type |
distributed |
This must be set to |
gen_objs_owner |
For objects of type |
min_communication |
Set to |
generate_80_ compatible |
Set to |
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.
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);
CREATE_SNAPSHOT_REPOBJECT
automatically generates snapshot support for updatable snapshots.
This procedure creates a new column group with one or more members. You must call this procedure from the master definition site.
DBMS_REPCAT.MAKE_COLUMN_GROUP ( sname IN VARCHAR2, oname IN VARCHAR2, column_group IN VARCHAR2, list_of_column_names IN VARCHAR2 | DBMS_REPCAT.VARCHAR2S);
This procedure removes local messages in the RepCatLog
associated with a given identification number, source, or replicated object group.
DBMS_REPCAT.PURGE_MASTER_LOG ( id IN NATURAL, source IN VARCHAR2, gname IN VARCHAR2);
Exception | Description |
---|---|
nonmaster |
|
This procedure removes information from the RepResolution_Statistics
view.
DBMS_REPCAT.PURGE_STATISTICS ( sname IN VARCHAR2, oname IN VARCHAR2, start_date IN DATE, end_date IN DATE);
Exception | Description |
---|---|
missingschema |
Given schema does not exist. |
missingobject |
Given table does not exist. |
statnotreg |
Table not registered to collect statistics. |
This procedure refreshes a snapshot site object group with the most recent data from its associated master site.
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);
This procedure facilitates the administration of snapshots at their respective master sites by inserting/modifying/deleting from registered_snapshot_groups
.
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);
This procedure collects information about the successful resolution of update, delete, and uniqueness conflicts for a table.
DBMS_REPCAT.REGISTER_STATISTICS ( sname IN VARCHAR2, oname IN VARCHAR2);
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. |
Exception | Description |
---|---|
missingschema |
Given schema does not exist. |
missingobject |
Given table does not exist. |
This procedure changes your master definition site to another master site in your replicated environment.
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);
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
.
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.
DBMS_REPCAT.REMOVE_MASTER_DATABASES ( gname IN VARCHAR2, master_list IN VARCHAR2 | master_table IN DBMS_UTILITY.DBLINK_ARRAY);
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.
DBMS_REPCAT.REPCAT_IMPORT_CHECK ( gname IN VARCHAR2, master IN BOOLEAN);
This procedure resumes normal replication activity after quiescing a replicated environment.
DBMS_REPCAT.RESUME_MASTER_ACTIVITY ( gname IN VARCHAR2, override IN BOOLEAN := FALSE);
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.
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:
The Read "Minimizing Data Propagation for Update Conflict Resolution" in the Oracle8i Replication manual before changing the default behavior of Oracle. |
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.
DBMS_REPCAT.SET_COLUMNS ( sname IN VARCHAR2, oname IN VARCHAR2, { column_list IN VARCHAR2 | column_table IN DBMS_UTILITY.NAME_ARRAY } );
This procedure suspends replication activity for an object group. You must call this procedure from the master definition site.
DBMS_REPCAT.SUSPEND_MASTER_ACTIVITY ( gname IN VARCHAR2);
Parameter | Description |
---|---|
gname |
Name of the object group for which you want to suspend activity. |
The current implementation of SUSPEND_MASTER_ACTIVITY
quiesces all replicated object groups at each master site.
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.
DBMS_REPCAT.SWITCH_SNAPSHOT_MASTER ( gname IN VARCHAR2, master IN VARCHAR2);
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. |
Exception | Description |
---|---|
nonsnapshot |
Invocation site is not a snapshot site. |
nonmaster |
Given database is not a master site. |
commfailure |
Given database is not accessible. |
This procedure facilitates the administration of snapshots at their respective master sites by inserting/modifying/deleting from registered_snapshot_groups
.
DBMS_REPCAT.UNREGISTER_SNAPSHOT_REPGROUP ( gname IN VARCHAR2, snapsite IN VARCHAR2);
Parameter | Description |
---|---|
gname |
Name of the snapshot object group to be unregistered. |
snapsite |
Global name of the snapshot site. |
This function validates the correctness of key conditions of a multiple master replication environment. This is overloaded.
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;
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.
This procedure determines whether changes that were asynchronously propagated to a master site have been applied.
DBMS_REPCAT.WAIT_MASTER_LOG ( gname IN VARCHAR2, record_count IN NATURAL, timeout IN NATURAL, true_count OUT NATURAL);
Exception | Description |
---|---|
nonmaster |
Invocation site is not a master site. |