Release 2 (9.2)
Part Number A96568-01
 Home |
 Book List |
 Contents |
 Index |
 Master Index |
 Feedback |
| Oracle9i Replication Management API Reference Release 2 (9.2) Part Number A96568-01 |
|
DBMS_REPCAT provides routines to administer and update the replication catalog and environment.
This chapter discusses the following topics:
| Subprogram | Description |
|---|---|
|
Adds members to an existing column group. |
|
|
Adds another master site to your replication environment. |
|
|
Adds the master sites in the |
|
|
Adds a member to a priority group. |
|
|
Adds a new site to a site priority group. |
|
|
Designates a method for resolving an update, delete, or uniqueness conflict. |
|
|
Alters the values for parameters stored in the |
|
|
Alters the propagation method for a specified replication group at a specified master site. |
|
|
Alters an object in your replication environment. |
|
|
Alters the propagation method for a specified replication group at the current materialized view site. |
|
|
Alters the priority level associated with a specified priority group member. |
|
|
Alters the value of a member in a priority group. |
|
|
Alters the priority level associated with a specified site. |
|
|
Alters the site associated with a specified priority level. |
|
|
Stops collecting statistics about the successful resolution of update, uniqueness, and delete conflicts for a table. |
|
|
Updates the comment field in the |
|
|
Updates the |
|
|
"COMMENT_ON_PRIORITY_GROUP/COMMENT_ON_SITE_PRIORITY Procedures" |
Updates the comment field in the |
|
Updates the comment field in the |
|
|
Updates the comment field in the |
|
|
Updates the comment field in the |
|
|
Updates the comment field in the |
|
|
Specifies whether to compare old column values at each master site for each nonkey column of a replicated table for updates and deletes. |
|
|
Creates a new, empty, quiesced master group. |
|
|
Specifies that an object is a replicated object. |
|
|
Creates a new, empty materialized view group in your local database. |
|
|
Adds a replicated object to a materialized view group. |
|
|
Creates an empty column group. |
|
|
Creates a new priority group for a master group. |
|
|
Creates a new site priority group for a master group. |
|
|
Executes the local outstanding deferred administrative procedures for the specified master group at the current master site, or for all master sites. |
|
|
Drops a column group. |
|
|
Removes members from a column group. |
|
|
Drops a master group from your current site. |
|
|
Drops a replicated object from a master group. |
|
|
Drops a replicated object from a master group. |
|
|
Drops a materialized view site from your replication environment. |
|
|
Drops a replicated object from a materialized view site. |
|
|
Drops a member of a priority group by priority level. |
|
|
Drops a priority group for a specified master group. |
|
|
Drops a member of a priority group by value. |
|
|
Drops a site priority group for a specified master group. |
|
|
Drops a specified site, by name, from a site priority group. |
|
|
Drops an update, delete, or uniqueness conflict resolution method. |
|
|
Supplies DDL that you want to have executed at each master site. |
|
|
Activates triggers and generate packages needed to support the replication of updatable materialized views or procedural replication. |
|
|
Generates the triggers, packages, and procedures needed to support replication for a specified object. |
|
|
Creates a new column group with one or more members. |
|
|
Changes the global name of the database you are adding to a master group. |
|
|
Removes local messages in the |
|
|
Removes information from the |
|
|
Refreshes a materialized view group with the most recent data from its associated master site or master materialized view site. |
|
|
Facilitates the administration of materialized views at their respective master sites or master materialized view sites by inserting, modifying, or deleting from |
|
|
Collects information about the successful resolution of update, delete, and uniqueness conflicts for a table. |
|
|
Changes your master definition site to another master site in your replication environment. |
|
|
Removes one or more master databases from a replication environment. |
|
|
Renames the shadow column group of a replicated table to make it a named column group. |
|
|
Ensures that the objects in the master 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. |
|
|
Resumes normal replication activity after quiescing a replication environment. |
|
|
Indicates that export is effectively finished and propagation for both extended and unaffected replication groups existing at master sites can be enabled. |
|
|
Specifies whether to send old column values for each nonkey column of a replicated table for updates and deletes. |
|
|
Specifies use of 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. |
|
|
Specifies the master sites you intend to add to an existing replication group without quiescing the group. |
|
|
Suspends replication activity for a master group. |
|
|
Changes the master site of a materialized view group to another master site. |
|
|
Undoes all of the changes made by the |
|
|
Facilitates the administration of materialized views at their respective master sites and master materialized view sites by inserting, modifying, or deleting from |
|
|
Validates the correctness of key conditions of a multimaster replication environment. |
|
|
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 replication 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);
This procedure adds the master sites in the DBA_REPSITES_NEW data dictionary view to the master groups specified when the SPECIFY_NEW_MASTERS procedure was run. Information about these new master sites are added to the replication catalog at all available master sites.
All master sites instantiated with object-level export/import must be accessible at this time. Their new replication groups are added in the quiesced state. Master sites instantiated through full database export/import or through changed-based recovery do not need to be accessible.
Run this procedure after you run the SPECIFY_NEW_MASTERS procedure.
See Also:
|
DBMS_REPCAT.ADD_NEW_MASTERS ( export_required IN BOOLEAN, { available_master_list IN VARCHAR2, | available_master_table IN DBMS_UTILITY.DBLINK_ARRAY,} masterdef_flashback_scn OUT NUMBER, extension_id OUT RAW, break_trans_to_masterdef IN BOOLEAN := false, break_trans_to_new_masters IN BOOLEAN := false, percentage_for_catchup_mdef IN BINARY_INTEGER := 100, cycle_seconds_mdef IN BINARY_INTEGER := 60, percentage_for_catchup_new IN BINARY_INTEGER := 100, cycle_seconds_new IN BINARY_INTEGER := 60);
|
Note: This procedure is overloaded. The |
For a new master site to be instantiated using change-based recovery or full database export/import, the following conditions apply:
For object-level export/import, before importing ensure that all the requests in the DBA_REPCATLOG data dictionary view for the extended groups have been processed without any error.
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:
Chapter 6, "Configure Conflict Resolution" and Oracle9i Replication for more information about conflict resolution methods |
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.
| See Also:
Chapter 6, "Configure Conflict Resolution" and Oracle9i Replication for more information about conflict resolution methods |
DBMS_REPCAT.ADD_SITE_PRIORITY_SITE ( gname IN VARCHAR2, name IN VARCHAR2 site IN VARCHAR2, priority IN NUMBER);
These procedures designate 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:
Chapter 6, "Configure Conflict Resolution" and Oracle9i Replication for more information about designating methods to resolve update conflicts, selecting uniqueness conflict resolution methods, and assigning delete conflict resolution methods |
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 | DBMS_UTILITY.LNAME_ARRAY, 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 | DBMS_UTILITY.LNAME_ARRAY, 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 to which you are adding a conflict resolution routine. The table can be the storage table of a nested table. |
column_group |
Name of the column group to 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 standard methods supported in this release for update conflicts are:
The standard methods supported in this release for uniqueness conflicts 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 For update or unique conflicts, this parameter accepts either a comma-delimited list of column names, or a PL/SQL index-by table of type For delete conflicts, this parameter accepts either a comma-delimited list of column names or a PL/SQL index-by table of type DBMS_REPCAT.VARCHAR2. The single value LOB columns cannot be specified for this parameter. See Also: "Usage Notes" if you are using column objects |
priority_group |
If you are using the See Chapter 6, "Configure Conflict Resolution" and Oracle9i Replication for more information. If you are using a different method, you can use the default value for this parameter, |
function_name |
If you selected the |
comment |
This user comment is added to the |
If you are using column objects, then whether you can specify the attributes of the column objects for the parameter_column_name parameter depends on whether the conflict resolution method is built-in (Oracle supplied) or user-created:
cust_address has street_address as an attribute, then you can specify cust_address.street_address for this parameter.REF, or an entire column object.cust_address has street_address as an attribute (among other attributes), then you can specify only cust_address for this parameter.This procedure alters the values for the following parameters stored in the DBA_REPEXTENSIONS data dictionary view:
These parameters were originally set by the ADD_NEW_MASTERS procedure. The new values you specify for these parameters are used during the remaining steps in the process of adding new master sites to a master group. These changes are only to the site at which it is executed. Therefore, it must be executed at each master site, including the master definition site, if you want to alter parameters at all sites.
See Also:
|
DBMS_REPCAT.ALTER_CATCHUP_PARAMETERS ( extension_id IN RAW, percentage_for_catchup_mdef IN BINARY_INTEGER := NULL, cycle_seconds_mdef IN BINARY_INTEGER := NULL, percentage_for_catchup_new IN BINARY_INTEGER := NULL, cycle_seconds_new IN BINARY_INTEGER := NULL);
This procedure alters the propagation method for a specified replication group at a specified master site. This replication 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 := '');
|
Note: This procedure is overloaded. The |
This procedure alters an object in your replication environment. You must call this procedure from the master definition site.
This procedure requires that you quiesce the master group of the object if either of the following conditions is true:
safe_table_change parameter set to false in a single master replication environment.You can use this procedure to alter nontable objects without quiescing the master group.
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 safe_table_change IN BOOLEAN := false);
This procedure alters the propagation method for a specified replication group at the current materialized view site. This procedure pushes the deferred transaction queue at the materialized view site, locks the materialized view base tables, and regenerates any triggers and their associated packages. You must call this procedure from the materialized view site.
DBMS_REPCAT.ALTER_MVIEW_PROPAGATION ( gname IN VARCHAR2, propagation_mode IN VARCHAR2, comment IN VARCHAR2 := '', gowner IN VARCHAR2 := 'PUBLIC');
This procedure alters the priority level associated with a specified priority group member. You must call this procedure from the master definition site.
| See Also:
Chapter 6, "Configure Conflict Resolution" and Oracle9i Replication for more information about conflict resolution methods |
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.
| See Also:
Chapter 6, "Configure Conflict Resolution" and Oracle9i Replication for more information about conflict resolution methods |
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 specified site. You must call this procedure from the master definition site.
| See Also:
Chapter 6, "Configure Conflict Resolution" and Oracle9i Replication for more information about conflict resolution methods |
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 specified priority level. You must call this procedure from the master definition site.
| See Also:
Chapter 6, "Configure Conflict Resolution" and Oracle9i Replication for more information about conflict resolution methods |
DBMS_REPCAT.ALTER_SITE_PRIORITY_SITE ( gname IN VARCHAR2, name IN VARCHAR2, old_site IN VARCHAR2, new_site IN VARCHAR2);
This procedure stops the collection of 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 |
Specified schema does not exist. |
missingobject |
Specified table does not exist. |
statnotreg |
Specified table is not currently registered to collect statistics. |
This procedure updates the comment field in the DBA_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 |
Specified column group does not exist. |
missingobj |
Object is missing. |
This procedure updates the SCHEMA_COMMENT field in the DBA_REPGROUP data dictionary view for the specified materialized view group. The group name must be registered locally as a replicated materialized view group. This procedure must be executed at the materialized view site.
DBMS_REPCAT.COMMENT_ON_MVIEW_REPSITES ( gowner IN VARCHAR2, gname IN VARCHAR2, comment IN VARCHAR2);
| Parameter | Description |
|---|---|
gowner |
Owner of the materialized view group. |
gname |
Name of the materialized view group. |
comment |
Updated comment to include in the |
| Parameter | Description |
|---|---|
missingrepgroup |
The materialized view group does not exist. |
nonmview |
The connected site is not a materialized view site. |
COMMENT_ON_PRIORITY_GROUP updates the comment field in the DBA_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 DBA_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 DBA_REPGROUP view for a master 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 replication 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 DBA_REPOBJECT view for a replicated object in a master group. 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);
If the replication group is a master group, then this procedure updates the MASTER_COMMENT field in the DBA_REPSITES view for a master site. If the replication group is a materialized view group, this procedure updates the SCHEMA_COMMENT field in the DBA_REPGROUP view for a materialized view site.
This procedure can be executed at either a master site or a materialized view site. If you execute this procedure on a a materialized view site, then the materialized view group owner must be PUBLIC.
| See Also:
"COMMENT_ON_conflicttype_RESOLUTION Procedure" for instructions on placing a comment in the |
DBMS_REPCAT.COMMENT_ON_REPSITES ( gname IN VARCHAR2, [ master IN VARCHAR,] comment IN VARCHAR2);
This procedure updates the RESOLUTION_COMMENT field in the DBA_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);
This procedure specifies whether to compare old column values during propagation of deferred transactions at each master site for each nonkey 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 sites and materialized view sites by invoking DBMS_REPCAT.COMPARE_OLD_VALUES at the master definition site.
When you use user-defined types, you can specify leaf attributes of a column object, or you can specify an entire column object. For example, if a column object named cust_address has street_address as an attribute, then you can specify cust_address.street_address for the column_list parameter or as part of the column_table parameter, or you can specify only cust_address.
When performing equality comparisons for conflict detection, Oracle treats objects as equal only if one of the following conditions is true:
NULL (the entire object is NULL)Given these conditions, if one object is atomically NULL while the other is not, then Oracle does not consider the objects to be equal. Oracle does not consider MAP and ORDER methods when performing equality comparisons.
DBMS_REPCAT.COMPARE_OLD_VALUES( sname IN VARCHAR2, oname IN VARCHAR2, { column_list IN VARCHAR2, | column_table IN DBMS_UTILITY.VARCHAR2s | DBMS_UTILITY.LNAME_ARRAY,} operation IN VARCHAR2 := 'UPDATE', compare IN BOOLEAN := true );
|
Note: This procedure is overloaded. The |
|
Note: The See Oracle9i Replication for more information about reduced data propagation using the |
This procedure creates a new, empty, quiesced master 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 master 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 master group. Be sure to use the @ sign. See Oracle9i Replication and Oracle9i Database Administrator's Guide for more information about connection qualifiers. |
This procedure makes an object a replicated object by adding the object to a master group. This procedure preserves the object identifier for user-defined types and object tables at all replication sites.
Replication of clustered tables is supported, but the use_existing_object parameter cannot be set to false for clustered tables. In other words, you must create the clustered table at all master sites participating in the master group before you execute the CREATE_MASTER_REPOBJECT procedure. However, these tables do not need to contain the table data. So, the copy_rows parameter can be set to true for clustered tables.
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 := '');
The following table describes the parameters for this procedure.
| 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 following types are supported:
|
use_existing_object |
Indicate Note: This parameter must be set to |
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. If the DDL is supplied without specifying a schema ( Note: Do not use the |
comment |
This comment is added to the |
retry |
Indicate |
copy_rows |
Indicate |
gname |
Name of the replication group in which you want to create the replicated object. The schema name is used as the default replication group name if none is specified, and a replication group with the same name as the schema must exist for the procedure to complete successfully in that case. |
This procedure creates a new, empty materialized view group in your local database. CREATE_MVIEW_REPGROUP automatically calls REGISTER_MIEW_REPGROUP, but ignores any errors that may have happened during registration.
DBMS_REPCAT.CREATE_MVIEW_REPGROUP ( gname IN VARCHAR2, master IN VARCHAR2, comment IN VARCHAR2 := '', propagation_mode IN VARCHAR2 := 'ASYNCHRONOUS', fname IN VARCHAR2 := NULL gowner IN VARCHAR2 := 'PUBLIC');
| Parameter | Description |
|---|---|
gname |
Name of the replication group. This group must exist at the specified master site or master materialized view site. |
master |
Fully qualified database name of the database in the replication environment to use as the master site or master materialized view site. You can include a connection qualifier if necessary. See Oracle9i Replication and Oracle9i Database Administrator's Guide for information about using connection qualifiers. |
comment |
This comment is added to the |
propagation_mode |
Method of propagation for all updatable materialized views in the replication group. Acceptable values are |
fname |
This parameter is for internal use only. Note: Do not set this parameter unless directed to do so by Oracle Support Services. |
gowner |
Owner of the materialized view group. |
This procedure adds a replicated object to a materialized view group.
DBMS_REPCAT.CREATE_MVIEW_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, gowner IN VARCHAR2 := 'PUBLIC');
| Parameter | Description |
|---|---|
sname |
Name of the schema in which the object is located. The schema must be same as the schema that owns the master table or master materialized view on which this materialized view is based. |
oname |
Name of the object that you want to add to the replicated materialized view group. |
type |
Type of the object that you are replicating. The following types are supported:
|
ddl_text |
For objects of type '' (an empty string) If a materialized view with the same name already exists, then Oracle ignores the DDL and registers the existing materialized view as a replicated object. If the master table or master materialized view for a materialized view does not exist in the replication group of the master designated for this schema, then Oracle raises a 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. If the object is not of type |
comment |
This comment is added to the |
gname |
Name of the replicated materialized view group to which you are adding an object. The schema name is used as the default group name if none is specified, and a materialized view group with the same name as the schema must exist for the procedure to complete successfully. |
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 |
gowner |
Owner of the materialized view group. |
This procedure creates an empty column group. You must call this procedure from the master definition site.
| See Also:
Chapter 6, "Configure Conflict Resolution" and Oracle9i Replication for more information about conflict resolution methods |
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 master group. You must call this procedure from the master definition site.
| See Also:
Chapter 6, "Configure Conflict Resolution" and Oracle9i Replication for more information about conflict resolution methods |
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 master group. You must call this procedure from the master definition site.
| See Also:
Chapter 6, "Configure Conflict Resolution" and Oracle9i Replication for more information about conflict resolution methods |
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 specified master group at the current master site, or (with assistance from job queues) for all master sites.
DO_DEFERRED_REPCAT_ADMIN executes only those administrative requests submitted by the connected user who called DO_DEFERRED_REPCAT_ADMIN. Requests submitted by other users are ignored.
DBMS_REPCAT.DO_DEFERRED_REPCAT_ADMIN ( gname IN VARCHAR2, all_sites IN BOOLEAN := false);
| Parameter | Description |
|---|---|
gname |
Name of the master 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 |
This procedure drops a column group. You must call this procedure from the master definition site.
| See Also:
Chapter 6, "Configure Conflict Resolution" and Oracle9i Replication for more information about conflict resolution methods |
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.
| See Also:
Chapter 6, "Configure Conflict Resolution" and Oracle9i Replication for more information about conflict resolution methods |
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 master definition site. |
missingobject |
Specified table does not exist. |
notquiesced |
Master group that the table belongs to is not quiesced. |
This procedure drops a master group from your current site. To drop the master group from all master sites, including the master definition site, you can call this procedure at the master definition site, and set all_sites 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 master 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 materialized view site from your replication environment. DROP_MVIEW_REPGROUP automatically calls UNREGISTER_MVIEW_REPGROUP at the master site or master materialized view site to unregister the materialized view, but ignores any errors that may have occurred during unregistration. If DROP_MVIEW_REPGROUP is unsuccessful, then connect to the master site or master materialized view site and run UNREGISTER_MVIEW_REPGROUP.
DBMS_REPCAT.DROP_MVIEW_REPGROUP ( gname IN VARCHAR2, drop_contents IN BOOLEAN := false, gowner IN VARCHAR2 := 'PUBLIC');
| Exception | Description |
|---|---|
nonmview |
Invocation site is not a materialized view site. |
missingrepgroup |
Specified replication group does not exist. |
This procedure drops a replicated object from a materialized view site.
DBMS_REPCAT.DROP_MVIEW_REPOBJECT ( sname IN VARCHAR2, oname IN VARCHAR2, type IN VARCHAR2, drop_objects IN BOOLEAN := false);
| Exception | Description |
|---|---|
nonmview |
Invocation site is not a materialized view site. |
missingobject |
Specified object does not exist. |
typefailure |
Specified type parameter is not supported. |
This procedure drops a member of a priority group by priority level. You must call this procedure from the master definition site.
| See Also:
Chapter 6, "Configure Conflict Resolution" and Oracle9i Replication for more information about conflict resolution methods |
DBMS_REPCAT.DROP_PRIORITY( gname IN VARCHAR2, pgroup IN VARCHAR2, priority_num IN NUMBER);
This procedure drops a priority group for a specified master group. You must call this procedure from the master definition site.
| See Also:
Chapter 6, "Configure Conflict Resolution" and Oracle9i Replication for more information about conflict resolution methods |
DBMS_REPCAT.DROP_PRIORITY_GROUP ( gname IN VARCHAR2, pgroup IN VARCHAR2);
| Parameter | Description |
|---|---|
gname |
Master 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.
| See Also:
Chapter 6, "Configure Conflict Resolution" and Oracle9i Replication for more information about conflict resolution methods |
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 specified master group. You must call this procedure from the master definition site.
| See Also:
Chapter 6, "Configure Conflict Resolution" and Oracle9i Replication for more information about conflict resolution methods |
DBMS_REPCAT.DROP_SITE_PRIORITY ( gname IN VARCHAR2, name IN VARCHAR2);
| Parameter | Description |
|---|---|
gname |
Master 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 specified site, by name, from a site priority group. You must call this procedure from the master definition site.
| See Also:
Chapter 6, "Configure Conflict Resolution" and Oracle9i Replication for more information about conflict resolution methods |
DBMS_REPCAT.DROP_SITE_PRIORITY_SITE ( gname IN VARCHAR2, name IN VARCHAR2, site IN VARCHAR2);
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.
The following table shows the procedure name for each conflict resolution routine.
| Routine | 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);
|
Note: This procedure is overloaded. The |
This procedure activates triggers and generate packages needed to support the replication of updatable materialized views or procedural replication.You must call this procedure from the materialized view site.
|
Note:
|
DBMS_REPCAT.GENERATE_MVIEW_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);
This procedure generates the triggers and packages needed to support replication for a specified object. 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 creates a new column group with one or more members. You must call this procedure from the master definition site.
| See Also:
Chapter 6, "Configure Conflict Resolution" and Oracle9i Replication for more information about conflict resolution methods |
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 enables the propagation of deferred transactions from other prepared new master sites and existing master sites to the invocation master site. This procedure also enables the propagation of deferred transactions from the invocation master site to the other prepared new master sites and existing master sites.
If you performed a full database export/import or a change-based recovery, then the new master site includes all of the deferred transactions that were in the deferred transactions queue at the master definition site. Because these deferred transactions should not exist at the new master site, this procedure deletes all transactions in the deferred transactions queue and error queue if full database export/import or change-based recovery was used.
For object-level export/import, ensure that all the requests in the DBA_REPCATLOG data dictionary view for the extended groups have been processed without error before running this procedure.
|
Note: To use change-based recovery, the existing master site and the new master site must be running under the same operating system, although the release of the operating system can differ. |
DBMS_REPCAT.PREPARE_INSTANTIATED_MASTER ( extension_id IN RAW);
This procedure removes local messages in the DBA_REPCATLOG view associated with a specified identification number, source, or master group.
To purge all of the administrative requests from a particular source, specify NULL for the id parameter. To purge all administrative requests from all sources, specify NULL for both the id parameter and the source parameter.
DBMS_REPCAT.PURGE_MASTER_LOG ( id IN BINARY_INTEGER, source IN VARCHAR2, gname IN VARCHAR2);
| Exception | Description |
|---|---|
nonmaster |
|
This procedure removes information from the DBA_REPRESOLUTION_STATISTICS view.
DBMS_REPCAT.PURGE_STATISTICS ( sname IN VARCHAR2, oname IN VARCHAR2, start_date IN DATE, end_date IN DATE);
| Exception | Description |
|---|---|
missingschema |
Specified schema does not exist. |
missingobject |
Specified table does not exist. |
statnotreg |
Table not registered to collect statistics. |
This procedure refreshes a materialized view group with the most recent data from its associated master site or master materialized view site.
DBMS_REPCAT.REFRESH_MVIEW_REPGROUP ( gname IN VARCHAR2, drop_missing_contents IN BOOLEAN := false, refresh_mviews IN BOOLEAN := false, refresh_other_objects IN BOOLEAN := false, gowner IN VARCHAR2 := 'PUBLIC');
This procedure facilitates the administration of materialized views at their respective master sites or master materialized view sites by inserting or modifying a materialized view group in DBA_REGISTERED_MVIEW_GROUPS.
DBMS_REPCAT.REGISTER_MVIEW_REPGROUP ( gname IN VARCHAR2, mviewsite IN VARCHAR2, comment IN VARCHAR2 := NULL, rep_type IN NUMBER := reg_unknown, fname IN VARCHAR2 := NULL, gowner IN VARCHAR2 := 'PUBLIC');
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 |
Specified schema does not exist. |
missingobject |
Specified table does not exist. |
This procedure changes your master definition site to another master site in your replication environment.
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 set to true and include_old_masterdef set to true.
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);
This procedure removes one or more master databases from a replication 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);
|
Note: This procedure is overloaded. The |
This procedure renames the shadow column group of a replicated table to make it a named column group. The replicated table's master group does not need to be quiesced to run this procedure.
DBMS_REPCAT.RENAME_SHADOW_COLUMN_GROUP ( sname IN VARCHAR2, oname IN VARCHAR2, new_col_group_name IN VARCHAR2)
This procedure ensures that the objects in the master group have the appropriate object identifiers and status values after you perform an export/import of a replicated object or an object used by Advanced Replication.
DBMS_REPCAT.REPCAT_IMPORT_CHECK ( gname IN VARCHAR2, master IN BOOLEAN, gowner IN VARCHAR2 := 'PUBLIC');
This procedure resumes normal replication activity after quiescing a replication environment.
DBMS_REPCAT.RESUME_MASTER_ACTIVITY ( gname IN VARCHAR2, override IN BOOLEAN := false);
During the process of adding new master sites to a master group without quiesce, this procedure indicates that export is effectively finished and propagation to the master definition site for both extended and unaffected replication groups existing at master sites can be enabled. Run this procedure after the export required to add new master sites to a master group is complete.
| See Also:
"Adding New Master Sites" for more information about adding master sites to a master group |
DBMS_REPCAT.RESUME_PROPAGATION_TO_MDEF ( extension_id IN RAW);
You have the option of sending old column values during propagation of deferred transactions for each nonkey column of a replicated table when rows are updated or deleted in the table. When min_communication is set to true, the default is the following:
You can change this behavior at all master sites and materialized view sites by invoking DBMS_REPCAT.SEND_OLD_VALUES at the master definition site. Then, generate replication support at all master sites and at each materialized view site.
When you use user-defined types, you can specify the leaf attributes of a column object, or an entire column object. For example, if a column object named cust_address has street_address as an attribute, then you can specify cust_address.street_address for the column_list parameter or as part of the column_table parameter, or you can specify only cust_address.
DBMS_REPCAT.SEND_OLD_VALUES( sname IN VARCHAR2, oname IN VARCHAR2, { column_list IN VARCHAR2, | column_table IN DBMS_UTILITY.VARCHAR2s | DBMS_UTILITY.LNAME_ARRAY,} operation IN VARCHAR2 := 'UPDATE', send IN BOOLEAN := true );
|
Note: This procedure is overloaded. The |
|
Note: The See Oracle9i Replication for information about reduced data propagation using the |
This procedure enables you 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.
When you use column objects, if an attribute of a column object can be used as a primary key or part of a primary key, then the attribute can be part of an alternate key column. For example, if a column object named cust_address has street_address as a VARCHAR2 attribute, then you can specify cust_address.street_address for the column_list parameter or as part of the column_table parameter. However, the entire column object, cust_address, cannot be specified.
For the storage table of a nested table column, this procedure accepts the NESTED_TABLE_ID as an alternate key column.
When you use object tables, you cannot specify alternate key columns. If the object identifier (OID) is system-generated for an object table, then Oracle uses the OID column in the object table as the key for the object table. If the OID is user-defined for an object table, then Oracle uses the primary key in the object table as the key.
The following types of columns cannot be alternate key columns:
REF| See Also:
The constraint_clause in Oracle9i SQL Reference for more information about restrictions on primary key columns |
DBMS_REPCAT.SET_COLUMNS ( sname IN VARCHAR2, oname IN VARCHAR2, { column_list IN VARCHAR2 | column_table IN DBMS_UTILITY.NAME_ARRAY | DBMS_UTILITY.LNAME_ARRAY } );
|
Note: This procedure is overloaded. The |
This procedure specifies the master sites you intend to add to an existing replication group without quiescing the group. This procedure must be run at the master definition site of the specified master group.
If necessary, this procedure creates an extension_id that tracks the process of adding new master sites to a master group. You use this extension_id in the other procedures that you run at various stages in the process. You can view information about the extension_id in the DBA_REPSITES_NEW and DBA_REPEXTENSIONS data dictionary views.
This procedure adds the new master sites to the DBA_REPSITES_NEW data dictionary view for the specified replication group. This procedure can be run any number of times for a given replication group. If it is run more than once, then it replaces any masters in the local DBA_REPSITES_NEW data dictionary view for the specified replication group with the masters specified in the master_list/master_table parameters.
You must run this procedure before you run the ADD_NEW_MASTERS procedure. No new master sites are added to the master group until you run the ADD_NEW_MASTERS procedure.
See Also:
|
DBMS_REPCAT.SPECIFY_NEW_MASTERS ( gname IN VARCHAR2, { master_list IN VARCHAR2 | master_table IN DBMS_UTILITY.DBLINK_ARRAY});
|
Note: This procedure is overloaded. The |
This procedure suspends replication activity for a master group. You use this procedure to quiesce the master 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 master group for which you want to suspend activity. |
| Exception | Description |
|---|---|
nonmasterdef |
Invocation site is not the master definition site. |
notnormal |
Master group is not in normal operation. |
commfailure |
At least one master site is not accessible. |
This procedure changes the master site of a materialized view group to another master site. This procedure does a full refresh of the affected materialized views and regenerates the triggers and their associated packages as needed. This procedure does not push the queue to the old master site before changing master sites.
If min_communication is true for the materialized view and the new master site is an Oracle7 master site, then regenerate replication support for the materialized view with min_communication set to false.
If generate_80_compatible is false for the materialized view and the new master site is a release lower than Oracle8i (Oracle7 or Oracle8), then regenerate replication support for the materialized view with generate_80_compatible set to true.
You can set both parameters for a materialized view in one call to DBMS_REPCAT.GENERATE_MVIEW_SUPPORT.
DBMS_REPCAT.SWITCH_MVIEW_MASTER ( gname IN VARCHAR2, master IN VARCHAR2, gowner IN VARCHAR2 := 'PUBLIC');
This procedure undoes all of the changes made by the SPECIFY_NEW_MASTERS and ADD_NEW_MASTERS procedures for a specified extension_id.
This procedure is executed at one master site, which may be the master definition site, and it only affects that master site. If you run this procedure at one master site affected by the request, you must run it at all new and existing master sites affected by the request. You can query the DBA_REPSITES_NEW data dictionary view to see the new master sites affected by the extension_id. This data dictionary view also lists the replication group name, and you must run this procedure at all existing master sites in the replication group.
DBMS_REPCAT.UNDO_ADD_NEW_MASTERS_REQUEST ( extension_id IN RAW, drop_contents IN BOOLEAN := TRUE);
This procedure facilitates the administration of materialized views at their respective master sites or master materialized view sites by deleting a materialized view group from DBA_REGISTERED_MVIEW_GROUPS. Run this procedure at the master site or master materialized view site.
DBMS_REPCAT.UNREGISTER_MVIEW_REPGROUP ( gname IN VARCHAR2, mviewsite IN VARCHAR2, gowner IN VARCHAR2 := 'PUBLIC');
| Parameter | Description |
|---|---|
gname |
Name of the materialized view group to be unregistered. |
mviewsite |
Global name of the materialized view site. |
gowner |
Owner of the materialized view group. |
This function validates the correctness of key conditions of a multimaster replication environment.
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;
|
Note: This function is overloaded. The return value of The second interface function shown under "Syntax" is similar except that there are two |
The return value of VALIDATE is the number of errors found. The function's OUT parameter 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. |
|
 Copyright © 1996, 2002 Oracle Corporation. All Rights Reserved. |
|