This content has been marked as final. Show 3 replies
From the following query you can identify whether the apply process applying the messages or not.
Latency_in_Seconds will give the latency between the event creation and apply time.
SELECT (APPLY_TIME-APPLIED_MESSAGE_CREATE_TIME)*86400 "Latency_in_Seconds",
TO_CHAR(APPLY_TIME,'HH24:MI:SS MM/DD/YY') "Apply_Time",
WHERE APPLY_NAME = <Apply_process_name> ;
Just Stop and Start the apply process again using following script :
--STOP THE APPLY PROCESS
DBMS_APPLY_ADM.stop_apply(apply_name => 'APPLY_STREAM');
--START THE APPLY PROCESS
DBMS_APPLY_ADM.START_APPLY(apply_name => 'APPLY_STREAM');
Then check the status of apply process in dba_apply .
You can also try any DML and see if everything is working fine .
I have faced this error, after I recreate my configuration, as I had missed my owne and it hadn't worked. So I had removed streamsconfiguration on apply side, but not removed the propagation.
I have disabled capture
next disabled propagation
then stopped apply porcess.
Removed the apply config (exec dbms_streams_adm.remove_streams_configuration(); + exec dbms_streams_adm.remove_queue(queue_name=>'<my applpyqueue>',cascade=>true,drop_unused_queue_table=>true);
Finally deleted the propagation as well. (I have one propagation for one target and it was my first config on target side.)
next I was following my config-steps well, and error has gone away.
Edited by: Lacko on Mar 22, 2012 11:51 AM