SQL> alter system set LOG_ARCHIVE_DEST_2='SERVICE=destdb LGWR SYNC NOREGISTER
VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE)DB_UNIQUE_NAME=destdb' scope=both;
BEGIN
DBMS_STREAMS_ADM.MAINTAIN_SCHEMAS(
schema_names => 'tester',
source_directory_object => 'SOURCE_DIRECTORY',
destination_directory_object => 'DEST_DIRECTORY',
source_database => 'testdb.net',
destination_database => 'destdb.net',
perform_actions => true,
dump_file_name => 'export_tester.dmp',
capture_queue_table => 'rep_capture_queue_table',
capture_queue_name => 'rep_capture_queue',
capture_queue_user => NULL,
apply_queue_table => 'rep_dest_queue_table',
apply_queue_name => 'rep_dest_queue',
apply_queue_user => NULL,
capture_name => 'capture_tester',
propagation_name => 'prop_tester',
apply_name => 'apply_tester',
log_file => 'export_tester.clg',
bi_directional => false,
include_ddl => true,
instantiation => DBMS_STREAMS_ADM.INSTANTIATION_SCHEMA);
END;
/
BEGIN
DBMS_CAPTURE_ADM.SET_PARAMETER(
capture_name => 'capture_tester',
parameter => 'downstream_real_time_mine',
value => 'y');
END;
/
SQL> select propagation_name,status from dba_propagation;
PROPAGATION_NAME
STATUS
------------------------------ --------
PROP_TESTER
ENABLED
SQL> select capture_name,status from dba_capture;
CAPTURE_NAME
STATUS
------------------------------ --------
CAPTURE_TESTER
ENABLED
SQL> select apply_name,status from dba_apply;
APPLY_NAME
STATUS
------------------------------ --------
APPLY_TESTER
ENABLED
SQL> show parameter _job_queue_interval
NAME
TYPEVALUE
------------------------------------ ----------- ------------------------------
_job_queue_interval
integer 1
SQL>
SQL>
SQL> show parameter aq_tm_processes
NAME
TYPEVALUE
------------------------------------ ----------- ------------------------------
aq_tm_processes
integer 1
SQL>
SQL> select * from dba_apply_error;
no rows selected
SQL> select * from v$buffered_queues;
QUEUE_ID QUEUE_SCHEMA
QUEUE_NAME STARTUP_TIME NUM_MSGS SPILL_MSGSCNUM_MSGS CSPILL_MSGS EXPIRED_MSGS
---------- ------------------------------ ------------------------------------------ ---------- ---------- ---------- ----------- ------------
51951 STRMADM
REP_DEST_QUEUE 06-MAR-09
6
6
6 6
0
51817 STRMADM
REP_CAPTURE_QUEUE 06-MAR-09
37
3 37 3
0
SQL> select status, error from v$archive_dest;
STATUSERROR
--------- -----------------------------------------------------------------
VALID
VALID
INACTIVE
INACTIVE
INACTIVE
INACTIVE
INACTIVE
INACTIVE
INACTIVE
INACTIVE
10 rows selected.
SQL>
SQL> select capture_name,state from V$STREAMS_CAPTURE;
CAPTURE_NAMESTATE
--------------------------------------------------------------------------------------------------------------
CAPTURE_TESTERCAPTURING CHANGES
SQL>
The following Capture process states are possible:
INITIALIZING: The process is starting up.
WAITING FOR DICTIONARY REDO – The process is waiting for redo log files containing the dictionary build related to the first SCN to be added to the Capture process session. A Capture process cannot begin to scan the redo log files until all of the log files containing the dictionary build have been added.
DICTIONARY INITIALIZATION – The process is processing a dictionary build.
MINING – The process is mining a dictionary build at the SCN shown in the message.
LOADING – The process is processing information from a dictionary build.
CAPTURING CHANGES – The process is scanning the redo log for changes that evaluate to TRUE against the Capture process rule sets.
WAITING FOR REDO – The process is waiting for new redo log files to be added to the Capture process session. This message is shown when the Capture process has finished processing the entire redo log files added to its session. This indicates that there is no activity at a source database. For a downstream Capture process, this state is possible if the Capture process is waiting for new log files to be added to its session.
EVALUATING RULE – The process is evaluating a change against a Capture process rule set.
CREATING LCR – The process is converting a change into an LCR.
配置脚本执行都正常，propagation/capture/apply各进程的状态都是正常的，数据就是过不去奇怪，
哪位老兄知道什么原因吗？
谢谢
|
