i need to understand more on scenerio one:
doubt 1). rep agent can be down : in what cases rep agent can be down because rep agent task is to read the transaction log of primary database and pass the marked transaction to primary rep server.
doubt 2) how to check if rep agent is working nicely , how to check sec truncation point is moving and is catching up with tran log moving.
doubt 3) how to check stable queue space and how to check sizes of inbound.outbound etc queues.
Thanks in advance
Main Topics
Browse All Topics
by: alpmoonPosted on 2009-08-28 at 00:01:57ID: 25205488
Two scenarios are critical:
1. If rep agent is down or stable queue space is full and replication server cannot write into inbound queue, secondary truncation point doesn't move. It means dump database cannot clear space in transaction log. You need scripts for regular check so that replication system is up running and free stable queue space is OK.
2. Depending on the version and your configuration, the transaction log space required to apply a big transaction might be much larger in the replicate site. Let's say if you update one million rows in primary database with one update statement, that update is normally replicated as one million update statements. It consumes more transaction log space and may not fit into available space. In a replicated database, smaller transactions are always better.
I think you should check how truncation marker, rs_zeroltm, secondary trunc point, rep agent etc. are working in Repserver manuals. Then ask specific questions.