Replication Management API Reference, 25 of 179

PUSH function

This function forces a deferred remote procedure (RPC) call queue at your current master or snapshot site to be pushed (propagated) to another master site using either serial or parallel propagation.

Syntax

DBMS_DEFER_SYS.PUSH (
   destination          IN  VARCHAR2,
   parallelism          IN  BINARY_INTEGER := 0,
   heap_size            IN  BINARY_INTEGER := 0,
   stop_on_error        IN  BOOLEAN        := FALSE,
   write_trace          IN  BOOLEAN        := FALSE,
   startup_seconds      IN  BINARY_INTEGER := 0,
   execution_seconds    IN  BINARY_INTEGER := seconds_infinity,
   delay_seconds        IN  BINARY_INTEGER := 0,
   transaction_count    IN  BINARY_INTEGER := transactions_infinity,
   delivery_order_limit IN  NUMBER         := delivery_order_infinity)
  RETURN BINARY_INTEGER;

Parameters

Table 8-40 PUSH Function Parameters (Page 1 of 2)

Parameter	Description
destination	The fully qualified database name of the master to which you are forwarding changes.
parallelism	0 specifies serial propagation; n > 1 specifies parallel propagation with n parallel server processes; 1 specifies parallel propagation using only one parallel server process.
heap_size	Maximum number of transactions to be examined simultaneously for parallel propagation scheduling. Oracle automatically calculates the default setting for optimal performance. Do not set the parameter unless so directed by Oracle Worldwide Support.
stop_on_error	The default, `FALSE`, indicates that the executor should continue even if errors, such as conflicts, are encountered. If `TRUE`, then shut down (cleanly if possible) at the first indication that a transaction encountered an error at the destination site.
write_trace	When set to `TRUE`, Oracle records the result value returned by the function in the server's trace file.
startup_seconds	Maximum number of seconds to wait for a previous push to the same destination.
execution_seconds	If >0, then stop push cleanly after the specified number of seconds of real time. If `transaction_count` and `execution_seconds` are zero (the default), then transactions are executed until there are no more in the queue. The `execution_seconds` parameter only controls the duration of time that operations can be started. It does not include the amount of time that the transactions require at remote sites. Therefore, the `execution_seconds` parameter is not intended to be used as a precise control to stop the propagation of transactions to a remote site. If a precise control is required, use the `transaction_count` or `delivery_order` parameters.
delay_seconds	Do not return before the specified number of seconds have elapsed, even if the queue is empty. Useful for reducing execution overhead if `PUSH` is called from a tight loop.
transaction_count	If > 0, then the maximum number of transactions to be pushed before stopping. If `transaction_count` and `execution_seconds` are zero (the default), then transactions are executed until there are no more in the queue that need to be pushed.
delivery_order_ limit	Stop execution cleanly before pushing a transaction where `delivery_order` >= `delivery_order_limit`

Returns

Table 8-41 PUSH Function Returns

Value	Description
0	OK, terminated after `delay_seconds` expired.
1	Terminated by lock timeout while starting.
2	Terminated by exceeding `execution_seconds`.
3	Terminated by exceeding `transaction_count`.
4	Terminated by exceeding `delivery_order_limit`.
5	Terminated after errors.

PUSH

Exceptions

Table 8-42 PUSH Function Exceptions

Exception	Description
deferror incompleteparallelpush	Serial propagation requires that parallel propagation shuts down cleanly.
executiondisabled	Execution of deferred RPCs is disabled at the destination.
crt_err_err	Error while creating entry in `DEFERROR`.
deferred_rpc_qiesce	Replication activity for object group is suspended.
commfailure	Communication failure during deferred RPC.
missingpropator	A propagator does not exist.