DEFSCHEDULE

Contains information about when a job is next scheduled to be executed and also includes propagation statistics. The propagation statistics are for propagation of deferred transactions from the current site to the site specified in the DBLINK column.

To clear the propagation statistics for a remote site and start fresh, use the CLEAR_PROP_STATISTICS procedure in the DBMS_DEFER_SYS package.

See Also:

"CLEAR_PROP_STATISTICS Procedure"

Column	Datatype	NULL	Description
`DBLINK`	`VARCHAR2(128)`	`NOT NULL`	Fully qualified path name to the master site for which you have scheduled periodic execution of deferred remote procedure calls.
`JOB`	`NUMBER`	-	Number assigned to job when you created it by calling `DBMS_DEFER_SYS.SCHEDULE_PUSH`. Query the `WHAT` column of the `USER_JOBS` view to determine what is executed when the job is run.
`INTERVAL`	`VARCHAR2(200)`	-	Function used to calculate the next time to push the deferred transaction queue to destination.
`NEXT_DATE`	`DATE`	-	Next date that job is scheduled to be executed.
`LAST_DATE`	`DATE`	-	Last time the queue was pushed (or attempted to push) remote procedure calls to this destination.
`DISABLED`	`CHAR(1)`	-	If `Y` then propagation to destination is disabled. If `N` then propagation to the destination is enabled.
`LAST_TXN_COUNT`	`NUMBER`	-	Number of transactions pushed during last attempt.
`LAST_ERROR_NUMBER`	`NUMBER`	-	Oracle error number from last push.
`LAST_ERROR_MESSAGE`	`VARCHAR2(2000)`	-	Error message from last push.
`CATCHUP`	`RAW(16)`	`NOT NULL`	The extension identifier associated with a new master site that is being added to a master group without quiescing the master group. If there is no extension identifier for a master site, then the value is `00`.
`TOTAL_TXN_COUNT`	`NUMBER`	-	Total combined number of successful transactions and error transactions.
`AVG_THROUGHPUT`	`NUMBER`	-	The average number of transactions for each second that are propagated using parallel propagation. The transactions include both successfully applied transactions and error transactions created on the remote site. Time that has elapsed when the propagation coordinator is inactive (sleeping) is included in the calculation.
`AVG_LATENCY`	`NUMBER`	-	If the transaction is successfully applied at the remote site, then the average number of seconds between the first call of a transaction on the current site and the confirmation that the transaction was applied at the remote site. The first call begins when the user makes the first data manipulation language (DML) change, not when the transaction is committed. If the transaction is an error transaction, then the average number of seconds between the first call of a transaction on the current site and the confirmation that the error transaction is committed on the remote site.
`TOTAL_BYTES_SENT`	`NUMBER`	-	Total number of bytes sent, including replicated data and metadata.
`TOTAL_BYTES_RECEIVED`	`NUMBER`	-	Total number of bytes received in propagation confirmation messages.
`TOTAL_ROUND_TRIPS`	`NUMBER`	-	Total number of network round trips completed to replicate data. A round trip is one or more consecutively sent messages followed by one or more consecutively received messages. So, if site A sends 20 messages to site B and then site B sends one message to site A, then that is that one round trip.
`TOTAL_ADMIN_COUNT`	`NUMBER`	-	Total number of administrative requests sent to maintain information about transactions applied at the receiving site. The receiving site is the site specified in the `DBLINK` column. This special administration is only required for parallel propagation.
`TOTAL_ERROR_COUNT`	`NUMBER`	-	Total number of unresolved conflicts for which a remote error was created.
`TOTAL_SLEEP_TIME`	`NUMBER`	-	Total number of seconds the propagation coordinator was inactive (sleeping). You control the amount of time that the propagation coordinator sleeps using the `delay_seconds` parameter in the `DBMS_DEFER_SYS.PUSH` function.
`DISABLED_INTERNALLY_SET`	`VARCHAR2(1)`	-	This value is relevant only if `DISABLED` is `Y`. If `DISABLED_INTERNALLY_SET` is `Y` then propagation to destination was set to disabled internally by Oracle for propagation synchronization when adding a new master site to a master group without quiescing the master group. Oracle will enable propagation automatically at a later time. If `DISABLED_INTERNALLY_SET` is `N` then propagation was not disabled internally.