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 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 Dbvisit Replicate 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
The Dbvisit Replicate setup wizard creates the necessary scripts for starting the replication apply process, so the actual commands listed here are not required and are information purposes only. The script names to start the apply process are listed in the Nextsteps.txt file created by the setup wizard. |
On Windows:
Start the Dbvisit Replicate 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
The Dbvisit Replicate setup wizard creates the necessary scripts for starting the replication fetcher process, so the actual commands listed here are not required and are information purposes only. The script names to start the apply process are listed in the Nextsteps.txt file created by the setup wizard. |
On Windows:
Start the Dbvisit Replicate 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:
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.