Page Comparison

We are replicating a lot of tables (170) and we are not seeing the prompt in the Dbvisit Replicate console.

Even when the console is listing all the tables being replicated, the command prompt is still available. However, the table listing can be so long that the prompt cannot be seen. By default, 30 tables are listed for each replication, thus for a 2-way replication, it takes up to 70 screen lines.
To change this, edit the *-MINE.ddc file and add line "set STATUS_BAR_ACTIVE_TABLES 5". Or enter this command at the console prompt. Restart the console for this change to take affect.

...

Why does the mine process have to go back to previous logs when it restarts?

The mine process always has to go back to the start of the oldest active transaction. That is why on re-start the mine has to go back to a previous log (plog) when it restarts. Note that Dbvisit Replicate will never remove a plog that still has an active transaction.

...

How do we see the progress of the replication?

To asses how the replication is going, start the Dbvisit Replicate console. Then look at the first lines that display datetime, log sequence and SCN of the mine and apply processes. These numbers should be constantly updating as the replication is happening in real-time. 

The first time you start the replication, it starts at the time as of when the *-apply.sh script was run; on subsequent restarts, it needs to go back to the start of the oldest active transaction.

...

How is 2-way (active-active) replication different to 1-way replication?

...

-MINE IS running. Currently at plog 400 and SCN 5532051 (07/31/2012 12:53:29).
APPLY IS running. Currently at plog 400 and SCN 5519040 (07/31/2012 12:21:38)
APPLY1 IS running. Currently at plog 370 and SCN 5249942 (07/31/2012 12:53:34).
MINE1 IS running. Currently at plog 370 and SCN 5249944 (07/31/2012 12:53:35).

By default when commands are issues in the console it issues commands against process MINE and APPLY. To set the console to issue commands against MINE1 or APPLY1, issue the following command:

dbvrep> choose process mine1

...

What are the important commands to run when diagnosing Dbvisit Replicate?

The following commands should be run from the Dbvisit Replicate console:

• "HEALTHCHECK"
• "SHOW TYPE"
• "SHOW PEER"
• "SHOW INTERFACE"
• "SHOW UNIQUE_ID"

Check that the hostnames and database names resolve to correct targets on all machines involved.

...

How can I check on which interfaces Dbvisit Replicate is listening?

Run the following command in the Dbvisit Replicate console:

"SHOW INTERFACE"

...

Our source is Oracle on Linux and our target is Microsoft SQL Server. Do we need a Linux Microsoft SQL Server ODBC driver on the source Linux server? Can we use the FETCHER process to avoid the Linux ODBC driver?

 The Mine process does not connect to the target database and thus does not need any ODBC drivers for Linux. So you do not need the FETCHER process. Apply is usually running locally with the database, and because that is Windows and it is a local MSSQL connection so that will work.
Dbvisit Replicate Console needs to connect to both MINE and APPLY, so it will need an ODBC connection. The simple solution is to run the console on the target server and you will not need an Linux MSSQL ODBC driver.