| Oracle8i Replication API Reference Release 8.1.5 A67793-01 |
|
All installations of Oracle advanced replication include the replication management application programming interface (API). A server's replication management API is a set of PL/SQL packages that encapsulates procedures and functions that administrators can use to configure Oracle's advanced replication features. Oracle Replication Manager also uses the procedures and functions of each site's replication management API to perform work. This chapter describes that packages that constitute Oracle replication API, including:
Oracle's replication management API includes the following packages:
To use Oracle's replication management API, you issue procedure or function calls using an ad-hoc query tool such as an Enterprise Manager SQL Worksheet, Server Manager's command prompt, or SQL*Plus. For example, the following call to the DBMS_REPCAT.CREATE_MASTER_REPOBJECT procedure creates a new replicated table SALES.EMP in the ACCT replication group.
DBMS_REPCAT.CREATE_MASTER_REPOBJECT( sname => 'sales', oname => 'emp', type => 'table', use_existing_object => TRUE, ddl_text => 'CREATE TABLE acct_rec.emp AS . . .', comment => 'created by . . .', retry => FALSE, copy_rows => TRUE, gname => 'acct');
To call a replication management API function, you must provide an environment to receive the return value of the function. For example, the following anonymous PL/SQL block calls the DBMS_DEFER_SYS.DISABLED function in an IF statement.
BEGIN IF DBMS_DEFER_SYS.DISABLED('inst2') THEN DBMS_OUTPUT.PUT_LINE('Propagation to INST2 is disabled.'); ELSE DBMS_OUTPUT.PUT_LINE('Propagation to INST2 is enabled.'); END IF; END;
For many procedures and functions in the replication management API, there are important prerequisites to consider. For example:
Oracle's Replication Manager uses the replication management API to perform most of its functions. Using Replication Manager is much more convenient than issuing replication management API calls individually because the utility:
An easy way to learn how to use Oracle's replication management API is to use Replication Manager scripting feature. When you start an administrative session with Replication Manager, turn scripting on. When you are finished, turn scripting off and then review the script file. The script file contains all replication management API calls that were made during the session. See the Replication Manager help documentation for more information about its scripting feature.
| Subprogram | Description |
|---|---|
CALL procedure |
Builds a deferred call to a remote procedure |
COMMIT_WORK procedure |
Performs a transaction commit after checking for well-formed deferred remote procedure calls |
datatype_ARG procedure |
Provides the data that is to be passed to a deferred remote procedure call |
TRANSACTION procedure |
Indicates the start of a new deferred transaction |
This procedure builds a deferred call to a remote procedure.
DBMS_DEFER.CALL ( schema_name IN VARCHAR2, package_name IN VARCHAR2, proc_name IN VARCHAR2, arg_count IN NATURAL, { nodes IN node_list_t | group_name IN VARCHAR2 :=''});
This procedure performs a transaction commit after checking for well-formed deferred remote procedure calls.
DBMS_DEFER.COMMIT_WORK ( commit_work_comment IN VARCHAR2);
| Parameter | Description |
|---|---|
commit_work_ comment |
Equivalent to SQL "COMMIT COMMENT" statement. |
| Exception | Description |
|---|---|
ORA-23304 (malformedcall) |
Transaction was not correctly formed or terminated. |
This procedure provides the data that is to be passed to a deferred remote procedure call. Depending upon the type of the data that you need to pass to a procedure, you must call one of the following procedures for each argument to the procedure.
DBMS_DEFER.NUMBER_ARG (arg IN NUMBER); DBMS_DEFER.DATE_ARG (arg IN DATE); DBMS_DEFER.VARCHAR2_ARG (arg IN VARCHAR2); DBMS_DEFER.CHAR_ARG (arg IN CHAR); DBMS_DEFER.ROWID_ARG (arg IN ROWID); DBMS_DEFER.RAW_ARG (arg IN RAW); DBMS_DEFER.BLOB_ARG (arg IN BLOB); DBMS_DEFER.CLOB_ARG (arg IN CLOB); DBMS_DEFER.NCLOB_ARG (arg IN NCLOB); DBMS_DEFER.NCHAR_ARG (arg IN NCHAR); DBMS_DEFER.NVARCHAR2_ARG (arg IN NVARCHAR2); DBMS_DEFER.ANY_CLOB_ARG (arg IN CLOB); DBMS_DEFER.ANY_VARCHAR2_ARG (arg IN VARCHAR2); DBMS_DEFER.ANY_CHAR_ARG (arg IN CHAR);
| Parameter | Description |
|---|---|
arg |
Value of the parameter that you want to pass to the remote procedure to which you previously deferred a call. |
| Exception | Description |
|---|---|
ORA-23323 |
Argument value is too long. |
This procedure indicates the start of a new deferred transaction. If you omit this call, then Oracle considers your first call to DBMS_DEFER.CALL to be the start of a new transaction.
DBMS_DEFER.TRANSACTION ( nodes IN node_list_t);
The TRANSACTION procedure is overloaded. The behavior of the version without an input parameter is similar to that of the version with an input parameter, except that the former uses the nodes in the DEFDEFAULTDEST view instead of using the nodes in the nodes parameter.
| Subprogram | Description |
|---|---|
GET_ARG_FORM function |
Determines the form of an argument in a deferred call. |
GET_ARG_TYPE function |
Determines the type of an argument in a deferred call. |
GET_CALL_ARGS procedure |
Returns the text version of the various arguments for the given call. |
GET_datatype_ARG function |
Determines the value of an argument in a deferred call. |
This function determines the form of an argument in a deferred call. This function will return the character set ID of a deferred call parameter.
For more about displaying deferred transactions, see "Displaying Deferred Transactions" in the Oracle8i Replication manual. For more information about displaying error transactions, see "Displaying Error Transactions" in the Oracle8i Replication manual.
DBMS_DEFER_QUERY.GET_ARG_FORM ( callno IN NUMBER, arg_no IN NUMBER, deferred_tran_id IN VARCHAR2) RETURN NUMBER;
| Exception | Description |
|---|---|
NO_DATA_FOUND |
Input parameters do not correspond to a parameter of a deferred call. |
| Return Value | Corresponding Datatype |
|---|---|
1 |
CHAR, VARCHAR2, CLOB |
2 |
NCHAR, NVARCHAR2, NCLOB |
This function determines the type of an argument in a deferred call. The type of the deferred RPC parameter will be returned.
For more about displaying deferred transactions, see "Displaying Deferred Transactions" in the Oracle8i Replication manual. For more information about displaying error transactions, see "Displaying Error Transactions" in the Oracle8i Replication manual.
DBMS_DEFER_QUERY.GET_ARG_TYPE ( callno IN NUMBER, arg_no IN NUMBER, deferred_tran_id IN VARCHAR2) RETURN NUMBER;
| Exception | Description |
|---|---|
NO_DATA_FOUND |
Input parameters do not correspond to a parameter of a deferred call. |
| Return Value | Corresponding Datatype |
|---|---|
1 |
VARCHAR2 |
2 |
NUMBER |
11 |
ROWID |
12 |
DATE |
23 |
RAW |
96 |
CHAR |
112 |
CLOB |
113 |
BLOB |
This procedure returns the text version of the various arguments for the given call. The text version is limited to the first 2000 bytes.
DBMS_DEFER_QUERY.GET_CALL_ARGS ( callno IN NUMBER, startarg IN NUMBER := 1, argcnt IN NUMBER, argsize IN NUMBER, tran_id IN VARCHAR2, date_fmt IN VARCHAR2, types OUT TYPE_ARY, forms OUT TYPE_ARY, vals OUT VAL_ARY);
| Exception | Description |
|---|---|
NO_DATA_FOUND |
Input parameters do not correspond to a parameter of a deferred call. |
This function determines the value of an argument in a deferred call.
For more about displaying deferred transactions, see "Displaying Deferred Transactions" in the Oracle8i Replication manual. For more information about displaying error transactions, see "Displaying Error Transactions" in the Oracle8i Replication manual.
Depending upon the type of the argument value that you want to retrieve, the syntax for the appropriate function is as follows. Each of these functions returns the value of the specified argument.
DBMS_DEFER_QUERY.GET_datatype_ARG ( callno IN NUMBER, arg_no IN NUMBER, deferred_tran_id IN VARCHAR2 DEFAULT NULL) RETURN datatype;
where datatype:
{ NUMBER | VARCHAR2 | CHAR | DATE | RAW | ROWID | BLOB | CLOB | NCLOB | NCHAR | NVARCHAR2 }
| Exception | Description |
|---|---|
NO_DATA_FOUND |
Input parameters do not correspond to a parameter of a deferred call. |
ORA-26564 |
Argument in this position is not of the specified type. |
| Subprogram | Description |
|---|---|
ADD_DEFAULT_DEST procedure |
Adds a destination database to the |
DELETE_DEFAULT_DEST procedure |
Removes a destination database from the |
DELETE_DEF_DESTINATION procedure |
Removes a destination database from the |
DELETE_ERROR |
Deletes a transaction from the |
DELETE_TRAN |
Deletes a transaction from the |
DISABLED |
Determines whether propagation of the deferred transaction queue from the current site to a given site is enabled. |
EXCLUDE_PUSH |
Acquires an exclusive lock that prevents deferred transaction |
EXECUTE_ERROR |
Re-executes a deferred transaction that did not initially complete successfully. |
EXECUTE_ERROR_AS_USER |
Re-executes a deferred transaction that did not initially complete successfully. |
PURGE |
Purges pushed transactions from the deferred transaction queue at your current master or snapshot site. |
PUSH function |
Forces a deferred remote procedure call queue at your current master or snapshot site to be pushed to another master site. |
REGISTER_PROPAGATOR procedure |
Registers the given user as the propagator for the local database. |
SCHEDULE_PURGE procedure |
Schedules a job to purge pushed transactions from the deferred transaction queue at your current master or snapshot site. |
SCHEDULE_PUSH procedure |
Schedules a job to push the deferred transaction queue to a remote master destination. |
SET_DISABLED procedure |
Disables or enables propagation of the deferred transaction queue from the current site to a given destination site. |
UNREGISTER_PROPAGATOR procedure |
Unregister a user as the propagator from the local database. |
UNSCHEDULE_PURGE procedure |
Stops automatic purges of pushed transactions from the deferred transaction queue at a snapshot or master site. |
UNSCHEDULE_PUSH procedure |
Stops automatic pushes of the deferred transaction queue from a snapshot or master site to another master site. |
This procedure adds a destination database to the DEFDEFAULTDEST view.
DBMS_DEFER_SYS.ADD_DEFAULT_DEST ( dblink IN VARCHAR2);
| Parameter | Description |
|---|---|
dblink |
The fully qualified database name of the node that you want to add to the |
| Exception | Description |
|---|---|
ORA-23352 |
The |
This procedure removes a destination database from the DEFDEFAULTDEST view.
DBMS_DEFER_SYS.DELETE_DEFAULT_DEST ( dblink IN VARCHAR2);
This procedure removes a destination database from the DEFSCHEDULE view.
DBMS_DEFER_SYS.DELETE_DEF_DESTINATION ( destination IN VARCHAR2, force IN BOOLEAN := FALSE);
To delete a transaction from the DEFERROR view.
DBMS_DEFER_SYS.DELETE_ERROR( deferred_tran_id IN VARCHAR2, destination IN VARCHAR2);
To delete a transaction from the DEFTRANDEST view. If there are no other DEFTRANDEST or DEFERROR entries for the transaction, then the transaction is deleted from the DEFTRAN and DEFCALL views as well.
DBMS_DEFER_SYS.DELETE_TRAN ( deferred_tran_id IN VARCHAR2, destination IN VARCHAR2);
To determine whether propagation of the deferred transaction queue from the current site to a given site is enabled. The DISABLED function returns TRUE if the deferred remote procedure call (RPC) queue is disabled for the given destination.
DBMS_DEFER_SYS.DISABLED ( destination IN VARCHAR2) RETURN BOOLEAN;
| Parameter | Description |
|---|---|
destination |
The fully qualified database name of the node whose propagation status you want to check. |
| Value | Description |
|---|---|
TRUE |
Propagation to this site from the current site is disabled. |
FALSE |
Propagation to this site from the current site is enabled. |
| Exception | Description |
|---|---|
NO_DATA_FOUND |
|
To acquire an exclusive lock that prevents deferred transaction PUSH (either serial or parallel). This function does a commit when acquiring the lock. The lock is acquired with RELEASE_ON_COMMIT => TRUE, so that pushing of the deferred transaction queue can resume after the next commit.
DBMS_DEFER_SYS.EXCLUDE_PUSH ( timeout IN INTEGER) RETURN INTEGER;
| Value | Description |
|---|---|
0 |
Success, lock acquired. |
1 |
Timeout, no lock acquired. |
2 |
Deadlock, no lock acquired. |
4 |
Already own lock. |
To reexecute a deferred transaction that did not initially complete successfully. This procedure raises an ORA-24275 error when illegal combinations of NULL and non-NULL parameters are used.
DBMS_DEFER_SYS.EXECUTE_ERROR ( deferred_tran_id IN VARCHAR2, destination IN VARCHAR2);
| Exception | Description |
|---|---|
badparam |
Parameter value missing or invalid (for example, if |
missinguser |
Invalid user. |
To reexecute a deferred transaction that did not initially complete successfully. Each transaction is executed in the security context of the connected user. This procedure raises an ORA-24275 error when illegal combinations of NULL and non-NULL parameters are used.
DBMS_DEFER_SYS.EXECUTE_ERROR_AS_USER ( deferred_tran_id IN VARCHAR2, destination IN VARCHAR2);
| Exception | Description |
|---|---|
badparam |
Parameter value missing or invalid (for example, if destination is |
missinguser |
Invalid user. |
To purge pushed transactions from the deferred transaction queue at your current master or snapshot site.
DBMS_DEFER_SYS.PURGE ( purge_method IN BINARY_INTEGER := purge_method_quick, rollback_segment IN VARCHAR2 := NULL, startup_seconds IN BINARY_INTEGER := 0, execution_seconds IN BINARY_INTEGER := seconds_infinity, delay_seconds IN BINARY_INTEGER := 0, transaction_count IN BINARY_INTEGER := transactions_infinity, write_trace IN BOOLEAN := NULL); RETURN BINARY_INTEGER;
| Exception | Description |
|---|---|
argoutofrange |
Parameter value is out of a valid range. |
executiondisabled |
Execution of purging is disabled. |
defererror |
Internal error. |
This function forces a deferred remote procedure call queue at your current master or snapshot site to be pushed (executed, propagated) to another master site using either serial or parallel propagation.
DBMS_DEFER_SYS.PUSH ( destination IN VARCHAR2, parallelism IN BINARY_INTEGER := 0, heap_size IN BINARY_INTEGER := 0) stop_on_error IN BOOLEAN := FALSE, write_trace IN BOOLEAN := FALSE, startup_seconds IN BINARY_INTEGER := 0, execution_seconds IN BINARY_INTEGER := seconds_infinity, delay_seconds IN BINARY_INTEGER := 0, transaction_count IN BINARY_INTEGER := transactions_infinity, delivery_order_limit IN NUMBER := delivery_order_infinity) RETURN BINARY_INTEGER;
This procedure registers the given user as the propagator for the local database. It also grants to the given user CREATE SESSION, CREATE PROCEDURE, CREATE DATABASE LINK, and EXECUTE ANY PROCEDURE privileges (so that the user can create wrappers).
DBMS_DEFER_SYS.REGISTER_PROPAGATOR ( username IN VARCHAR2);
| Parameter | Description |
|---|---|
username |
Name of the user. |
| Exception | Description |
|---|---|
missinguser |
Given user does not exist. |
alreadypropagator |
Given user is already the propagator. |
duplicatepropagator |
There is already a different propagator. |
This procedure schedules a job to purge pushed transactions from the deferred transaction queue at your current master or snapshot site. You should schedule one purge job.
DBMS_DEFER_SYS.SCHEDULE_PURGE ( interval IN VARCHAR2, next_date IN DATE, reset IN BOOLEAN := NULL, purge_method IN BINARY_INTEGER := NULL, rollback_segment IN VARCHAR2 := NULL, startup_seconds IN BINARY_INTEGER := NULL, execution_seconds IN BINARY_INTEGER := NULL, delay_seconds IN BINARY_INTEGER := NULL, transaction_count IN BINARY_INTEGER := NULL, write_trace IN BOOLEAN := NULL);
This procedure schedules a job to push the deferred transaction queue to a remote master destination. This procedure does a COMMIT.
DBMS_DEFER_SYS.SCHEDULE_PUSH ( destination IN VARCHAR2, interval IN VARCHAR2, next_date IN DATE, reset IN BOOLEAN := FALSE, parallelism IN BINARY_INTEGER := NULL, heap_size IN BINARY_INTEGER := NULL, stop_on_error IN BOOLEAN := NULL, write_trace IN BOOLEAN := NULL, startup_seconds IN BINARY_INTEGER := NULL, execution_seconds IN BINARY_INTEGER := NULL, delay_seconds IN BINARY_INTEGER := NULL, transaction_count IN BINARY_INTEGER := NULL);
To disable or enable propagation of the deferred transaction queue from the current site to a given destination site. If the disabled parameter is TRUE, then the procedure disables propagation to the given destination and future invocations of PUSH do not push the deferred remote procedure call (RPC) queue. SET_DISABLED eventually affects a session already pushing the queue to the given destination, but does not affect sessions appending to the queue with DBMS_DEFER.
If the disabled parameter is FALSE, then the procedure enables propagation to the given destination and, although this does not push the queue, it permits future invocations to PUSH to push the queue to the given destination. Whether the disabled parameter is TRUE or FALSE, a COMMIT is required for the setting to take effect in other sessions.
DBMS_DEFER_SYS.SET_DISABLED ( destination IN VARCHAR2, disabled IN BOOLEAN := TRUE);
| Exception | Description |
|---|---|
NO_DATA_FOUND |
No entry was found in the |
To unregister a user as the propagator from the local database. This procedure
DEFPROPAGATOR.
REGISTER_PROPAGATOR from the given user (including identical privileges granted independently).
DBMS_DEFER_SYS.UNREGISTER_PROPAGATOR ( username IN VARCHAR2 timeout IN INTEGER DEFAULT DBMS_LOCK.MAXWAIT);
| Parameter | Description |
|---|---|
username |
Name of the propagator user. |
timeout |
Timeout in seconds. If the propagator is in use, then the procedure waits until timeout. The default is |
| Parameter | Description |
|---|---|
missingpropagator |
Given user is not a propagator. |
propagator_inuse |
Propagator is in use, and thus cannot be unregistered. Try later. |
This procedure stops automatic purges of pushed transactions from the deferred transaction queue at a snapshot or master site.
DBMS_DEFER_SYS.UNSCHEDULE_PURGE;
None
This procedure stops automatic pushes of the deferred transaction queue from a snapshot or master site to another master site.
DBMS_DEFER_SYS.UNSCHEDULE_PUSH ( dblink IN VARCHAR2);
| Parameter | Description |
|---|---|
dblink |
Fully qualified pathname to master database site at which you want to unschedule periodic execution of deferred remote procedure calls. |
| Exception | Description |
|---|---|
NO_DATA_FOUND |
No entry was found in the |
| Subprogram | Description |
|---|---|
BEGIN_INSTANTIATION procedure |
Starts offline instantiation of a replicated master group. |
BEGIN_LOAD procedure |
Disables triggers while data is imported to new master site as part of offline instantiation. |
END_INSTANTIATION procedure |
Completes offline instantiation of a replicated master group. |
END_LOAD procedure |
Re-enables triggers after importing data to new master site as part of offline instantiation. |
RESUME_SUBSET_OF_ MASTERS procedure |
Resumes replication activity at all existing sites except the new site during offline instantiation of a replicated master group. |
This procedure starts offline instantiation of a replicated master group. You must call this procedure from the master definition site.
DBMS_OFFLINE_OG.BEGIN_INSTANTIATION ( gname IN VARCHAR2, new_site IN VARCHAR2 fname IN VARCHAR2);
This procedure disables triggers while data is imported to new master site as part of offline instantiation. You must call this procedure from the new master site.
DBMS_OFFLINE_OG.BEGIN_LOAD ( gname IN VARCHAR2, new_site IN VARCHAR2);
This procedure completes offline instantiation of a replicated master group. You must call this procedure from the master definition site.
DBMS_OFFLINE_OG.END_INSTANTIATION ( gname IN VARCHAR2, new_site IN VARCHAR2);
This procedure re-enables triggers after importing data to new master site as part of offline instantiation. You must call this procedure from the new master site.
DBMS_OFFLINE_OG.END_LOAD ( gname IN VARCHAR2, new_site IN VARCHAR2 fname IN VARCHAR2);
This procedure resumes replication activity at all existing sites except the new site during offline instantiation of a replicated master group. You must call this procedure from the master definition site.
DBMS_OFFLINE_OG.RESUME_SUBSET_OF_MASTERS ( gname IN VARCHAR2, new_site IN VARCHAR2 override IN BOOLEAN := FALSE);
| Subprogram | Description |
|---|---|
BEGIN_LOAD procedure |
Prepares a snapshot site for import of a new snapshot as part of offline instantiation. |
END_LOAD procedure |
Completes offline instantiation of a snapshot. |
This procedure prepares a snapshot site for import of a new snapshot as part of offline instantiation. You must call this procedure from the snapshot site for the new snapshot.
DBMS_OFFLINE_SNAPSHOT.BEGIN_LOAD ( gname IN VARCHAR2, sname IN VARCHAR2, master_site IN VARCHAR2, snapshot_oname IN VARCHAR2, storage_c IN VARCHAR2 := '', comment IN VARCHAR2 := '', min_communication IN BOOLEAN := TRUE);
This procedure completes offline instantiation of a snapshot. You must call this procedure from the snapshot site for the new snapshot.
DBMS_OFFLINE_SNAPSHOT.END_LOAD ( gname IN VARCHAR2, sname IN VARCHAR2, snapshot_oname IN VARCHAR2);
| Subprogram | Description |
|---|---|
DIFFERENCES procedure |
Determines the differences between two tables. |
RECTIFY procedure |
Resolves the differences between two tables. |
This procedure determines the differences between two tables.
DBMS_RECTIFIER_DIFF.DIFFERENCES ( sname1 IN VARCHAR2, oname1 IN VARCHAR2, reference_site IN VARCHAR2 := '', sname2 IN VARCHAR2, oname2 IN VARCHAR2, comparison_site IN VARCHAR2 := '', where_clause IN VARCHAR2 := '', { column_list IN VARCHAR2 := '', | array_columns IN dbms_utility.name_array, } missing_rows_sname IN VARCHAR2, missing_rows_oname1 IN VARCHAR2, missing_rows_oname2 IN VARCHAR2, missing_rows_site IN VARCHAR2 := '', max_missing IN INTEGER, commit_rows IN INTEGER := 500);
The error ORA-00001 (Unique constraint violated) is issued when there are any unique or primary key constraints on the MISSING_ROWS_DATA table.
This procedure resolves the differences between two tables.
DBMS_RECTIFIER_DIFF.RECTIFY ( sname1 IN VARCHAR2, oname1 IN VARCHAR2, reference_site IN VARCHAR2 := '', sname2 IN VARCHAR2, oname2 IN VARCHAR2, comparison_site IN VARCHAR2 := '', { column_list IN VARCHAR2 := '', | array_columns IN dbms_utility.name_array, } missing_rows_sname IN VARCHAR2, missing_rows_oname1 IN VARCHAR2, missing_rows_oname2 IN VARCHAR2, missing_rows_site IN VARCHAR2 := '', commit_rows IN INTEGER := 500);
| Subprogram | Description |
|---|---|
ADD procedure |
Adds snapshots to a refresh group. |
CHANGE procedure |
Changes the refresh interval for a snapshot group. |
DESTROY procedure |
Removes all of the snapshots from a refresh group and deletes the refresh group. |
MAKE procedure |
Specifies the members of a refresh group and the time interval used to determine when the members of this group should be refreshed. |
REFRESH procedure |
Manually refreshes a refresh group. |
SUBTRACT procedure |
Removes snapshots from a refresh group. |
This procedure adds snapshots to a refresh group.
For additional information, see "ADD OBJECTS TO REFRESH GROUP". Also see "Snapshot Concepts & Architecture" in the Oracle8i Replication manual.
DBMS_REFRESH.ADD ( name IN VARCHAR2, { list IN VARCHAR2, | tab IN DBMS_UTILITY.UNCL_ARRAY, } lax IN BOOLEAN := FALSE);
This procedure changes the refresh interval for a snapshot group.
For additional information, see "Snapshot Concepts & Architecture" in the Oracle8i Replication manual.
DBMS_REFRESH.CHANGE ( name IN VARCHAR2, next_date IN DATE := NULL, interval IN VARCHAR2 := NULL, implicit_destroy IN BOOLEAN := NULL, rollback_seg IN VARCHAR2 := NULL, push_deferred_rpc IN BOOLEAN := NULL, refresh_after_errors IN BOOLEAN := NULL, purge_option IN BINARY_INTEGER := NULL, parallelism IN BINARY_INTEGER := NULL, heap_size IN BINARY_INTEGER := NULL);
This procedure removes all of the snapshots from a refresh group and delete the refresh group.
For additional information, see "Snapshot Concepts & Architecture" in the Oracle8i Replication manual.
DBMS_REFRESH.DESTROY ( name IN VARCHAR2);
| Parameter | Description |
|---|---|
name |
Name of the refresh group that you want to destroy. |
This procedure specifies the members of a refresh group and the time interval used to determine when the members of this group should be refreshed.
For additional information, see "CREATE REFRESH GROUP". Also see "Snapshot Concepts & Architecture" in the Oracle8i Replication manual.
DBMS_REFRESH.MAKE ( name IN VARCHAR2 { list IN VARCHAR2, | tab IN DBMS_UTILITY.UNCL_ARRAY,} next_date IN DATE, interval IN VARCHAR2, implicit_destroy IN BOOLEAN := FALSE, lax IN BOOLEAN := FALSE, job IN BINARY INTEGER := 0, rollback_seg IN VARCHAR2 := NULL, push_deferred_rpc IN BOOLEAN := TRUE, refresh_after_errors IN BOOLEAN := FALSE) purge_option IN BINARY_INTEGER := NULL, parallelism IN BINARY_INTEGER := NULL, heap_size IN BINARY_INTEGER := NULL);
This procedure manually refreshes a refresh group.
For additional information, see "Snapshot Concepts & Architecture" in the Oracle8i Replication manual.
DBMS_REFRESH.REFRESH ( name IN VARCHAR2);
| Parameter | Description |
|---|---|
name |
Name of the refresh group that you want to refresh manually. |
This procedure removes snapshots from a refresh group.
For additional information, see "Snapshot Concepts & Architecture" in the Oracle8i Replication manual.
DBMS_REFRESH.SUBTRACT ( name IN VARCHAR2, { list IN VARCHAR2, | tab IN DBMS_UTILITY.UNCL_ARRAY, } lax IN BOOLEAN := FALSE);
| Subprogram | Description |
|---|---|
ADD_GROUPED_COLUMN procedure |
Adds members to an existing column group. |
ADD_MASTER_DATABASE procedure |
Adds another master site to your replicated environment. |
ADD_PRIORITY_datatype procedure |
Adds a member to a priority group. |
ADD_SITE_PRIORITY_SITE procedure |
Adds a new site to a site priority group. |
ADD_conflicttype_RESOLUTION procedure |
Designates a method for resolving an update, delete, or uniqueness conflict. |
ALTER_MASTER_PROPAGATION procedure |
Alters the propagation method for a given object group at a given master site. |
ALTER_MASTER_REPOBJECT procedure |
Alters an object in your replicated environment. |
ALTER_PRIORITY procedure |
Alters the priority level associated with a given priority group member. |
ALTER_PRIORITY_datatype procedure |
Alters the value of a member in a priority group. |
ALTER_SITE_PRIORITY procedure |
Alters the priority level associated with a given site. |
ALTER_SITE_PRIORITY_SITE procedure |
Alters the site associated with a given priority level. |
ALTER_SNAPSHOT_PROPAGATION procedure |
Alters the propagation method for a given object group at the current snapshot site. |
CANCEL_STATISTICS procedure |
Stops collecting statistics about the successful resolution of update, uniqueness, and delete conflicts for a table. |
COMMENT_ON_COLUMN_GROUP procedure |
Updates the comment field in the |
COMMENT_ON_PRIORITY_ GROUP/COMMENT_ON_SITE_ PRIORITY procedure |
Updates the comment field in the |
COMMENT_ON_REPGROUP procedure |
Updates the comment field in the |
COMMENT_ON_REPSITES procedure |
Updates the comment field in the |
COMMENT_ON_REPOBJECT procedure |
Updates the comment field in the |
COMMENT_ON_conflicttype_ RESOLUTION procedure |
Updates the comment field in the |
CREATE_MASTER_REPGROUP procedure |
Creates a new, empty, quiesced master replication object group. |
CREATE_MASTER_REPOBJECT procedure |
Indicates that an object is a replicated object. |
CREATE_SNAPSHOT_REPGROUP procedure |
Creates a new, empty snapshot replication object group in your local database. |
CREATE_SNAPSHOT_REPOBJECT procedure |
Adds a replicated object to your snapshot site. |
DEFINE_COLUMN_GROUP procedure |
Creates an empty column group |
DEFINE_PRIORITY_GROUP procedure |
Creates a new priority group for a replicated master group. |
DEFINE_SITE_PRIORITY procedure |
Creates a new site priority group for a replicated master group. |
DO_DEFERRED_REPCAT_ADMIN procedure |
Executes the local outstanding deferred administrative procedures for the given replicated 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 replicated master group from your current site. |
DROP_MASTER_REPOBJECT procedure |
Drops a replicated object from a replicated master group. |
DROP_PRIORITY procedure |
Drops a member of a priority group by priority level. |
DROP_PRIORITY_GROUP procedure |
Drops a priority group for a given replicated 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 given replicated master group. |
DROP_SITE_PRIORITY_SITE procedure |
Drops a given site, by name, from a site priority group. |
DROP_SNAPSHOT_REPGROUP procedure |
Drops a snapshot site from your replicated environment. |
DROP_SNAPSHOT_REPOBJECT procedure |
Drops a replicated object from a snapshot site. |
DROP_conflicttype_ RESOLUTION procedure |
Drops an update, delete, or uniqueness conflict resolution routine. |
EXECUTE_DDL procedure |
Supplies DDL that you want to have executed at each master site. |
GENERATE_REPLICATION_ SUPPORT procedure |
Generates the triggers, packages, and procedures needed to support replication. |
GENERATE_SNAPSHOT_SUPPORT procedure |
Activates triggers and generate packages needed to support the replication of updatable snapshots or procedural replication. |
MAKE_COLUMN_GROUP procedure |
Creates a new column group with one or more members. |
PURGE_MASTER_LOG procedure |
Removes local messages in the |
PURGE_STATISTICS procedure |
Removes information from the |
REFRESH_SNAPSHOT_REPGROUP procedure |
Refreshes a snapshot site object group with the most recent data from its associated master site. |
REGISTER_SNAPSHOT_REPGROUP procedure |
Facilitates the administration of snapshots at their respective master sites by inserting/modifying/deleting from |
REGISTER_STATISTICS procedure |
Collects information about the successful resolution of update, delete and uniqueness conflicts for a table. |
RELOCATE_MASTERDEF procedure |
Changes your master definition site to another master site in your replicated environment. |
REMOVE_MASTER_DATABASES procedure |
Removes one or more master databases from a replicated environment. |
REPCAT_IMPORT_CHECK procedure |
Ensures that the objects in the replicated 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 replicated environment. |
SUSPEND_MASTER_ACTIVITY procedure |
Suspends replication activity for an object group |
SWITCH_SNAPSHOT_MASTER procedure |
Changes the master database of a snapshot replicated master group to another master site. |
UNREGISTER_SNAPSHOT_ REPGROUP procedure |
Facilitates the administration of snapshots at their respective master sites by inserting/modifying/deleting from |
VALIDATE function |
Validates the correctness of key conditions of a multiple master replication environment. |
WAIT_MASTER_LOG procedure |
Determines whether changes that were asynchronously propagated to a master site have been applied. |
This procedure adds members to an existing column group. You must call this procedure from the master definition site.
DBMS_REPCAT.ADD_GROUPED_COLUMN ( sname IN VARCHAR2, oname IN VARCHAR2, column_group IN VARCHAR2, list_of_column_names IN VARCHAR2 | DBMS_REPCAT.VARCHAR2S);
This procedure adds another master site to your replicated environment. This procedure regenerates all the triggers and their associated packages at existing master sites. You must call this procedure from the master definition site.
DBMS_REPCAT.ADD_MASTER_DATABASE ( gname IN VARCHAR2, master IN VARCHAR2, use_existing_objects IN BOOLEAN := TRUE, copy_rows IN BOOLEAN := TRUE, comment IN VARCHAR2 := '', propagation_mode IN VARCHAR2 := 'ASYNCHRONOUS', fname IN VARCHAR2 := NULL);
| Parameter | Description |
|---|---|
gname |
Name of the object group being replicated. This object group must already exist at the master definition site. |
master |
Fully qualified database name of the new master database. |
use_existing_objects |
Indicate |
copy_rows |
Indicate |
comment |
This is added to the |
propagation_mode |
Method of forwarding changes to and receiving changes from new master database. Accepted values are |
fname |
This system parameter is for internal use only. Do not set the parameter unless so directed by Oracle Worldwide Support. |
This procedure adds a member to a priority group. You must call this procedure from the master definition site. The procedure that you must call is determined by the datatype of your priority column. You must call this procedure once for each of the possible values of the priority column.
For additional information, see "Conflict Resolution" in the Oracle8i Replication manual.
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.
For additional information, see "Conflict Resolution" in the Oracle8i Replication manual.
DBMS_REPCAT.ADD_SITE_PRIORITY_SITE ( gname IN VARCHAR2, name IN VARCHAR2 site IN VARCHAR2, priority IN NUMBER);
This procedure designates a method for resolving an update, delete, or uniqueness conflict. You must call these procedures from the master definition site. The procedure that you need to call is determined by the type of conflict that the routine resolves.
| Conflict Type | Procedure Name |
|---|---|
update |
ADD_UPDATE_RESOLUTION |
uniqueness |
ADD_UNIQUE_RESOLUTION |
delete |
ADD_DELETE_RESOLUTION |
For more information about designating methods to resolve update conflicts, selecting uniqueness conflict resolution methods, and, assigning delete conflict resolution methods see "Conflict Resolution" in the Oracle8i Replication manual.
DBMS_REPCAT.ADD_UPDATE_RESOLUTION ( sname IN VARCHAR2, oname IN VARCHAR2, column_group IN VARCHAR2, sequence_no IN NUMBER, method IN VARCHAR2, parameter_column_name IN VARCHAR2 | DBMS_REPCAT.VARCHAR2S, priority_group IN VARCHAR2 := NULL, function_name IN VARCHAR2 := NULL, comment IN VARCHAR2 := NULL); DBMS_REPCAT.ADD_DELETE_RESOLUTION ( sname IN VARCHAR2, oname IN VARCHAR2, sequence_no IN NUMBER, parameter_column_name IN VARCHAR2 | DBMS_REPCAT.VARCHAR2S, function_name IN VARCHAR2, comment IN VARCHAR2 := NULL method IN VARCHAR2 := 'USER FUNCTION'); DBMS_REPCAT.ADD_UNIQUE_RESOLUTION( sname IN VARCHAR2, oname IN VARCHAR2, constraint_name IN VARCHAR2, sequence_no IN NUMBER, method IN VARCHAR2, parameter_column_name IN VARCHAR2 | DBMS_REPCAT.VARCHAR2S, function_name IN VARCHAR2 := NULL, comment IN VARCHAR2 := NULL);
| Parameter | Description |
|---|---|
sname |
Name of the schema containing the table to be replicated. |
oname |
Name of the table for which you are adding a conflict resolution routine. |
column_group |
Name of the column group for which you are adding a conflict resolution routine. Column groups are required for update conflict resolution routines only. |
constraint_name |
Name of the unique constraint or unique index for which you are adding a conflict resolution routine. Use the name of the unique index if it differs from the name of the associated unique constraint. Constraint names are required for uniqueness conflict resolution routines only. |
sequence_no |
Order in which the designated conflict resolution methods should be applied. |
method |
Type of conflict resolution routine that you want to create. This can be the name of one of the standard routines provided with advanced replication, or, if you have written your own routine, you should choose |
parameter_column_ name |
Name of the columns used to resolve the conflict. The standard methods operate on a single column. For example, if you are using the This argument accepts either a comma separated list of column names, or a PL/SQL table of type dbms_repcat.varchar2s. The single value '*' indicates that you want to use all of the columns in the table (or column group, for update conflicts) to resolve the conflict. If you specify '*', then the columns are passed to your function in alphabetical order. |
priority_group |
If you are using the
See "Conflict Resolution" in the Oracle8i Replication manual. If you are using a different method, you can use the default value for this argument, |
function_name |
If you selected the |
comment |
This user comment is added to the |
This procedure alters the propagation method for a given object group at a given master site. This object group must be quiesced. You must call this procedure from the master definition site. If the master appears in the dblink_list or dblink_table, then ALTER_MASTER_PROPAGATION ignores that database link. You cannot change the propagation mode from a master to itself.
DBMS_REPCAT.ALTER_MASTER_PROPAGATION ( gname IN VARCHAR2, master IN VARCHAR2, { dblink_list IN VARCHAR2, | dblink_table IN dbms_utility.dblink_array,} propagation_mode IN VARCHAR2 : ='asynchronous', comment IN VARCHAR2 := '');
This procedure alters an object in your replicated environment. You must call this procedure from the master definition site.
DBMS_REPCAT.ALTER_MASTER_REPOBJECT ( sname IN VARCHAR2, oname IN VARCHAR2, type IN VARCHAR2, ddl_text IN VARCHAR2, comment IN VARCHAR2 := '', retry IN BOOLEAN := FALSE);
If the DDL is supplied without specifying a schema, then the default schema is the replication administrator's schema. Be sure to specify the schema if it is other than the replication administrator's schema.
This procedure alters the priority level associated with a given priority group member. You must call this procedure from the master definition site.
See "Conflict Resolution" in the Oracle8i Replication manual.
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.
For additional information, see "Conflict Resolution" in the Oracle8i Replication manual.
DBMS_REPCAT.ALTER_PRIORITY_datatype ( gname IN VARCHAR2, pgroup IN VARCHAR2, old_value IN datatype, new_value IN datatype);
where datatype:
{ NUMBER | VARCHAR2 | CHAR | DATE | RAW | NCHAR | NVARCHAR2 }
This procedure alters the priority level associated with a given site. You must call this procedure from the master definition site.
See "Conflict Resolution" in the Oracle8i Replication manual.
DBMS_REPCAT.ALTER_SITE_PRIORITY ( gname IN VARCHAR2, name IN VARCHAR2, old_priority IN NUMBER, new_priority IN NUMBER);
This procedure alters the site associated with a given priority level. You must call this procedure from the master definition site.
See "Conflict Resolution" in the Oracle8i Replication manual.
DBMS_REPCAT.ALTER_SITE_PRIORITY_SITE ( gname IN VARCHAR2, name IN VARCHAR2, old_site IN VARCHAR2, new_site IN VARCHAR2);
This procedure alters the propagation method for a given object group at the current snapshot site. This procedure pushes the deferred transaction queue at the snapshot site, locks the snapshot base tables, and regenerates any triggers and their associated packages. You must call this procedure from the snapshot site.
DBMS_REPCAT.ALTER_SNAPSHOT_PROPAGATION ( gname IN VARCHAR2, propagation_mode IN VARCHAR2, comment IN VARCHAR2 := '');
This procedure stops collecting statistics about the successful resolution of update, uniqueness, and delete conflicts for a table.
DBMS_REPCAT.CANCEL_STATISTICS ( sname IN VARCHAR2, oname IN VARCHAR2);
| Parameter | Description |
|---|---|
sname |
Name of the schema in which the table is located. |
oname |
Name of the table for which you do not want to gather conflict resolution statistics. |
| Exception | Description |
|---|---|
missingschema |
Given schema does not exist. |
missingobject |
Given table does not exist. |
statnotreg |
Given table is not currently registered to collect statistics. |
This procedure updates the comment field in the RepColumn_Group view for a column group. This comment is not added at all master sites until the next call to DBMS_REPCAT.GENERATE_REPLICATION_SUPPORT.
DBMS_REPCAT.COMMENT_ON_COLUMN_GROUP ( sname IN VARCHAR2, oname IN VARCHAR2, column_group IN VARCHAR2, comment IN VARCHAR2);
| Exception | Description |
|---|---|
nonmasterdef |
Invocation site is not the master definition site. |
missinggroup |
Given column group does not exist. |
missingobj |
Object is missing. |
COMMENT_ON_PRIORITY_GROUP updates the comment field in the REPPRIORITY_GROUP view for a priority group. This comment is not added at all master sites until the next call to GENERATE_REPLICATION_SUPPORT.
COMMENT_ON_SITE_PRIORITY updates the comment field in the REPPRIORITY_GROUP view for a site priority group. This procedure is a wrapper for the COMMENT_ON_COLUMN_GROUP procedure and is provided as a convenience only. This procedure must be issued at the master definition site.
DBMS_REPCAT.COMMENT_ON_PRIORITY_GROUP ( gname IN VARCHAR2, pgroup IN VARCHAR2, comment IN VARCHAR2); DBMS_REPCAT.COMMENT_ON_SITE_PRIORITY ( gname IN VARCHAR2, name IN VARCHAR2, comment IN VARCHAR2);
This procedure updates the comment field in the REPGROUP view for a replicated 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 object group that you want to comment on. |
comment |
Updated comment to include in the |
| Exception | Description |
|---|---|
nonmasterdef |
Invocation site is not the master definition site. |
commfailure |
At least one master site is not accessible. |
This procedure updates the comment field in the RepSite view for a replicated site. This procedure must be issued at the master definition site.
DBMS_REPCAT.COMMENT_ON_REPSITES ( gname IN VARCHAR2, [ master IN VARCHAR,] comment IN VARCHAR2);
| Exception | Description |
|---|---|
nonmasterdef |
Invocation site is not the master definition site. |
nonmaster |
Invocation site is not a master site. |
commfailure |
At least one master site is not accessible. |
This procedure updates the comment field in the RepObject view for a replicated object. This procedure must be issued at the master definition site.
DBMS_REPCAT.COMMENT_ON_REPOBJECT ( sname IN VARCHAR2, oname IN VARCHAR2, type IN VARCHAR2, comment IN VARCHAR2);
This procedure updates the comment field in the RepResolution view for a conflict resolution routine. The procedure that you need to call is determined by the type of conflict that the routine resolves. These procedures must be issued at the master definition site.
| Conflict Type | Procedure Name |
|---|---|
|
update |
COMMENT_ON_UPDATE_RESOLUTION |
|
uniqueness |
COMMENT_ON_UNIQUE_RESOLUTION |
|
delete |
COMMENT_ON_DELETE_RESOLUTION |
The comment is not added at all master sites until the next call to GENERATE_REPLICATION_SUPPORT.
DBMS_REPCAT.COMMENT_ON_UPDATE_RESOLUTION ( sname IN VARCHAR2, oname IN VARCHAR2, column_group IN VARCHAR2, sequence_no IN NUMBER, comment IN VARCHAR2); DBMS_REPCAT.COMMENT_ON_UNIQUE_RESOLUTION ( sname IN VARCHAR2, oname IN VARCHAR2, constraint_name IN VARCHAR2, sequence_no IN NUMBER, comment IN VARCHAR2); DBMS_REPCAT.COMMENT_ON_DELETE_RESOLUTION ( sname IN VARCHAR2, oname IN VARCHAR2, sequence_no IN NUMBER, comment IN VARCHAR2);
You have the option of comparing old column values for each non-key column of a replicated table for updates and deletes. The default is to compare old values for all columns. You can change this behavior at all master and snapshot sites by invoking DBMS_REPCAT.COMPARE_OLD_VALUES at the master definition site.
DBMS_REPCAT.COMPARE_OLD_VALUES( sname IN VARCHAR2, oname IN VARCHAR2, { column_list IN VARCHAR2, | column_table IN DBMS_REPCAT.VARCHAR2s,} operation IN VARCHAR2 := `UPDATE', compare IN BOOLEAN := TRUE );
|
Note:
The Read "Minimizing Data Propagation for Update Conflict Resolution" in the Oracle8i Replication manual before changing the default behavior of Oracle. |
This procedure creates a new, empty, quiesced master replication object group.
DBMS_REPCAT.CREATE_MASTER_REPGROUP ( gname IN VARCHAR2, group_comment IN VARCHAR2 := '', master_comment IN VARCHAR2 := ''), qualifier IN VARCHAR2 := '');
| Parameter | Description |
|---|---|
gname |
Name of the object group that you want to create. |
group_comment |
This comment is added to the |
master_comment |
This comment is added to the |
qualifier |
Connection qualifier for object group. Be sure to use the @ sign, as shown in the example: See "Managing Master Groups" in the Oracle8i Replication manual. |
This procedure indicates that an object is a replicated object.
DBMS_REPCAT.CREATE_MASTER_REPOBJECT ( sname IN VARCHAR2, oname IN VARCHAR2, type IN VARCHAR2, use_existing_object IN BOOLEAN := TRUE, ddl_text IN VARCHAR2 := NULL, comment IN VARCHAR2 := '', retry IN BOOLEAN := FALSE copy_rows IN BOOLEAN := TRUE, gname IN VARCHAR2 := '');
| Parameters | Description |
|---|---|
sname |
Name of the schema in which the object that you want to replicate is located. |
oname |
Name of the object you are replicating. If |
type |
Type of the object that you are replicating. The types supported are: |
use_existing_object |
Indicate |
ddl_text |
If the object does not already exist at the master definition site, then you must supply the DDL text necessary to create this object. PL/SQL packages, package bodies, procedures, and functions must have a trailing semicolon. SQL statements do not end with trailing semicolon. Oracle does not parse this DDL before applying it; therefore, you must ensure that your DDL text provides the appropriate schema and object name for the object being created. |
comment |
This comment is added to the |
retry |
Indicate |
copy_rows |
Indicate |
gname |
Name of the object group in which you want to create the replicated object. The schema name is used as the default object group name if none is specified. |
If the DDL is supplied without specifying a schema, then the default schema is the replication administrator's schema. Be sure to specify the schema if it is other than the replication administrator's schema.
This procedure creates a new, empty snapshot group in your local database.
DBMS_REPCAT.CREATE_SNAPSHOT_REPGROUP ( gname IN VARCHAR2, master IN VARCHAR2, comment IN VARCHAR2 := '', propagation_mode IN VARCHAR2 := 'ASYNCHRONOUS', fname IN VARCHAR2 := NULL);
CREATE_SNAPSHOT_REPGROUP automatically calls REGISTER_SNAPSHOT_REPGROUP, but ignores any errors that may have happened during registration.
This procedure adds a replicated object to your snapshot site.
DBMS_REPCAT.CREATE_SNAPSHOT_REPOBJECT ( sname IN VARCHAR2, oname IN VARCHAR2, type IN VARCHAR2, ddl_text IN VARCHAR2 := '', comment IN VARCHAR2 := '', gname IN VARCHAR2 := '', gen_objs_owner IN VARCHAR2 := '', min_communication IN BOOLEAN := TRUE , generate_80_compatible IN BOOLEAN := TRUE);
| Parameter | Description |
|---|---|
sname |
Name of the schema in which the object is located. |
oname |
Name of the object that you want to add to the replicated snapshot object group. |
type |
Type of the object that you are replicating. The types supported for snapshot sites are: |
ddl_text |
For objects of type |
comment |
This comment is added to the |
gname |
Name of the replicated master group to which you are adding an object. The schema name is used as the default group name if none is specified. |
gen_objs_owner |
Name of the user you want to assign as owner of the transaction. |
min_communication |
Set to |
generate_80_ compatible |
Set to |
If the DDL is supplied without specifying a schema, then the default schema is the replication administrator's schema. Be sure to specify the schema if it is other than the replication administrator's schema.
This procedure creates an empty column group. You must call this procedure from the master definition site.
For more information, see "Conflict Resolution" in the Oracle8i Replication manual.
DBMS_REPCAT.DEFINE_COLUMN_GROUP ( sname IN VARCHAR2, oname IN VARCHAR2, column_group IN VARCHAR2, comment IN VARCHAR2 := NULL);
This procedure creates a new priority group for a replicated master group. You must call this procedure from the master definition site.
See "Conflict Resolution" in the Oracle8i Replication manual.
DBMS_REPCAT.DEFINE_PRIORITY_GROUP ( gname IN VARCHAR2, pgroup IN VARCHAR2, datatype IN VARCHAR2, fixed_length IN INTEGER := NULL, comment IN VARCHAR2 := NULL);
This procedure creates a new site priority group for a replicated master group. You must call this procedure from the master definition site.
See "Conflict Resolution" in the Oracle8i Replication manual.
DBMS_REPCAT.DEFINE_SITE_PRIORITY ( gname IN VARCHAR2, name IN VARCHAR2, comment IN VARCHAR2 := NULL);
This procedure executes the local outstanding deferred administrative procedures for the given replicated master group at the current master site, or (with assistance from job queues) for all master sites.
DBMS_REPCAT.DO_DEFERRED_REPCAT_ADMIN ( gname IN VARCHAR2, all_sites IN BOOLEAN := FALSE);
| Parameter | Description |
|---|---|
gname |
Name of the replicated 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 |
DO_DEFERRED_REPCAT_ADMIN executes only those administrative requests submitted by the connected user that called DO_DEFERRED_REPCAT_ADMIN. Requests submitted by other users are ignored.
This procedure drops a column group. You must call this procedure from the master definition site.
See "Conflict Resolution" in the Oracle8i Replication manual.
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.
For more information, see "Conflict Resolution" in the Oracle8i Replication manual.
DBMS_REPCAT.DROP_GROUPED_COLUMN ( sname IN VARCHAR2, oname IN VARCHAR2, column_group IN VARCHAR2, list_of_column_names IN VARCHAR2 | DBMS_REPCAT.VARCHAR2S);
| Exception | Description |
|---|---|
nonmasterdef |
Invocation site is not the masterdef site. |
missingobject |
Given table does not exist. |
notquiesced |
replicated master group that the table belongs to is not quiesced. |
This procedure drops a replicated master group from your current site. To drop the replicated master group from all master sites, including the master definition site, you can call this procedure at the master definition site, and set the final argument to TRUE.
DBMS_REPCAT.DROP_MASTER_REPGROUP ( gname IN VARCHAR2, drop_contents IN BOOLEAN := FALSE, all_sites IN BOOLEAN := FALSE);
This procedure drops a replicated object from a replicated 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 member of a priority group by priority level. You must call this procedure from the master definition site.
See "Conflict Resolution" in the Oracle8i Replication manual.
DBMS_REPCAT.DROP_PRIORITY( gname IN VARCHAR2, pgroup IN VARCHAR2, priority_num IN NUMBER);
This procedure drops a priority group for a given replicated master group. You must call this procedure from the master definition site.
See "Conflict Resolution" in the Oracle8i Replication manual.
DBMS_REPCAT.DROP_PRIORITY_GROUP ( gname IN VARCHAR2, pgroup IN VARCHAR2);
| Parameter | Description |
|---|---|
gname |
replicated 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 "Conflict Resolution" in the Oracle8i Replication manual.
DBMS_REPCAT.DROP_PRIORITY_datatype ( gname IN VARCHAR2, pgroup IN VARCHAR2, value IN datatype);
where datatype:
{ NUMBER | VARCHAR2 | CHAR | DATE | RAW | NCHAR | NVARCHAR2 }
This procedure drops a site priority group for a given replicated master group. You must call this procedure from the master definition site.
See "Conflict Resolution" in the Oracle8i Replication manual.
DBMS_REPCAT.DROP_SITE_PRIORITY ( gname IN VARCHAR2, name IN VARCHAR2);
| Parameter | Description |
|---|---|
gname |
replicated 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 given site, by name, from a site priority group. You must call this procedure from the master definition site.
See "Conflict Resolution" in the Oracle8i Replication manual.