Start/Stop Replication

Starting the MINE process

The Dbvisit Replicate setup wizard creates the necessary scripts for starting the replication MINE process, so the actual dbvrep commands listed here are not required and are for information purposes only. The script names to start the MINE process are listed in the Nextsteps.txt file created by the setup wizard. The script names will have the word run and will contain the server name on which to run the actual script.

Example:
d112f-run-dbvisit210.sh

Where:

• d112f is the DDC file name 
• dbvisit210 is the server name

On Windows:

Start the Command Console with the DDC file.

On Windows, the Dbvisit Replicate can be started as a local service.

dbvrep> start_service mine

This starts the Windows service. The service can also be started from the Windows service control panel.

If the service is not yet created, the service can be created with:

dbvrep> create service mine

On Linux/Unix

Start the Dbvisit Replicate executable with a DDC file and start the MINE as a daemon process:

dbvrep --ddcfile w112a.ddc --daemon start mine

The –daemon option makes dbvrep disconnect from the console and run in the background. No further commands can be entered. 
To see the progress of the replication, start a new Dbvisit Replicate Command Console and load the same DDC file. See Viewing the status of the replication for more information.

Starting the APPLY process

On Windows:

Start the Command Console with the DDC file.

On Windows, the Dbvisit Replicate can be started as a local service.

dbvrep> start_service APPLY

This starts the Windows service. The service can also be started from the Windows service control panel.

If the service is not yet created, the service can be created with:

dbvrep> create service apply

On Linux/Unix:

Start the Dbvisit Replicate executable with a DDC file and start the APPLY as a daemon process:

dbvrep --ddcfile w112a.ddc --daemon start apply

The –daemon option makes dbvrep disconnect from the console and run in the background. No further commands can be entered.
To see the progress of the replication, start a new Dbvisit Replicate Command Console and load the same DDC file. See Viewing the status of the replication for more information.

Starting the fetcher process

On Windows:

Start the Command Console with the DDC file.

On Windows, the Dbvisit Replicate can be started as a local service.

dbvrep> start_service fetcher

This starts the Windows service. The service can also be started from the Windows service control panel.

If the service is not yet created, the service can be created with:

dbvrep> create service fetcher

On Linux/Unix:

Start the Dbvisit Replicate executable with a DDC file and start the fetcher as a daemon process:

dbvrep --ddcfile w112a.ddc --daemon start fetcher

The –daemon option makes dbvrep disconnect from the console and run in the background. No further commands can be entered.
To see the progress of the replication, start a new Dbvisit Replicate Command Console and load the same DDC file. See Viewing the status of the replication for more information.

Stopping the replication process

To stop or shutdown the replication process:

dbvrep> shutdown all

This will stop all the replication processes including MINE, APPLY and fetcher (if started).

On Linux/Unix, the dbvrep process associated with the MINE, APPLY or fetcher can also stopped with a kill -9 command. 

On Windows, the APPLY, MINE or fetcher process can be also stopped by shutdown the associated Windows service.

It is always a good idea to ensure that there are no connections active for the user 'dbvrep' in either database before restarting MINE and APPLY. If any sessions after shutting down all do exist, kill the oracle session before restarting.