Name
DBMS_REPCAT.DROP_conflicttype_RESOLUTION
Synopsis
The DROP_conflicttype_RESOLUTION procedure removes a conflict resolution type from a replicated table. The value of conflicttype can be UPDATE, UNIQUE, or DELETE.
PROCEDURE DBMS_REPCAT.DROP_UPDATE_RESOLUTION
(sname IN VARCHAR2,
oname IN VARCHAR2,
column_group IN VARCHAR2,
sequence_no IN NUMBER) ;
PROCEDURE DBMS_REPCAT.DROP_UNIQUE_RESOLUTION
(sname IN VARCHAR2,
oname IN VARCHAR2,
constraint_name IN VARCHAR2,
sequence_no IN NUMBER) ;
PROCEDURE DBMS_REPCAT.DROP_DELETE_RESOLUTION
(sname IN VARCHAR2,
oname IN VARCHAR2,
sequence_no IN NUMBER) ;Parameters
Parameter Name | Description |
|---|---|
sname | Name of the schema containing the replicated schema. Defaults to current user. |
oname | Name of the replicated table. |
column_group | Column group for which the conflict resolution method is defined. |
constraint_name | For procedure DROP_UNIQUE_RESOLUTION only. Name of the constraint name or unique index for which the conflict resolution method is defined. |
sequence_no | Number indicating when this conflict resolution method is applied relative to other conflict resolution methods defined for the same column group or priority group. |
Exceptions
Exception Name | Number | Description |
|---|---|---|
missingobject | –23308 | Table oname does not exist in the replication group. |
missingschema | –23306 | Schema sname does not exist. |
nonmasterdef | –23312 | Calling site is not the master definition site. |
Restrictions
You must call this procedure from the master definition site.
After this call, you must generate replication support ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access