Oracle7 Server Distributed Systems Volume II: Replicated Data

DBMS_DEFER_SYS.SCHEDULE_EXECUTION

Purpose

To establish communication between a master or snapshot site and another master site. For additional information, refer to

Syntax

The parameters for the SCHEDULE_EXECUTION procedure are described in Table 12 - 25. The syntax for this procedure is shown below:

DBMS_DEFER_SYS.SCHEDULE_EXECUTION(
	dblink 	IN 	VARCHAR2,
	interval 	IN 	VARCHAR2,
	next_date 	IN 	DATE,
	reset	IN	BOOLEAN default FALSE,
	stop_on_error	IN	BOOLEAN := NULL,
	transaction_count	IN	BINARY_INTEGER := NULL,
	execution_seconds	IN	BINARY_INTEGER := NULL,
	execute_as_user	IN	BOOLEAN := NULL,
	delay_seconds	IN	NATURAL := NULL,
	batch_size	IN	NATURAL := NULL)

Parameter Description
dblink Fully qualified pathname to master database site at which you want to schedule periodic execution of deferred remote procedure calls.
interval Allows you to provide a function that is used to calculate the next time to apply any changes. This value is stored in the INTERVAL field of the DefSchedule view and is used to calculate the NEXT_DATE field of this view. If you use the default value for this parameter, NULL, the value of this field remains unchanged. If the field had no previous value, it is created with a value of null. If you do not supply a value for this field, you must supply a value for NEXT_DATE.
next_date Allows you to specify a given time to apply any outstanding changes to the given master site. This value is stored in the NEXT_DATE field of the DefSchedule view. If you use the default value for this parameter, NULL, the value of this field remains unchanged. If this field had no previous value, it is created with a value of null. If you do not supply a value for this field, you must supply a value for INTERVAL.
Scheduling a communication interval between master sites is very similar to scheduling a refresh interval for snapshots, as described .
reset Set to TRUE to reset LAST_TXN_COUNT, LST_ERROR, and LAST_MSG to NULL.
stop_on_error
transaction_count
execution_seconds
execute_as_user
delay_seconds
batch_size These parameters are passed to the DBMS_DEFER_SYS.EXECUTE call that is scheduled for execution by this call. See Table 12 - 23 for more information on how these parameters are used by EXECUTE.

Table 12 - 25. Parameters for SCHEDULE_EXECUTION

Parameter	Description
`dblink`	Fully qualified pathname to master database site at which you want to schedule periodic execution of deferred remote procedure calls.
`interval`	Allows you to provide a function that is used to calculate the next time to apply any changes. This value is stored in the INTERVAL field of the DefSchedule view and is used to calculate the NEXT_DATE field of this view. If you use the default value for this parameter, NULL, the value of this field remains unchanged. If the field had no previous value, it is created with a value of null. If you do not supply a value for this field, you must supply a value for NEXT_DATE.
`next_date`	Allows you to specify a given time to apply any outstanding changes to the given master site. This value is stored in the NEXT_DATE field of the DefSchedule view. If you use the default value for this parameter, NULL, the value of this field remains unchanged. If this field had no previous value, it is created with a value of null. If you do not supply a value for this field, you must supply a value for INTERVAL.
	Scheduling a communication interval between master sites is very similar to scheduling a refresh interval for snapshots, as described .
`reset`	Set to TRUE to reset LAST_TXN_COUNT, LST_ERROR, and LAST_MSG to NULL.
`stop_on_error` `transaction_count` `execution_seconds` `execute_as_user` `delay_seconds` `batch_size`	These parameters are passed to the DBMS_DEFER_SYS.EXECUTE call that is scheduled for execution by this call. See Table 12 - 23 for more information on how these parameters are used by EXECUTE.