Capture Process States
ENQUEUING MESSAGE – The process is
enqueuing a LCR that satisfies the Capture process rule sets
into the Capture process queue.
PAUSED FOR FLOW CONTROL – The
process is unable to enqueue LCRs either because of low memory
or because propagations and Apply processes are consuming
messages slower than the Capture process is creating them. This
state indicates flow control that is used to reduce spilling of
captured LCRs when propagation or apply has fallen behind. This
potentially can happen when there is huge transactional activity
on the source database tables.
SHUTTING DOWN – The process is
Next information on how to manage various
parameters for a Capture process will be presented.
Setting Up the Capture Parameters
Even though a simple format of the Capture
process can be created by using the add_table_rules,
add_schema_rules or add_subset_rules, certain extra
parameters can be set up only by executing the set_parameter
procedure of the dbms_capture_adm package. Capture
process parameters control the way a Capture process operates.
What are the parameters that are allowed to
be altered? Table 4.1 shows all of the parameters that can be
If set to Y, the Capture process is
disabled if the Capture process terminates because it
reached a value specified by the time_limit
parameter or message_limit parameter. If set to
N, the Capture process is restarted immediately after
stopping because it reached a limit. The default is N.
Sets the SCN value beyond which
Capture process becomes disabled. If set to INFINITE,
then the Capture process runs regardless of the SCN
value. The default is INFINITE.