Step-4: Define the Rules for Capture
At the destination database, either
instantiate or set the instantiation SCN for each database
object added to the Streams environment. In case the database
objects do not exist at a destination database, instantiate them
using export/import, transportable tablespaces, or RMAN. In the
case of database objects being present at the destination
database, set the instantiation SCNs for them manually.
In order to set the instantiation SCN for a
table manually, run the procedure set_table_instantiation_scn
procedure in the dbms_apply_adm package at a destination
database. Finally, the Streams process that was stopped earlier
must be started or enabled.
To start the Streams process:
-
Use the start_capture procedure in
the dbms_capture_adm package to start a Capture process.
-
Use the enable_propagation_schedule
procedure in the dbms_aqadm package to enable a
propagation job.
-
Use the start_apply procedure in the
dbms_apply_adm package to start an Apply process.
So far, the basic configurations of the
Capture and Propagation processes have been presented. The next
step is to see how to manage them and how to understand
different attributes for those processes
Capture Process States
The state of a Capture process describes
what the Capture process is doing currently. The state of a
Capture process can be viewed by querying the STATE column in
the v$streams_capture dynamic performance view. This is a
useful piece of information to monitor in the Capture process.
For example, the state PAUSED FOR FLOW CONTROL reveals that
there are some bottlenecks in the Capture process. Typically,
the state should be CAPTURING CHANGES.
