Streams Replication 10.2.0.4 (source) and 11.1.0.6 (Destination)

Question

I am testing streams based replication between 10204 and 11106 databases. The destination db was down for a while (>10+hours) and after the destination db was brought up, I don't see the changes getting applied on the destination database. I don't see any apply errors. I have restarted the capture, propagation, and apply processes but still don't see the changes applied on the destination database. I am unable to troubleshoot any further. Since this is a test, I can do a reinstantiation but it would help me understand what went wrong in this case. I can provide any SQL output which you can use to help me.

Answer 1

What is the order you have restarted the streams.
Please follow the below order.
--On Source - Stop the capture process
exec dbms_capture_adm.stop_capture(capture_name => '<capture_name>');
--make sure it is stopped:
select capture_name, status from dba_capture;
-- On Destination - Stop the apply process:
exec dbms_apply_adm.stop_apply(apply_name => '<apply_name>');
-- Make sure it is stopped:
select apply_name, status from dba_apply;
-- On Source - Stop the propagation:
exec dbms_propagation_adm.stop_propagation(propagation_name => '<prop_name>');
-- Make sure it is stopped:
select propagation_name, status from dba_propagation;
-- On Source - Start the propagation:
exec dbms_propagation_adm.start_propagation(propagation_name => '<prop_name>');
--Make sure it has started:
select propagation_name, status from dba_propagation;
-- On Destination - Start the apply process:
exec dbms_apply_adm.start_apply(apply_name => '<apply_name>');
-- Make sure apply is started
select apply_name, status from dba_apply;
-- On Source - Start the capture process:
exec dbms_capture_adm.start_capture(capture_name => '<capture_name>');
-- Make sure capture is started
select capture_name, status from dba_capture;
Verify whether streams is working or not.