Release 8.0
A54651-01
 Library |
 Product |
 Contents |
 Index |
| Oracle8(TM) Server Replication Release 8.0 A54651-01 |
|
This chapter describes the data dictionary views that can be useful to users of the advanced replication facility. The views are alphabetized within the following general groupings:
Whenever you install advanced replication capabilities at a site, Oracle installs the replication catalog, which consists of tables and views, at that site. As shown in Table 11-1, the views are used by master and snapshot sites to determine such information as what objects are being replicated, where they are being replicated, and if any errors have occurred during replication. You should not modify the replication catalog tables directly; use the procedures provided in the DBMS_REPCAT package.
Each view has three versions, which have different prefixes: USER_*, ALL_*, and SYS.DBA_* unless otherwise stated. This section ignores any differences between these views.
The REPGROUP view lists all of the object groups that are being replicated. The members of each object group are listed in a different view, REPOBJECT.
The REPCATLOG at each master site contains the interim status of any asynchronous administrative requests and any error messages generated. All messages encountered while executing a request are eventually transferred to the REPCATLOG at the master that originated the request. If an administrative request completes without error, ultimately all traces of this request are removed from the REPCATLOG view.
The REPCOLUMN view lists the replicated columns for a table.
The REPCOLUMN_GROUP view lists all of the column groups that you have defined for each replicated table.
| Column | Description |
|---|---|
|
sname |
The name of the schema containing the replicated table. |
|
oname |
The name of the replicated table. |
|
group_name |
The column group name. |
|
group_Comment |
Any user-supplied Comments. |
Note: The sname column is not present in the USER_ view.
The REPCONFLICT view displays the name of the table for which you have defined a conflict resolution method and the type of conflict that the method is used to resolve.
Note: The sname column is not present in the USER_ view.
The REPDDL holds DDL for replication objects.
The REPGENERATED view lists information about system-generated objects.
Note: The REPGENERATED view is obsolete and is kept only for backward compatibility.
The REPGROUPED_COLUMN view lists all of the columns that make up the column groups for each table.
Note: The sname column is not present in the USER_ version of the view.
The REPKEY_COLUMNS view lists information relating to the primary key column.
| Column | Description |
|---|---|
|
sname |
Owner of the replicated table. |
|
oname |
Name of the replicated table. |
|
col |
"Primary Key" column name in the table. |
The REPOBJECT view provides information about the objects in each replicated object group. An object can belong to only one object group. A replicated object group can span multiple schemas.
In addition to the information contained in the REPRESOLUTION view, the REPPARAMETER_COLUMN view also contains information about the columns that you indicated should be used to resolve the conflict. These are the column values that are passed as the LIST_OF_COLUMN_NAMES argument to the ADD_*_RESOLUTION procedures in the DBMS_REPCAT package.
Note: The SNAME column is not present in the USER_ view.
The REPPRIORITY view displays the value and priority level of each priority group member. Priority group names must be unique within a replicated object group. Priority levels and values must each be unique within a given priority group.
Note: The SNAME and GNAME columns are not present in the USER_ view.
The REPPRIORITY_GROUP view lists the priority and site priority groups that you have defined for a replicated object group.
The REPPROP view indicates the technique used to propagate operations on an object to the same object at another master site. These operations may have resulted from a call to a stored procedure or procedure wrapper, or may have been issued against a table directly.
The REPRESOLUTION view indicates the routines used to resolve update, unique or delete conflicts for each table replicated using row-level replication for a given schema.
Note: The SNAME column is not present in the USER_ view.
The REPRESOL_STATS_CONTROL view lists information about statistics collection for conflict resolutions for all replicated tables in the database.
Note: The SNAME column is not present in the USER_ view.
The REPRESOLUTION_METHOD view lists all of the conflict resolution routines available in your current database. Initially, this view lists the standard routines provided with the advanced replication facility. As you create new user functions and add them as conflict resolution methods for an object in the database, these functions are added to this view.
The REPRESOLUTION_STATISTICS view lists information about successfully resolved update, uniqueness, and delete conflicts for all replicated tables. These statistics are only gathered for a table if you have called DBMS_REPCAT.REGISTER_STATISTICS.
Note: The SNAME column is not present in the USER_ view.
The REPSITES view lists the members of each replicated object group.
The DBA_REPSITES view has the following additional columns:
|
prop_updates |
Number of requested updates for master. |
|
my_dblink |
Used to detect problem after import. If Y, the dblink is the global name. |
The REPGENOBJECTS view describes objects generated to support replication.
Oracle provides several views for you to use in administering deferred transactions. These views provide information about each deferred transaction, such as the transaction destinations, the deferred calls that make up the transactions, and any errors encountered during attempted execution of the transaction. You should not modify the tables directly; use the procedures provided in the DBMS_DEFER and DBMS_DEFER_SYS packages.
The DEFCALL view records all deferred remote procedure calls.
The DEFCALLDEST view lists the destinations for each deferred remote procedure call.
If you are not using Oracle's replication facility and do not supply a destination for a deferred transaction or the calls within that transaction, Oracle uses the DEFDEFAULTDEST view to determine the destination databases to which you want to defer a remote procedure call.
| Column | Description |
|---|---|
|
dblink |
The fully qualified database name to which to replicate a transaction. |
The DEFERRCOUNT view provides information about the error transactions for a given destination.
| Column | Description |
|---|---|
|
errcount |
Number of existing transactions that caused an error for the destination. |
|
destination |
Database link used to address destination. |
The DEFERROR view provides the ID of each transaction that could not be applied. You can use this ID to locate the queued calls associated with this transaction. These calls are stored in the DEFCALL view. You can use the procedures in the DBMS_DEFER_QUERY package to determine the arguments to the procedures listed in the DEFCALL view.
The DEFLOB view stores the LOB parameters to deferred RPCs.
The DEFPROPAGATOR view displays information about the local propagator.
| Column | Description |
|---|---|
|
username |
Username of the propagator. |
|
userid |
User ID of the propagator. |
|
status |
Status of the propagator. |
|
created |
Time when the propagator was registered. |
The DEFSCHEDULE view displays information about when a job is next scheduled to be executed.
The DEFTRAN view records all deferred transactions.
The DEFTRANDEST view lists the destinations for a deferred transaction.
Oracle provides the following views that have information about snapshots and snapshot refresh groups.
The SNAPSHOTS catalog view lists information about all of the snapshots in a database.
Note: UPDATE_TRIG: NULL in Oracle8 because of internalized triggers; MASTER_VIEW: NULL in Oracle8, now obsolete.
This view describes local or remote snapshots of local tables.
The SNAPSHOT_LOGS view describes all the snapshot logs in the database.
Note: The view shows one row for each snapshot using the log. However, there is only one for all the snapshots located at the master site. To find out which logs are used, query USER_SNAPSHOT_LOGS using unique and not selecting SNAPSHOT_ID and CURRENT_SNAPSHOTS.
The REFRESH view lists each refresh group found in the database, and includes information about the refresh interval for each group.
The REFRESH_CHILDREN view lists the members of each refresh group owned by the user, and includes information about the refresh interval for each member.
