Oracle's advanced replication option relies primarily on deferred transactions and remote procedure calls (RPCs). When you commit a transaction against a replicated table, for example, the replication support triggers queue a deferred transaction to do your bidding in one or more remote databases. In addition to providing many of the underpinnings for the advanced replication option, the packages used to create and manipulate deferred calls are available for direct use in your applications. You will use the packages described in this chapter for deferred transactions and RPCs.
Performs administrative tasks such as scheduling, executing, and deleting queued transactions.
Builds deferred calls.
Provides access to parameters passed to deferred calls, primarily for diagnostic purposes.
NOTE: Users must have explicit EXECUTE privileges on DBMS_DEFER in order to create deferred calls.
This section provides some basic information you'll find useful in using the packages described in this chapter.
If you are using the advanced replication option, you have implicitly named the destinations for deferred RPCs and transactions by creating master sites. Whenever a user performs DML on a table, the transaction is applied locally and is queued for delivery to all other sites where the table is replicated; these sites are listed in the DBA_REPSITES data dictionary view. Similarly, replicated procedure calls are also queued for all master sites in the replicated environment. Refer to Chapter 15, Advanced Replication, for details on using DBMS_REPCAT, which performs most replicated environment administration operations.
If you are not using the advanced replication option, then the destination site(s) are determined by one of the following means, listed in order of precedence:
The sites specified in the nodes parameter in the call to DBMS_DEFER.CALL, described later in this chapter.
The sites specified in the nodes parameter to DBMS_DEFER.TRANSACTION, described later in this chapter.
The sites specified in the DEFDEFAULTDEST data dictionary view, described later in this chapter (Table 17.4).
If Oracle cannot determine a call's destination by any of these methods, or if you specify differing destinations in the DBMS_DEFER.TRANSACTION and DBMS_DEFER.CALL procedures, the deferred call will raise an exception.
There are eight data dictionary views (see Table 17.1) that contain data about deferred transactions and RPCs. You can query these views to determine information such as the destination of RPC calls, error messages, and scheduled execution times. Most of the packages associated with deferred calls reference and/or modify the data in these views.
Tables 17-2 through 17-9 provide details about the contents of these views.
Contains information about all deferred RPCs. Queries SYSTEM.DEF$_CALL table.
Contains the destination database(s) for each deferred RPC in DEFCALL. Queries SYSTEM.DEF$_CALL, SYSTEM.DEF$_DESTINATION, SYSTEM.DEF$_CALLDEST, SYSTEM.DEF$_ERROR, and SYSTEM.REPCAT$_REPPROP.
Contains the default destinations for deferred RPCs. Queries SYSTEM.DEF$_DEFAULTDEST.
Contains error information for deferred calls that could not be applied at their destination. Queries SYSTEM.
Contains the count of errors for each destination. Queries SYSTEM.DEF$_ERROR.
Contains information about the scheduling of deferred jobs. Queries SYSTEM.DEF$_DESTINATION and SYS.JOB$.
Contains information about all deferred calls. Queries SYSTEM.DEF$_CALL and SYS.USER$.
Contains the destination database(s) for each deferred transaction. Queries SYSTEM.DEF$_CALL, SYSTEM.DEF$_DESTINATION, SYSTEM.DEF$_ERROR, SYSTEM.DEF$_CALLDEST, and SYSTEM.REPCAT$_REPPROP.
Unique ID of call at deferred_tran_db
Global name of database that originated the call
Unique ID of the transaction
Schema that owns the package
Name of the package
Name of the procedure within the package
Number of arguments passed to the procedure
Unique ID of call at deferred_tran_db.
Unique ID of the transaction. Note that each deferred_tran_id has one or more calls.
Global name of database that originated the call.
Global name of the destination database.
Global name of the destination database
Global name of the database that originated the RPC
ID of the transaction originating or copying the deferred RPC
Unique ID of call at deferred_tran_db
Database link used to specify the destination database
Time the error occurred
Oracle error number
Error message text
Number of errors in deferred RPC calls to destination
Global name of destination database
Global name of the database for which pushes of deferred RPC calls is scheduled
Number of the job (job column in DBA_JOBS)
Date expression that determines how often the job runs
Next time the job is scheduled to run
Last time the job ran
Y if propagation to destination is disabled, otherwise N
Number of transactions pushed last time job ran
Oracle error number from the most recent push
Error message text from the most recent push
ID of the transaction that originated or copied the deferred RPCs.
Global name of the database that originated or copied the deferred RPCs.
ID of the transaction that originated the deferred RPCs.
Global name of the database that originated the deferred RPCs.
USERID of user originating deferred RPC calls.
SCN of the deferred transaction in the queue.
R if destinations are determined by the DBA_REPSCHEMA data dictionary view. D if destinations were specified in DEFDEFAULTDEST or the NODE_LIST parameter to the DBMS_DEFER.TRANSACTION, DBMS_DEFER.CALL, or DBMS_DEFER.COPY procedures.
Start time of the origination transaction.
ID of the transaction to propagate to database specified by dblink
Global name of the database that originated the deferred transaction
|16.6 Monitoring Conflict Resolution with DBMS_REPCAT||17.2 DBMS_DEFER_SYS: Managing Deferred Transactions|
Copyright (c) 2000 O'Reilly & Associates. All rights reserved.