• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 432
  • Last Modified:

replication is not working when i did DML opetation

Hello Experts,

i have a problem with replication (one way)

I created a one-way table replication using streams. The replication would propagate to the target database almost immediately whenever a DML change was made on the source table. I then tried to pause the replication by stopping the apply process at the target database. I then proceeded to insert rows into the source table; and then restarted the apply [ e.g., dbms_apply_adm.start_apply( STRMS_APPLY_HB ) ]. The Streams subsystem is no longer propgating DML changes to the target table.

Did I miss something thats preventing this replication from being paused?

can any one help me

0
pavan27
Asked:
pavan27
  • 3
2 Solutions
 
schwertnerCommented:
What is apply server doing. Check  V$STREAMS_APPLY_SERVER:

The state of an apply server describes what the apply server is doing currently. You can view the state of each apply server for an apply process by querying the V$STREAMS_APPLY_SERVER dynamic performance view. The following apply server states are possible:

IDLE - Performing no work
RECORD LOW-WATERMARK - Performing an administrative action that maintains information about the apply progress, which is used in the ALL_APPLY_PROGRESS and DBA_APPLY_PROGRESS data dictionary views
ADD PARTITION - Performing an administrative action that adds a partition that is used for recording information about in-progress transactions
DROP PARTITION - Performing an administrative action that drops a partition that was used to record information about in-progress transactions
EXECUTE TRANSACTION - Applying a transaction
WAIT COMMIT - Waiting to commit a transaction until all other transactions with a lower commit SCN are applied. This state is possible only if the COMMIT_SERIALIZATION apply process parameter is set to a value other than none and the PARALELLISM apply process parameter is set to a value greater than 1.
WAIT DEPENDENCY - Waiting to apply an LCR in a transaction until another transaction, on which it has a dependency, is applied. This state is possible only if the PARALELLISM apply process parameter is set to a value greater than 1.
WAIT FOR NEXT CHUNK - Waiting for the next set of LCRs for a large transaction
TRANSACTION CLEANUP - Cleaning up an applied transaction, which includes removing LCRs from the apply process queue
0
 
schwertnerCommented:
To find out the state of the capture process:

 

select state from v$streams_capture;

 

STATE

---------------------------------

CAPTURING CHANGES

 

 

 

To find out total number of messages propagated on sending side:

select total_msgs from v$propagation_sender

 

TOTAL_MSGS

--------------------

15863766

 

 

To find out what is the state of apply reader:

select state from v$streams_apply_reader;

STATE

--------------

SPILLING

 

0
 
schwertnerCommented:
Good luck!
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Cloud Class® Course: CompTIA Healthcare IT Tech

This course will help prep you to earn the CompTIA Healthcare IT Technician certification showing that you have the knowledge and skills needed to succeed in installing, managing, and troubleshooting IT systems in medical and clinical settings.

  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now