18 DBMS_REPCAT

"ADD_GROUPED_COLUMN Procedure"

Adds members to an existing column group.

"ADD_MASTER_DATABASE Procedure"

Adds another master site to your replication environment.

"ADD_NEW_MASTERS Procedure"

Adds the master sites in the DBA_REPSITES_NEW data dictionary view to the replication catalog at all available master sites.

"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_CATCHUP_PARAMETERS Procedure"

Alters the values for parameters stored in the DBA_REPEXTENSIONS data dictionary view.

"ALTER_MASTER_PROPAGATION Procedure"

Alters the propagation method for a specified replication group at a specified master site.

"ALTER_MASTER_REPOBJECT Procedure"

Alters an object in your replication environment.

"ALTER_MVIEW_PROPAGATION Procedure"

Alters the propagation method for a specified replication group at the current materialized view site.

"ALTER_PRIORITY Procedure"

Alters the priority level associated with a specified 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 specified site.

"ALTER_SITE_PRIORITY_SITE Procedure"

Alters the site associated with a specified priority level.

"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 ALL_REPCOLUMN_GROUP view for a column group.

"COMMENT_ON_MVIEW_REPSITES Procedure"

Updates the SCHEMA_COMMENT field in the ALL_REPGROUP view for a materialized view site.

"COMMENT_ON_PRIORITY_GROUP Procedures"

Updates the comment field in the ALL_REPPRIORITY_GROUP view for a priority group.

"COMMENT_ON_REPGROUP Procedure"

Updates the comment field in the ALL_REPGROUP view for a master group.

"COMMENT_ON_REPOBJECT Procedure"

Updates the comment field in the ALL_REPOBJECT view for a replicated object.

"COMMENT_ON_REPSITES Procedure"

Updates the comment field in the ALL_REPSITE view for a replicated site.

"COMMENT_ON_SITE_PRIORITY Procedure"

Updates the comment field in the ALL_REPPRIORITY_GROUP view for a site priority group.

"COMMENT_ON_conflicttype_RESOLUTION Procedure"

Updates the comment field in the ALL_REPRESOLUTION view for a conflict resolution routine.

"COMPARE_OLD_VALUES Procedure"

Specifies whether to compare old column values at each master site for each nonkey column of a replicated table for updates and deletes.

"CREATE_MASTER_REPGROUP Procedure"

Creates a new, empty, quiesced master group.

"CREATE_MASTER_REPOBJECTProcedure"

Specifies that an object is a replicated object.

"CREATE_MVIEW_REPGROUP Procedure"

Creates a new, empty materialized view group in your local database.

"CREATE_MVIEW_REPOBJECT Procedure"

Adds a replicated object to a materialized view group.

"DEFINE_COLUMN_GROUP Procedure"

Creates an empty column group.

"DEFINE_PRIORITY_GROUP Procedure"

Creates a new priority group for a master group.

"DEFINE_SITE_PRIORITY Procedure"

Creates a new site priority group for a master group.

"DO_DEFERRED_REPCAT_ADMIN Procedure"

Executes the local outstanding deferred administrative procedures for the specified master 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 master group from your current site.

"DROP_MASTER_REPOBJECT Procedure"

Drops a replicated object from a master group.

"DROP_MVIEW_REPGROUP Procedure"

Drops a replicated object from a master group.

"DROP_MVIEW_REPGROUP Procedure"

Drops a materialized view site from your replication environment.

"DROP_MVIEW_REPOBJECT Procedure"

Drops a replicated object from a materialized view site.

"DROP_PRIORITY Procedure"

Drops a member of a priority group by priority level.

"DROP_PRIORITY_GROUP Procedure"

Drops a priority group for a specified master 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 specified master group.

"DROP_SITE_PRIORITY_SITE Procedure"

Drops a specified site, by name, from a site priority group.

"DROP_conflicttype_RESOLUTION Procedure"

Drops an update, delete, or uniqueness conflict resolution method.

"EXECUTE_DDL Procedure"

Supplies DDL that you want to have executed at each master site.

"GENERATE_MVIEW_SUPPORT Procedure"

Activates triggers and generate packages needed to support the replication of updatable materialized views or procedural replication.

"GENERATE_REPLICATION_SUPPORT Procedure"

Generates the triggers, packages, and procedures needed to support replication for a specified object.

"MAKE_COLUMN_GROUP Procedure"

Creates a new column group with one or more members.

"PREPARE_INSTANTIATED_MASTER Procedure"

Changes the global name of the database you are adding to a master group.

"PURGE_MASTER_LOG Procedure"

Removes local messages in the DBA_REPCATLOG associated with a specified identification number, source, or master group.

"PURGE_STATISTICS Procedure"

Removes information from the ALL_REPRESOLUTION_STATISTICS view.

"REFRESH_MVIEW_REPGROUP Procedure"

Refreshes a materialized view group with the most recent data from its associated master site or master materialized view site.

REGISTER_MVIEW_REPGROUP Procedure

Facilitates the administration of materialized views at their respective master sites or master materialized view sites by inserting, modifying, or deleting from DBA_REGISTERED_MVIEW_GROUPS.

"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 replication environment.

"REMOVE_MASTER_DATABASES Procedure"

Removes one or more master databases from a replication environment.

"RENAME_SHADOW_COLUMN_GROUP Procedure"

Renames the shadow column group of a replicated table to make it a named column group.

"REPCAT_IMPORT_CHECKProcedure"

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.

"RESUME_MASTER_ACTIVITY Procedure"

Resumes normal replication activity after quiescing a replication environment.

"RESUME_PROPAGATION_TO_MDEF Procedure"

Indicates that export is effectively finished and propagation for both extended and unaffected replication groups existing at master sites can be enabled.

"SEND_OLD_VALUES Procedure"

Specifies whether to send old column values for each nonkey column of a replicated table for updates and deletes.

"SET_COLUMNS Procedure"

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.

"SPECIFY_NEW_MASTERS Procedure"

Specifies the master sites you intend to add to an existing replication group without quiescing the group.

"STREAMS_MIGRATION Procedure"

Generates a migration script that migrates an Advanced Replication environment to a Streams environment.

"SUSPEND_MASTER_ACTIVITY Procedure"

Suspends replication activity for a master group.

"SWITCH_MVIEW_MASTER Procedure"

Changes the master site of a materialized view group to another master site.

"UNDO_ADD_NEW_MASTERS_REQUEST Procedure"

Undoes all of the changes made by the SPECIFY_NEW_MASTERS and ADD_NEW_MASTERS procedures for a specified extension_id.

"UNREGISTER_MVIEW_REPGROUP Procedure"

Facilitates the administration of materialized views at their respective master sites and master materialized view sites by inserting, modifying, or deleting from DBA_REGISTERED_MVIEW_GROUPS.

"VALIDATE Function"

Validates the correctness of key conditions of a multimaster replication environment.

"WAIT_MASTER_LOG Procedure"

Determines whether changes that were asynchronously propagated to a master site have been applied.

sname

Schema in which the replicated table is located.

oname

Name of the replicated table with which the column group is associated. The table can be the storage table of a nested table.

column_group

Name of the column group to which you are adding members.

list_of_column_names

Names of the columns that you are adding to the designated column group. This can either be a comma-delimited list or a PL/SQL index-by table of column names. The PL/SQL index-by table must be of type DBMS_REPCAT.VARCHAR2. Use the single value '*' to create a column group that contains all of the columns in your table.

You can specify column objects, but you cannot specify attributes of column objects.

If the table is an object, then you can specify SYS_NC_OID$ to add the object identifier column to the column group. This column tracks the object identifier of each row object.

If the table is a storage table of a nested table, then you can specify NESTED_TABLE_ID to add the column that tracks the identifier for each row of the nested table.

nonmasterdef

Invocation site is not the master definition site.

missingobject

Specified table does not exist.

missinggroup

Specified column group does not exist.

missingcolumn

Specified column does not exist in the specified table.

duplicatecolumn

Specified column is already a member of another column group.

missingschema

Specified schema does not exist.

notquiesced

Replication group to which the specified table belongs is not quiesced.

gname

Name of the replication group being replicated. This replication group must already exist at the master definition site.

master

Fully qualified database name of the new master database.

use_existing_objects

Indicate TRUE if you want to reuse any objects of the same type and shape that already exist in the schema at the new master site.

copy_rows

Indicate TRUE if you want the initial contents of a table at the new master site to match the contents of the table at the master definition site.

comment

This comment is added to the MASTER_COMMENT field of the DBA_REPSITES view.

propagation_mode

Method of forwarding changes to and receiving changes from new master database. Accepted values are synchronous and asynchronous.

fname

This parameter is for internal use only.

Note: Do not set this parameter unless directed to do so by Oracle Support Services.

nonmasterdef

Invocation site is not the master definition site.

notquiesced

Replication has not been suspended for the master group.

missingrepgroup

Replication group does not exist at the specified database site.

commfailure

New master is not accessible.

typefailure

An incorrect propagation mode was specified.

duplrepgrp

Master site already exists.

export_required

Set to TRUE if either object-level or full database export is required for at least one of the new master sites. Set to FALSE if you are using change-based recovery for all of the new master sites.

available_master_list

A comma-delimited list of the new master sites to be instantiated using object-level export/import. The sites listed must match the sites specified in the SPECIFY_NEW_MASTERS procedure. List only the new master sites, not the existing master sites. Do not put any spaces between site names.

Specify NULL if all masters will be instantiated using full database export/import or change-based recovery.

available_master_table

A table that lists the new master sites to be instantiated using object-level export/import. The sites in the table must match the sites specified in the SPECIFY_NEW_MASTERS procedure. Do not specify masters that will be instantiated using full database export/import or change-based recovery.

In the table that lists the master sites to be instantiated using object-level export/import, list only the new master sites for the master groups being extended. Do not list the existing master sites in the master groups being extended. The first master site should be at position 1, the second at position 2, and so on.

masterdef_flashback_scn

This OUT parameter returns a system change number (SCN) that must be used during export or change-based recovery. Use the value returned by this parameter for the FLASHBACK_SCN export parameter when you perform the export. You can find the flashback_scn value by querying the DBA_REPEXTENSIONS data dictionary view.

extension_id

This OUT parameter returns an identifier for the current pending request to add master databases without quiesce. You can find the extension_id by querying the DBA_REPSITES_NEW and DBA_REPEXTENSIONS data dictionary views.

break_trans_to_masterdef

This parameter is meaningful only if export_required is set to TRUE.

If break_trans_to_masterdef is set to TRUE, then existing masters can continue to propagate their deferred transactions to the master definition site for replication groups that are not adding master sites. Deferred transactions for replication groups that are adding master sites cannot be propagated until the export completes.

Each deferred transaction is composed of one or more remote procedure calls (RPCs). If set to FALSE and a transaction occurs that references objects in both unaffected master groups and master groups that are being extended, then the transaction might be split into two parts and sent to a destination in two separate transactions at different times. Such transactions are called split-transactions. If split-transactions are possible, then you must disable integrity constraints that might be violated by this behavior until the new master sites are added.

If break_trans_to_masterdef is set to FALSE, then existing masters cannot propagate their deferred transactions to the master definition site.

break_trans_to_new_masters

If break_trans_to_new_masters is set to TRUE, then existing master sites can continue to propagate deferred transactions to the new master sites for replication groups that are not adding master sites.

Each deferred transaction is composed of one or more remote procedure calls (RPCs). If set to TRUE and a transaction occurs that references objects in both unaffected master groups and master groups that are being extended, then the transaction might be split into two parts and sent to a destination in two separate transactions at different times. Such transactions are called split-transactions. If split-transactions are possible, then you must disable integrity constraints that might be violated by this behavior until the new master sites are added.

If break_trans_to_new_masters is set to FALSE, then propagation of deferred transaction queues to the new masters is disabled.

percentage_for_catchup_mdef

This parameter is meaningful only if export_required and break_trans_to_masterdef are both set to TRUE.

The percentage of propagation resources that should be used for catching up propagation to the master definition site. Must be a multiple of 10 and must be between 0 and 100.

cycle_seconds_mdef

This parameter is meaningful when percentage_for_catchup_mdef is both meaningful and set to a value between 10 and 90, inclusive. In this case, propagation to the master definition site alternates between replication groups that are not being extended and replication groups that are being extended, with one push to each during each cycle. This parameter indicates the length of the cycle in seconds.

percentage_for_catchup_new

This parameter is meaningful only if break_trans_to_new_masters is set to TRUE.

The percentage of propagation resources that should be used for catching up propagation to new master sites. Must be a multiple of 10 and must be between 0 and 100.

cycle_seconds_new

This parameter is meaningful when percentage_for_catchup_new is both meaningful and set to a value between 10 and 90, inclusive. In this case, propagation to a new master alternates between replication groups that are not being extended and replication groups that are being extended, with one push to each during each cycle. This parameter indicates the length of the cycle in seconds.

nonmasterdef

Invocation site is not the master definition site.

typefailure

The parameter value specified for one of the parameters is not appropriate.

novalidextreq

No valid extension request. The extension_id is not valid.

nonewsites

No new master sites to be added for the specified extension request.

notanewsite

Not a new site for extension request. A site was specified that was not specified when you ran the SPECIFY_NEW_MASTERS procedure.

dbnotcompatible

Feature is incompatible with database version. All databases must be at 9.0.1 or higher compatibility level.

gname

Master group for which you are creating a priority group.

pgroup

Name of the priority group.

value

Value of the priority group member. This is one of the possible values of the associated priority column of a table using this priority group.

priority

Priority of this value. The higher the number, the higher the priority.

nonmasterdef

Invocation site is not the master definition site.

duplicatevalue

Specified value already exists in the priority group.

duplicatepriority

Specified priority already exists in the priority group.

missingrepgroup

Specified master group does not exist.

missingprioritygroup

Specified priority group does not exist.

typefailure

Specified value has the incorrect data type for the priority group.

notquiesced

Specified master group is not quiesced.

gname

Master group for which you are adding a site to a group.

name

Name of the site priority group to which you are adding a member.

site

Global database name of the site that you are adding.

priority

Priority level of the site that you are adding. A higher number indicates a higher priority level.

nonmasterdef

Invocation site is not the master definition site.

missingrepgroup

Specified master group does not exist.

missingpriority

Specified site priority group does not exist.

duplicatepriority

Specified priority level already exists for another site in the group.

duplicatevalue

Specified site already exists in the site priority group.

notquiesced

Master group is not quiesced.

update

ADD_UPDATE_RESOLUTION

uniqueness

ADD_UNIQUE_RESOLUTION

delete

ADD_DELETE_RESOLUTION

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 user function, and provide the name of your method as the function_name parameter.

The standard methods supported in this release for update conflicts are:

• minimum

• maximum

• latest timestamp

• earliest timestamp

• additive, average

• priority group

• site priority

• overwrite

• discard

The standard methods supported in this release for uniqueness conflicts are: append site name, append sequence, and discard. There are no built-in (Oracle supplied) methods for delete conflicts.

parameter_column_name

Name of the columns used to resolve the conflict. The standard methods operate on a single column. For example, if you are using the latest timestamp method for a column group, then you should pass the name of the column containing the time stamp value as this parameter. If your are using a user function, then you can resolve the conflict using any number of columns.

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 DBMS_REPCAT.VARCHAR2 or DBMS_UTILITY.LNAME_ARRAY. Use DBMS_UTILITY.LNAME_ARRAY if any column name is greater than or equal to 30 bytes, which might occur when you specify the attributes of column objects.

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 '*' 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.

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 priority group or site priority update conflict resolution method, then you must supply the name of the priority group that you have created.

See Chapter 6, "Configuring Conflict Resolution" and Oracle Database Advanced Replication for more information. If you are using a different method, you can use the default value for this parameter, NULL. This parameter is applicable to update conflicts only.

function_name

If you selected the user function method, or if you are adding a delete conflict resolution routine, then you must supply the name of the conflict resolution routine that you have written. If you are using one of the standard methods, then you can use the default value for this parameter, NULL.

comment

This user comment is added to the DBA_REPRESOLUTION view.

nonmasterdef

Invocation site is not the master definition site.

missingobject

Specified object does not exist as a table in the specified schema using row-level replication.

missingschema

Specified schema does not exist.

missingcolumn

Column that you specified as part of the parameter_column_name parameter does not exist.

missinggroup

Specified column group does not exist.

missingprioritygroup

The priority group that you specified does not exist for the table.

invalidmethod

Resolution method that you specified is not recognized.

invalidparameter

Number of columns that you specified for the parameter_column_name parameter is invalid. (The standard routines take only one column name.)

missingfunction

User function that you specified does not exist.

missingconstraint

Constraint that you specified for a uniqueness conflict does not exist.

notquiesced

Replication group to which the specified table belongs is not quiesced.

duplicateresolution

Specified conflict resolution method is already registered.

duplicatesequence

The specified sequence number already exists for the specified object.

invalidprioritygroup

The specified priority group does not exist.

paramtype

Type is different from the type assigned to the priority group.

extension_id

The identifier for the current pending request to add master database without quiesce. You can find the extension_id by querying the DBA_REPSITES_NEW and DBA_REPEXTENSIONS data dictionary views.

percentage_for_catchup_mdef

The percentage of propagation resources that should be used for catching up propagation to the master definition site. Must be a multiple of 10 and must be between 0 and 100.

cycle_seconds_mdef

This parameter is meaningful when percentage_for_catchup_mdef is both meaningful and set to a value between 10 and 90, inclusive. In this case, propagation to the master definition site alternates between replication groups that are not being extended and replication groups that are being extended, with one push to each during each cycle. This parameter indicates the length of the cycle in seconds.

percentage_for_catchup_new

The percentage of propagation resources that should be used for catching up propagation to new master sites. Must be a multiple of 10 and must be between 0 and 100.

cycle_seconds_new

This parameter is meaningful when percentage_for_catchup_new is both meaningful and set to a value between 10 and 90, inclusive. In this case, propagation to a new master alternates between replication groups that are not being extended and replication groups that are being extended, with one push to each during each cycle. This parameter indicates the length of the cycle in seconds.

typefailure

The parameter value specified for one of the parameters is not appropriate.

dbnotcompatible

Feature is incompatible with database version. All databases must be at 9.0.1 or higher compatibility level.

gname

Name of the replication group to which to alter the propagation mode.

master

Name of the master site at which to alter the propagation mode.

dblink_list

A comma-delimited list of database links for which to alter the propagation method. If NULL, then all masters except the master site being altered are used by default.

dblink_table

A PL/SQL index-by table, indexed from position 1, of database links for which to alter propagation.

propagation_mode

Determines the manner in which changes from the specified master site are propagated to the sites identified by the list of database links. Appropriate values are synchronous and asynchronous.

comment

This comment is added to the DBA_REPPROP view.

nonmasterdef

Invocation site is not the master definition site.

notquiesced

Invocation site is not quiesced.

typefailure

Propagation mode specified was not recognized.

nonmaster

List of database links includes a site that is not a master site.

sname

Schema containing the object that you want to alter.

oname

Name of the object that you want to alter. The object cannot be a storage table for a nested table.

type

Type of the object that you are altering. The following types are supported:

FUNCTION               SYNONYM
INDEX                  TABLE
INDEXTYPE              TRIGGER
OPERATOR               TYPE
PACKAGE                TYPE BODY
PACKAGE BODY           VIEW
PROCEDURE

ddl_text

The DDL text that you want used to alter the object. Oracle does not parse this DDL before applying it. Therefore, you must ensure that your DDL text provides the appropriate schema and object name for the object being altered.

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.

comment

If not NULL, then this comment is added to the COMMENT field of the DBA_REPOBJECT view.

retry

If retry is TRUE, then ALTER_MASTER_REPOBJECT alters the object only at masters whose object status is not VALID.

safe_table_change

Specify TRUE if the change to a table is safe. Specify FALSE if the change to a table is unsafe.

You can make safe changes to a master table in a single master replication environment without quiescing the master group that contains the table. To make unsafe changes, you must quiesce the master group.

Only specify this parameter for tables in single master replication environments. This parameter is ignored in multimaster replication environments and when the object specified is not a table. In multimaster replication environments, you must quiesce the master group to run the ALTER_MASTER_REPOBJECT procedure on a table.

The following are safe changes:

• Changing storage and extent information

• Making existing columns larger. For example, changing a VARCHAR2(20) column to a VARCHAR2(50) column.

• Adding non primary key constraints

• Altering non primary key constraints

• Enabling and disabling non primary key constraints

The following are unsafe changes:

• Changing the primary key by adding or deleting columns in the key

• Adding or deleting columns

• Making existing columns smaller. For example, changing a VARCHAR2(50) column to a VARCHAR2(20) column.

• Disabling a primary key constraint

• Changing the data type of an existing column

• Dropping an existing column

If you are unsure whether a change is safe or unsafe, then quiesce the master group before you run the ALTER_MASTER_REPOBJECT procedure.

nonmasterdef

Invocation site is not the master definition site.

notquiesced

Associated replication group has not been suspended.

missingobject

Object identified by sname and oname does not exist.

typefailure

Specified type parameter is not supported.

ddlfailure

DDL at the master definition site did not succeed.

commfailure

At least one master site is not accessible.

gname

Name of the replication group for which to alter the propagation method.

propagation_mode

Manner in which changes from the current materialized view site are propagated to its associated master site or master materialized view site. Appropriate values are synchronous and asynchronous.

comment

This comment is added to the DBA_REPPROP view.

gowner

Owner of the materialized view group.

missingrepgroup

Specified replication group does not exist.

typefailure

Propagation mode was specified incorrectly.

nonmview

Current site is not a materialized view site for the specified replication group.

commfailure

Cannot contact master site or master materialized view site.

failaltermviewrop

Materialized view group propagation can be altered only when there are no other materialized view groups with the same master site or master materialized view site sharing the materialized view site.

gname

Master group with which the priority group is associated.

pgroup

Name of the priority group containing the priority that you want to alter.

old_priority

Current priority level of the priority group member.

new_priority

New priority level that you want assigned to the priority group member.

nonmasterdef

Invocation site is not the master definition site.

duplicatepriority

New priority level already exists in the priority group.

missingrepgroup

Specified master group does not exist.

missingvalue

Value was not registered by a call to DBMS_REPCAT.ADD_PRIORITY_datatype.

missingprioritygroup

Specified priority group does not exist.

notquiesced

Specified master group is not quiesced.

gname

Master group with which the priority group is associated.

pgroup

Name of the priority group containing the value that you want to alter.

old_value

Current value of the priority group member.

new_value

New value that you want assigned to the priority group member.

nonmasterdef

Invocation site is not the master definition site.

duplicatevalue

New value already exists in the priority group.

missingrepgroup

Specified master group does not exist.

missingprioritygroup

Specified priority group does not exist.

missingvalue

Old value does not exist.

paramtype

New value has the incorrect data type for the priority group.

typefailure

Specified value has the incorrect data type for the priority group.

notquiesced

Specified master group is not quiesced.

gname

Master group with which the site priority group is associated.

name

Name of the site priority group whose member you are altering.

old_priority

Current priority level of the site whose priority level you want to change.

new_priority

New priority level for the site. A higher number indicates a higher priority level.

nonmasterdef

Invocation site is not the master definition site.

missingrepgroup

Specified master group does not exist.

missingpriority

Old priority level is not associated with any group members.

duplicatepriority

New priority level already exists for another site in the group.

missingvalue

Old value does not already exist.

paramtype

New value has the incorrect data type for the priority group.

notquiesced

Master group is not quiesced.

gname

Master group with which the site priority group is associated.

name

Name of the site priority group whose member you are altering.

old_site

Current global database name of the site to disassociate from the priority level.

new_site

New global database name that you want to associate with the current priority level.

nonmasterdef

Invocation site is not the master definition site.

missingrepgroup

Specified master group does not exist.

missingpriority

Specified site priority group does not exist.

missingvalue

Old site is not a group member.

notquiesced

Master group is not quiesced.

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.

missingschema

Specified schema does not exist.

missingobject

Specified table does not exist.

statnotreg

Specified table is not currently registered to collect statistics.

sname

Name of the schema in which the object is located.

oname

Name of the replicated table with which the column group is associated.

column_group

Name of the column group.

comment

Text of the updated comment that you want included in the GROUP_COMMENT field of the DBA_REPCOLUMN_GROUP view.

nonmasterdef

Invocation site is not the master definition site.

missinggroup

Specified column group does not exist.

missingobj

Object is missing.

gowner

Owner of the materialized view group.

gname

Name of the materialized view group.

comment

Updated comment to include in the SCHEMA_COMMENT field of the DBA_REPGROUP view.

missingrepgroup

The materialized view group does not exist.

nonmview

The connected site is not a materialized view site.

gname

Name of the master group.

pgroup

Name of the priority group.

comment

Text of the updated comment that you want included in the PRIORITY_COMMENT field of the DBA_REPPRIORITY_GROUP view.

nonmasterdef

Invocation site is not the master definition site.

missingrepgroup

Specified master group does not exist.

missingprioritygroup

Specified priority group does not exist.

gname

Name of the replication group that you want to comment on.

comment

Updated comment to include in the SCHEMA_COMMENT field of the DBA_REPGROUP view.

nonmasterdef

Invocation site is not the master definition site.

commfailure

At least one master site is not accessible.

sname

Name of the schema in which the object is located.

oname

Name of the object that you want to comment on. The object cannot be a storage table for a nested table.

type

Type of the object. The following types are supported:

FUNCTION              SYNONYM
INDEX                 TABLE
INDEXTYPE             TRIGGER
OPERATOR              TYPE
PACKAGE               TYPE BODY
PACKAGE BODY          VIEW
PROCEDURE

comment

Text of the updated comment that you want to include in the OBJECT_COMMENT field of the DBA_REPOBJECT view.

nonmasterdef

Invocation site is not the master definition site.

missingobject

Specified object does not exist.

typefailure

Specified type parameter is not supported.

commfailure

At least one master site is not accessible.

gname

Name of the replication group. This avoids confusion if a database is a master site in more than one replication environment.

master

The fully qualified database name of the master site on which you want to comment. If you are executing the procedure on a master site, then this parameter is required. To update comments at a materialized view site, omit this parameter. This parameter is optional.

comment

Text of the updated comment that you want to include in the comment field of the appropriate dictionary view. If the site is a master site, then this procedure updates the MASTER_COMMENT field of the DBA_REPSITES view. If the site is a materialized view site, then this procedure updates the SCHEMA_COMMENT field of the DBA_REPGROUP view.

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.

missingrepgroup

Replication group does not exist.

commfailure

One or more master sites are not accessible.

corrupt

There is an inconsistency in the replication catalog views.

gname

Name of the master group.

name

Name of the site priority group.

comment

Text of the updated comment that you want included in the PRIORITY_COMMENT field of the DBA_REPPRIORITY_GROUP view.

nonmasterdef

Invocation site is not the master definition site.

missingrepgroup

Specified master group does not exist.

missingprioritygroup

Specified priority group does not exist.

update

COMMENT_ON_UPDATE_RESOLUTION

uniqueness

COMMENT_ON_UNIQUE_RESOLUTION

delete

COMMENT_ON_DELETE_RESOLUTION

sname

Name of the schema.

oname

Name of the replicated table with which the conflict resolution routine is associated.

column_group

Name of the column group with which the update conflict resolution routine is associated.

constraint_name

Name of the unique constraint with which the uniqueness conflict resolution routine is associated.

sequence_no

Sequence number of the conflict resolution procedure.

comment

The text of the updated comment that you want included in the RESOLUTION_COMMENT field of the DBA_REPRESOLUTION view.

nonmasterdef

Invocation site is not the master definition site.

missingobject

Specified object does not exist.

missingresolution

Specified conflict resolution routine is not registered.

sname

Schema in which the table is located.

oname

Name of the replicated table. The table can be the storage table of a nested table.

column_list

A comma-delimited list of the columns in the table. There must be no spaces between entries.

column_table

Instead of a list, you can use a PL/SQL index-by table of type DBMS_REPCAT.VARCHAR2 or DBMS_UTILITY.LNAME_ARRAY to contain the column names. The first column name should be at position 1, the second at position 2, and so on.

Use DBMS_UTILITY.LNAME_ARRAY if any column name is greater than or equal to 30 bytes, which might occur when you specify the attributes of column objects.

operation

Possible values are: update, delete, or the asterisk wildcard '*', which means update and delete.

compare

If compare is TRUE, the old values of the specified columns are compared when sent. If compare is FALSE, the old values of the specified columns are not compared when sent. Unspecified columns and unspecified operations are not affected. The specified change takes effect at the master definition site as soon as min_communication is TRUE for the table. The change takes effect at a master site or at a materialized view site the next time replication support is generated at that site with min_communication TRUE.

nonmasterdef

Invocation site is not the master definition site.

missingobject

Specified object does not exist as a table in the specified schema waiting for row-level replication information.

missingcolumn

At least one column is not in the table.

notquiesced

Master group has not been quiesced.

typefailure

An illegal operation is specified.

keysendcomp

A specified column is a key column in a table.

dbnotcompatible

Feature is incompatible with database version. Typically, this exception arises when you are trying to compare the attributes of column objects. In this case, all databases must be at 9.0.1 or higher compatibility level.

gname

Name of the master group that you want to create.

group_comment

This comment is added to the DBA_REPGROUP view.

master_comment

This comment is added to the DBA_REPSITES view.

qualifier

Connection qualifier for master group. Be sure to use the @ sign. See Oracle Database Advanced Replication and Oracle Database Administrator's Guide for more information about connection qualifiers.

duplicaterepgroup

Master group already exists.

norepopt

Advanced replication option is not installed.

missingrepgroup

Master group name was not specified.

qualifiertoolong

Connection qualifier is too long.

sname

Name of the schema in which the object that you want to replicate is located.

oname

Name of the object you are replicating. If ddl_text is NULL, then this object must already exist in the specified schema. To ensure uniqueness, table names should be a maximum of 27 bytes long, and package names should be no more than 24 bytes. The object cannot be a storage table for a nested table.

type

Type of the object that you are replicating. The following types are supported:

FUNCTION                SYNONYM
INDEX                   TABLE
INDEXTYPE               TRIGGER
OPERATOR                TYPE
PACKAGE                 TYPE BODY
PACKAGE BODY            VIEW
PROCEDURE

use_existing_object

Indicate TRUE if you want to reuse any objects of the same type and shape at the current master sites. See Table 18-56 for more information.

Note: This parameter must be set to TRUE for clustered tables.

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 (sname parameter), 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.

Note: Do not use the ddl_text parameter to add user-defined types or object tables. Instead, create the object first and then add the object.

comment

This comment is added to the OBJECT_COMMENT field of the DBA_REPOBJECT view.

retry

Indicate TRUE if you want Oracle to reattempt to create an object that it was previously unable to create. Use this if the error was transient or has since been rectified, or if you previously had insufficient resources. If this is TRUE, then Oracle creates the object only at master sites whose object status is not VALID.

copy_rows

Indicate TRUE if you want the initial contents of a newly replicated object to match the contents of the object at the master definition site. See Table 18-56 for more information.

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.

nonmasterdef

Invocation site is not the master definition site.

notquiesced

Master group is not quiesced.

duplicateobject

Specified object already exists in the master group and retry is FALSE, or if a name conflict occurs.

missingobject

Object identified by sname and oname does not exist and appropriate DDL has not been provided.

typefailure

Objects of the specified type cannot be replicated.

ddlfailure

DDL at the master definition site did not succeed.

commfailure

At least one master site is not accessible.

yes

TRUE

TRUE

duplicatedobject message if objects do not match. For tables, use data from master definition site.

yes

FALSE

TRUE

duplicatedobject message if objects do not match. For tables, DBA must ensure contents are identical.

yes

TRUE/FALSE

FALSE

duplicatedobject message.

no

TRUE

TRUE/FALSE

Object is created. Tables populated using data from master definition site.

no

FALSE

TRUE/FALSE

Object is created. DBA must populate tables and ensure consistency of tables at all sites.

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 Oracle Database Advanced Replication and Oracle Database Administrator's Guide for information about using connection qualifiers.

comment

This comment is added to the DBA_REPGROUP view.

propagation_mode

Method of propagation for all updatable materialized views in the replication group. Acceptable values are synchronous and asynchronous.

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.

duplicaterepgroup

Replication group already exists at the invocation site.

nonmaster

Specified database is not a master site or master materialized view site.

commfailure

Specified database is not accessible.

norepopt

Advanced replication option is not installed.

typefailure

Propagation mode was specified incorrectly.

missingrepgroup

Replication group does not exist at master site.

invalidqualifier

Connection qualifier specified for the master site or master materialized view site is not valid for the replication group.

alreadymastered

At the local site, there is another materialized view group with the same group name, but different master site or master materialized view site.

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:

FUNCTION               SNAPSHOT
INDEX                  SYNONYM
INDEXTYPE              TRIGGER
OPERATOR               TYPE
PACKAGE                TYPE BODY
PACKAGE BODY           VIEW
PROCEDURE

Use SNAPSHOT type of the object is a materialized view.

ddl_text

For objects of type MATERIALIZED VIEW, the DDL needed to create the object. For other types, use the default:

'' (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 missingobject error.

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 MATERIALIZED VIEW, then the materialized view site connects to the master site or master materialized view site and pulls down the DDL text to create the object. If the object type is TYPE or TYPE BODY, then the object identifier (OID) for the object at the materialized view site is the same as the OID at the master site or master materialized view site.

comment

This comment is added to the OBJECT_COMMENT field of the DBA_REPOBJECT view.

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

This parameter is obsolete. Use the default value (TRUE).

generate_80_compatible

Set to TRUE if the materialized view's master site is running a version of Oracle server prior to Oracle8i Database release 8.1.5. Set to FALSE if the materialized view's master site or master materialized view site is running Oracle8i Database release 8.1.5 or later.

gowner

Owner of the materialized view group.

nonmview

Invocation site is not a materialized view site.

nonmaster

Master is no longer a master site or master materialized view site.

missingobject

Specified object does not exist in the master's replication group.

duplicateobject

Specified object already exists with a different shape.

typefailure

Type is not an allowable type.

ddlfailure

DDL did not succeed.

commfailure

Master site or master materialized view site is not accessible.

missingschema

Schema does not exist as a database schema.

badmviewddl

DDL was executed but materialized view does not exist.

onlyonemview

Only one materialized view for master table or master materialized view can be created.

badmviewname

Materialized view differs from master table or master materialized view.

missingrepgroup

Replication group at the master does not exist.

sname

Schema in which the replicated table is located.

oname

Name of the replicated table for which you are creating a column group.

column_group

Name of the column group that you want to create.

comment

This user text is displayed in the DBA_REPCOLUMN_GROUP view.

nonmasterdef

Invocation site is not the master definition site.

missingobject

Specified table does not exist.

duplicategroup

Specified column group already exists for the table.

notquiesced

Replication group to which the specified table belongs is not quiesced.

gname

Master group for which you are creating a priority group.

pgroup

Name of the priority group that you are creating.

datatype

Data type of the priority group members. The data types supported are: CHAR, VARCHAR2, NUMBER, DATE, RAW, NCHAR, and NVARCHAR2.

fixed_length

You must provide a column length for the CHAR data type. All other types can use the default, NULL.

comment

This user comment is added to the DBA_REPPRIORITY view.

nonmasterdef

Invocation site is not the master definition site.

missingrepgroup

Specified master group does not exist.

duplicatepriority group

Specified priority group already exists in the master group.

typefailure

Specified data type is not supported.

notquiesced

Master group is not quiesced.

gname

The master group for which you are creating a site priority group.

name

Name of the site priority group that you are creating.

comment

This user comment is added to the DBA_REPPRIORITY view.

nonmasterdef

Invocation site is not the master definition site.

missingrepgroup

Specified master group does not exist.

duplicate prioritygroup

Specified site priority group already exists in the master group.

notquiesced

Master group is not quiesced.

gname

Name of the master group.

all_sites

If this is TRUE, then use a job to execute the local administrative procedures at each master site.

nonmaster

Invocation site is not a master site.

commfailure

At least one master site is not accessible and all_sites is TRUE.

sname

Schema in which the replicated table is located.

oname

Name of the replicated table whose column group you are dropping.

column_group

Name of the column group that you want to drop.

nonmasterdef

Invocation site is not the master definition site.

referenced

Specified column group is being used in conflict detection and resolution.

missingobject

Specified table does not exist.

missinggroup

Specified column group does not exist.

notquiesced

Master group to which the table belongs is not quiesced.

sname

Schema in which the replicated table is located.

oname

Name of the replicated table in which the column group is located. The table can be the storage table of a nested table.

column_group

Name of the column group from which you are removing members.

list_of_column_names

Names of the columns that you are removing from the designated column group. This can either be a comma-delimited list or a PL/SQL index-by table of column names. The PL/SQL index-by table must be of type DBMS_REPCAT.VARCHAR2.

You can specify column objects, but you cannot specify attributes of column objects.

If the table is an object, then you can specify SYS_NC_OID$ to add the object identifier column to the column group. This column tracks the object identifier of each row object.

If the table is a storage table of a nested table, then you can specify NESTED_TABLE_ID to add the column that tracks the identifier for each row of the nested table.

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.

gname

Name of the master group that you want to drop from the current master site.

drop_contents

By default, when you drop the replication group at a master site, all of the objects remain in the database. They simply are no longer replicated. That is, the replicated objects in the replication group no longer send changes to, or receive changes from, other master sites. If you set this to TRUE, then any replicated objects in the master group are dropped from their associated schemas.

all_sites

If this is TRUE and if the invocation site is the master definition site, then the procedure synchronously multicasts the request to all masters. In this case, execution is immediate at the master definition site and might be deferred at all other master sites.

nonmaster

Invocation site is not a master site.

nonmasterdef

Invocation site is not the master definition site and all_sites is TRUE.

commfailure

At least one master site is not accessible and all_sites is TRUE.

fullqueue

Deferred remote procedure call (RPC) queue has entries for the master group.

masternotremoved

Master does not recognize the master definition site and all_sites is TRUE.

sname

Name of the schema in which the object is located.

oname

Name of the object that you want to remove from the master group. The object cannot be a storage table for a nested table.

type

Type of object that you want to drop. The following types are supported:

FUNCTION               SYNONYM
INDEX                  TABLE
INDEXTYPE              TRIGGER
OPERATOR               TYPE
PACKAGE                TYPE BODY
PACKAGE BODY           VIEW
PROCEDURE

drop_objects

By default, the object remains in the schema, but is dropped from the master group. That is, any changes to the object are no longer replicated to other master and materialized view sites. To completely remove the object from the replication environment, set this parameter to TRUE. If the parameter is set to TRUE, the object is dropped from the database at each master site.

nonmasterdef

Invocation site is not the master definition site.

missingobject

Specified object does not exist.

typefailure

Specified type parameter is not supported.

commfailure

At least one master site is not accessible.

gname

Name of the replication group that you want to drop from the current materialized view site. All objects generated to support replication, such as triggers and packages, are dropped.

drop_contents

By default, when you drop the replication group at a materialized view site, all of the objects remain in their associated schemas. They simply are no longer replicated. If you set this to TRUE, then any replicated objects in the replication group are dropped from their schemas.

gowner

Owner of the materialized view group.

nonmview

Invocation site is not a materialized view site.

missingrepgroup

Specified replication group does not exist.

sname

Name of the schema in which the object is located.

oname

Name of the object that you want to drop from the replication group.

type

Type of the object that you want to drop. The following types are supported:

FUNCTION                SNAPSHOT
INDEX                   SYNONYM
INDEXTYPE               TRIGGER
OPERATOR                TYPE
PACKAGE                 TYPE BODY
PACKAGE BODY            VIEW
PROCEDURE

Use SNAPSHOT to drop a materialized view.

drop_objects

By default, the object remains in its associated schema, but is dropped from its associated replication group. To completely remove the object from its schema at the current materialized view site, set this parameter to TRUE. If the parameter is set to TRUE, the object is dropped from the database at the materialized view site.

nonmview

Invocation site is not a materialized view site.

missingobject

Specified object does not exist.

typefailure

Specified type parameter is not supported.

gname

Master group with which the priority group is associated.

pgroup

Name of the priority group containing the member that you want to drop.

priority_num

Priority level of the priority group member that you want to remove from the group.

nonmasterdef

Invocation site is not the master definition site.

missingrepgroup

Specified master group does not exist.

missingprioritygroup

Specified priority group does not exist.

notquiesced

Master group is not quiesced.

gname

Master group with which the priority group is associated.

pgroup

Name of the priority group that you want to drop.

nonmasterdef

Invocation site is not the master definition site.

missingrepgroup

Specified master group does not exist.

referenced

Specified priority group is being used in conflict resolution.

notquiesced

Specified master group is not quiesced.

gname

Master group with which the priority group is associated.

pgroup

Name of the priority group containing the member that you want to drop.

value

Value of the priority group member that you want to remove from the group.

nonmasterdef

Invocation site is not the master definition site.

missingrepgroup

Specified master group does not exist.

missingprioritygroup

Specified priority group does not exist.

paramtype, typefailure

Value has the incorrect data type for the priority group.

notquiesced

Specified master group is not quiesced.

gname

Master group with which the site priority group is associated.

name

Name of the site priority group that you want to drop.

nonmasterdef

Invocation site is not the master definition site.

missingrepgroup

Specified master group does not exist.

referenced

Specified site priority group is being used in conflict resolution.

notquiesced

Specified master group is not quiesced.

gname

Master group with which the site priority group is associated.

name

Name of the site priority group whose member you are dropping.

site

Global database name of the site you are removing from the group.

nonmasterdef

Invocation site is not the master definition site.

missingrepgroup

Specified master group does not exist.

missingpriority

Specified site priority group does not exist.

notquiesced

Specified master group is not quiesced.

update

DROP_UPDATE_RESOLUTION

uniqueness

DROP_UNIQUE_RESOLUTION

delete

DROP_DELETE_RESOLUTION

sname

Schema in which the table is located.

oname

Name of the table for which you want to drop a conflict resolution routine.

column_group

Name of the column group for which you want to drop an update conflict resolution routine.

constraint_name

Name of the unique constraint for which you want to drop a unique conflict resolution routine.

sequence_no

Sequence number assigned to the conflict resolution method that you want to drop. This number uniquely identifies the routine.

nonmasterdef

Invocation site is not the master definition site.

missingobject

Specified object does not exist as a table in the specified schema, or a conflict resolution routine with the specified sequence number is not registered.

notquiesced

Master group is not quiesced.

gname

Name of the master group.

master_list

A comma-delimited list of master sites at which you want to execute the supplied DDL. Do not put any spaces between site names. The default value, NULL, indicates that the DDL should be executed at all sites, including the master definition site.

master_table

A table that lists the master sites where you want to execute the supplied DDL. The first master should be at position 1, the second at position 2, and so on.

ddl_text

The DDL that you want to execute at each of the specified master sites. 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.

nonmasterdef

Invocation site is not the master definition site.

nonmaster

At least one site is not a master site.

ddlfailure

DDL at the master definition site did not succeed.

commfailure

At least one master site is not accessible.

sname

Schema in which the object is located.

oname

The name of the object for which you are generating support.

type

Type of the object. The types supported are MATERIALIZED VIEW, PACKAGE, and PACKAGE BODY.

gen_objs_owner

For objects of type PACKAGE or PACKAGE BODY, the schema in which the generated object should be created. If NULL, the objects are created in SNAME.

min_communication

If TRUE, then the update trigger sends the new value of a column only if the update statement modifies the column. The update trigger sends the old value of the column only if it is a key column or a column in a modified column group.

generate_80_compatible

Set to TRUE if the materialized view's master site is running a version of Oracle server prior to Oracle8i Database release 8.1.5. Set to FALSE if the materialized view's master site or master materialized view site is running Oracle8i Database release 8.1.5 or later.

nonmview

Invocation site is not a materialized view site.

missingobject

Specified object does not exist as a materialized view in the replicated schema waiting for row/column-level replication information or as a package (body) waiting for wrapper generation.

typefailure

Specified type parameter is not supported.

missingschema

Specified owner of generated objects does not exist.

missingremoteobject

Object at master site or master materialized view site has not yet generated replication support.

commfailure

Master site or master materialized view site is not accessible.

sname

Schema in which the object is located.

oname

Name of the object for which you are generating replication support.

type

Type of the object. The types supported are: TABLE, PACKAGE, and PACKAGE BODY.

package_prefix

For objects of type PACKAGE or PACKAGE BODY this value is prepended to the generated wrapper package name. The default is DEFER_.

procedure_prefix

For objects of type PACKAGE or PACKAGE BODY, this value is prepended to the generated wrapper procedure names. By default, no prefix is assigned.

distributed

This must be set to TRUE.

gen_objs_owner

For objects of type PACKAGE or PACKAGE BODY, the schema in which the generated object should be created. If NULL, the objects are created in sname.

min_communication

This parameter is obsolete. Use the default value (TRUE).

generate_80_compatible

Set to TRUE if any master site is running a version of Oracle server prior to Oracle8i Database release 8.1.5. Set to FALSE if all master sites are running Oracle8i Database release 8.1.5 or later.

nonmasterdef

Invocation site is not the master definition site.

missingobject

Specified object does not exist as a table in the specified schema waiting for row-level replication information or as a package (body) waiting for wrapper generation.

typefailure

Specified type parameter is not supported.

notquiesced

Replication group has not been quiesced.

commfailure

At least one master site is not accessible.

missingschema

Schema does not exist.

duplicateobject

Object already exists.

sname

Schema in which the replicated table is located.

oname

Name of the replicated table for which you are creating a new column group. The table can be the storage table of a nested table.

column_group

Name that you want assigned to the column group that you are creating.

list_of_column_names

Names of the columns that you are grouping. This can either be a comma-delimited list or a PL/SQL index-by table of column names. The PL/SQL index-by table must be of type DBMS_REPCAT.VARCHAR2. Use the single value '*' to create a column group that contains all of the columns in your table.

You can specify column objects, but you cannot specify attributes of column objects.

If the table is an object table, then you can specify SYS_NC_OID$ to add the object identifier column to the column group. This column tracks the object identifier of each row object.

If the table is the storage table of a nested table, then you can specify NESTED_TABLE_ID to add the column that tracks the identifier for each row of the nested table.

nonmasterdef

Invocation site is not the master definition site.

duplicategroup

Specified column group already exists for the table.

missingobject

Specified table does not exist.

missingcolumn

Specified column does not exist in the designated table.

duplicatecolumn

Specified column is already a member of another column group.

notquiesced

Master group is not quiesced.

extension_id

The identifier for the current pending request to add master databases to a master group without quiesce. You can find the extension_id by querying the DBA_REPSITES_NEW and DBA_REPEXTENSIONS data dictionary views.

typefailure

The parameter value specified for one of the parameters is not appropriate.

dbnotcompatible

Feature is incompatible with database version. All databases must be at 9.0.1 or higher compatibility level.

id

Identification number of the request, as it appears in the DBA_REPCATLOG view.

source

Master site from which the request originated.

gname

Name of the master group for which the request was made.

nonmaster

gname is not NULL, and the invocation site is not a master site.

sname

Name of the schema in which the replicated table is located.

oname

Name of the table whose conflict resolution statistics you want to purge.

start_date/end_date

Range of dates for which you want to purge statistics. If start_date is NULL, then purge all statistics up to the end_date. If end_date is NULL, then purge all statistics after the start_date.

missingschema

Specified schema does not exist.

missingobject

Specified table does not exist.

statnotreg

Table not registered to collect statistics.

gname

Name of the replication group.

drop_missing_contents

If an object was dropped from the replication group at the master site or master materialized view site, then it is not automatically dropped from the schema at the materialized view site. It is simply no longer replicated. That is, changes to this object are no longer sent to its associated master site or master materialized view site. Materialized views can continue to be refreshed from their associated master tables or master materialized views. However, any changes to an updatable materialized view are lost. When an object is dropped from the replication group, you can choose to have it dropped from the schema entirely by setting this parameter to TRUE.

refresh_mviews

Set to TRUE to refresh the contents of the materialized views in the replication group.

refresh_other_objects

Set this to TRUE to refresh the contents of the non materialized view objects in the replication group. Non materialized view objects can include the following:

• Tables

• Views

• Indexes

• PL/SQL packages and package bodies

• PL/SQL procedures and functions

• Triggers

• Synonyms

gowner

Owner of the materialized view group.

nonmview

Invocation site is not a materialized view site.

nonmaster

Master is no longer a master site or master materialized view site.

commfailure

Master site or master materialized view site is not accessible.

missingrepgroup

Replication group name not specified.

gname

Name of the materialized view group to be registered.

mviewsite

Global name of the materialized view site.

comment

Comment for the materialized view site or update for an existing comment.

rep_type

Version of the materialized view group. Valid constants that can be assigned include the following:

• dbms_repcat.reg_unknown (the default)

• dbms_repcat.reg_v7_group

• dbms_repcat.reg_v8_group

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.

failregmviewrepgroup

Registration of materialized view group failed.

missingrepgroup

Replication group name not specified.

nullsitename

A materialized view site was not specified.

nonmaster

Procedure must be executed at the materialized view's master site or master materialized view site.

duplicaterepgroup

Replication group already exists.

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.

missingschema

Specified schema does not exist.

missingobject

Specified table does not exist.

gname

Name of the replication group whose master definition you want to relocate.

old_masterdef

Fully qualified database name of the current master definition site.

new_masterdef

Fully qualified database name of the existing master site that you want to make the new master definition site.

notify_masters

If this is TRUE, then the procedure synchronously multicasts the change to all masters (including old_masterdef only if include_old_masterdef is TRUE). If any master does not make the change, then roll back the changes at all masters.

If just the master definition site fails, then you should invoke RELOCATE_MASTERDEF with notify_masters set to TRUE and include_old_masterdef set to 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 set to FALSE.

include_old_masterdef

If notify_masters is TRUE and if include_old_masterdef is also TRUE, then the old master definition site is also notified of the change.

require_flavor_change

This parameter is for internal use only.

Note: Do not set this parameter unless directed to do so by Oracle Support Services.

nonmaster

new_masterdef is not a master site or the invocation site is not a master site.

nonmasterdef

old_masterdef is not the master definition site.

commfailure

At least one master site is not accessible and notify_masters is TRUE.

gname

Name of the replication group associated with the replication environment. This prevents confusion if a master database is involved in more than one replication environment.

master_list

A comma-delimited list of fully qualified master database names that you want to remove from the replication environment. There must be no spaces between names in the list.

master_table

In place of a list, you can specify the database names in a PL/SQL index-by table of type DBMS_UTILITY.DBLINK_ARRAY.

nonmasterdef

Invocation site is not the master definition site.

nonmaster

At least one of the specified databases is not a master site.

reconfigerror

One of the specified databases is the master definition site.

commfailure

At least one remaining master site is not accessible.

sname

Schema in which the replicated table is located.

oname

Name of the replicated table.

new_col_group_name

Name of the new column group. The columns currently in the shadow group are placed in a column group with the name you specify.

missmview

The specified schema does not exist.

nonmasterdef

Invocation site is not the master definition site.

missingobject

The specified object does not exist.

duplicategroup

The column group that was specified for creation already exists.

gname

Name of the master group. If you omit both parameters, then the procedure checks all master groups at your current site.

master

Set this to TRUE if you are checking a master site and FALSE if you are checking a materialized view site.

gowner

Owner of the master group.

nonmaster

master is TRUE and either the database is not a master site for the replication group or the database is not the expected database.

nonmview

master is FALSE and the database is not a materialized view site for the replication group.

missingobject

A valid replicated object in the replication group does not exist.

missingrepgroup

The specified replicated replication group does not exist.

missingschema

The specified replicated replication group does not exist.

gname

Name of the master group.

override

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

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

nonmasterdef

Invocation site is not the master definition site.

notquiesced

Master group is not quiescing or quiesced.

commfailure

At least one master site is not accessible.

notallgenerated

Generate replication support before resuming replication activity.

extension_id

The identifier for the current pending request to add master databases to a master group without quiesce. You can find the extension_id by querying the DBA_REPSITES_NEW and DBA_REPEXTENSIONS data dictionary views.

nonmasterdef

Invocation site is not the master definition site.

extstinapp

Extension status is inappropriate. The extension status should be EXPORTING when you run this procedure. To check the extension status, query the DBA_REPEXTENSIONS data dictionary view.

dbnotcompatible

Feature is incompatible with database version. All databases must be at 9.0.1 or higher compatibility level.

sname

Schema in which the table is located.

oname

Name of the replicated table. The table can be the storage table of a nested table.

column_list

A comma-delimited list of the columns in the table. There must be no spaces between entries.

column_table

Instead of a list, you can use a PL/SQL index-by table of type DBMS_REPCAT.VARCHAR2 or DBMS_UTILITY.LNAME_ARRAY to contain the column names. The first column name should be at position 1, the second at position 2, and so on.

Use DBMS_UTILITY.LNAME_ARRAY if any column name is greater than or equal to 30 bytes, which might occur when you specify the attributes of column objects.

operation

Possible values are: update, delete, or the asterisk wildcard '*', which means update and delete.

send

If TRUE, then the old values of the specified columns are sent. If FALSE, then the old values of the specified columns are not sent. Unspecified columns and unspecified operations are not affected.

The specified change takes effect at the master definition site as soon as min_communication is TRUE for the table. The change takes effect at a master site or at a materialized view site the next time replication support is generated at that site with min_communication TRUE.

nonmasterdef

Invocation site is not the master definition site.

missingobject

Specified object does not exist as a table in the specified schema waiting for row-level replication information.

missingcolumn

At least one column is not in the table.

notquiesced

Master group has not been quiesced.

typefailure

An illegal operation is specified.

keysendcomp

A specified column is a key column in a table.

dbnotcompatible

Feature is incompatible with database version. Typically, this exception arises when you are trying to send the attributes of column objects. In this case, all databases must be at 9.0.1 or higher compatibility level.

sname

Schema in which the table is located.

oname

Name of the table.

column_list

A comma-delimited list of the columns in the table that you want to use as a primary key. There must be no spaces between entries.

column_table

Instead of a list, you can use a PL/SQL index-by table of type DBMS_UTILITY.NAME_ARRAY or DBMS_UTILITY.LNAME_ARRAY to contain the column names. The first column name should be at position 1, the second at position 2, and so on.

Use DBMS_UTILITY.LNAME_ARRAY if any column name is greater than or equal to 30 bytes, which might occur when you specify the attributes of column objects.

nonmasterdef

Invocation site is not the master definition site.

missingobject

Specified object does not exist as a table in the specified schema waiting for row-level replication information.

missingcolumn

At least one column is not in the table.

notquiesced

Replication group is not quiescing or quiesced.

gname

Master group to which you are adding new master sites.

master_list

A comma-delimited list of new master sites that you want to add to the master group. List only the new master sites, not the existing master sites. Do not put any spaces between site names.

If master_list is NULL, all master sites for the given replication group are removed from the DBA_REPSITES_NEW data dictionary view. Specify NULL to indicate that the master group is not being extended.

master_table

A table that lists the new master sites that you want to add to the master group. In the table, list only the new master sites, not the existing master sites. The first master site should be at position 1, the second at position 2, and so on.

If the table is empty, then all master sites for the specified replication group are removed from the DBA_REPSITES_NEW data dictionary view. Use an empty table to indicate that the master group is not being extended.

duplicaterepgroup

A master site that you are attempting to add is already part of the master group.

nonmasterdef

Invocation site is not the master definition site.

propmodenotallowed

Synchronous propagation mode not allowed for this operation. Only asynchronous propagation mode is allowed.

extstinapp

Extension request with status not allowed. There must either be no extension_id for the master group or the extension_id status must be READY. You can view the status for each extension_id at a master site in the DBA_REPEXTENSIONS data dictionary view.

dbnotcompatible

Feature is incompatible with database version. All databases must be at 9.0.1 or higher compatibility level.

notsamecq

Master groups do not have the same connection qualifier.

gnames

List of replication groups to migrate to Streams. The replication groups listed must all contain exactly the same master sites. An error is raised if the replication groups have different masters.

file_location

Directory location of the migration script. The specified location should be a directory object that is accessible to PL/SQL. You can use the SQL statement CREATE DIRECTORY to create a directory object.

See Also: Oracle Database SQL Language Reference for more information about the CREATE DIRECTORY statement

filename

Name of the migration script.

gname

Name of the master group for which you want to suspend activity.

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.

gname

Name of the materialized view group for which you want to change the master site.

master

Fully qualified database name of the new master site to use for the materialized view group.

gowner

Owner of the materialized view group.

nonmview

Invocation site is not a materialized view site.

nonmaster

Specified database is not a master site.

commfailure

Specified database is not accessible.

missingrepgroup

Materialized view group does not exist.

qrytoolong

Materialized view definition query is greater 32 KB.

alreadymastered

At the local site, there is another materialized view group with the same group name mastered at the old master site.

extension_id

The identifier for the current pending request to add master databases to a master group without quiesce. You can find the extension_id by querying the DBA_REPSITES_NEW and DBA_REPEXTENSIONS data dictionary views.

drop_contents

Specify TRUE, the default, to drop the contents of objects in new replication groups being extended at the local site. Specify FALSE to retain the contents.

dbnotcompatible

Feature is incompatible with database version. All databases must be at 9.0.1 or higher compatibility level.

typefail

A parameter value that you specified is not appropriate.

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.

gname

Name of the master group to validate.

check_genflags

Check whether all the objects in the group are generated. This must be done at the master definition site only.

check_valid_objs

Check that the underlying objects for objects in the group valid. This must be done at the master definition site only. The master definition site goes to all other sites and checks that the underlying objects are valid. The validity of the objects is checked within the schema of the connected user.

check_links_sched

Check whether the links are scheduled for execution. This should be invoked at each master site.

check_links

Check whether the connected user (repadmin), as well as the propagator, have correct links for replication to work properly. Checks that the links exist in the database and are accessible. This should be invoked at each master site.

error_table

Returns the messages and numbers of all errors that are found.

error_msg_table

Returns the messages of all errors that are found.

error_num_table

Returns the numbers of all errors that are found.

missingdblink

Database link does not exist in the schema of the replication propagator or has not been scheduled. Ensure that the database link exists in the database, is accessible, and is scheduled for execution.

dblinkmismatch

Database link name at the local node does not match the global name of the database that the link accesses. Ensure that the GLOBAL_NAMES initialization parameter is set to TRUE and the link name matches the global name.

dblinkuidmismatch

User name of the replication administration user at the local node and the user name at the node corresponding to the database link are not the same. Advanced Replication expects the two users to be the same. Ensure that the user identification of the replication administration user at the local node and the user identification at the node corresponding to the database link are the same.

objectnotgenerated

Object has not been generated at other master sites or is still being generated. Ensure that the object is generated by calling GENERATE_REPLICATION_SUPPORT and DO_DEFERRED_REPCAT_ADMIN for the object at the master definition site.

gname

Name of the master group.

record_count

Procedure returns whenever the number of incomplete activities is at or below this threshold.

timeout

Maximum number of seconds to wait before the procedure returns.

true_count
(out parameter)

Returns the number of incomplete activities.

nonmaster

Invocation site is not a master site.