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.
| Section |
|---|
| Column | ||
|---|---|---|
| ||
|
| width | 95% |
|---|
| bgColor | CCC |
|---|
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:
| Section |
|---|
| Column | ||
|---|---|---|
| ||
|
| width | 95% |
|---|
| bgColor | CCC |
|---|
dbvrep> create service mine
On Linux/Unix:
...
| Column | ||
|---|---|---|
| ||
|
...
| width | 95% |
|---|
...
Start the Dbvisit Replicate executable with a DDC file and start the MINE as a daemon process:
| No Format | ||
|---|---|---|
| ||
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. This option is not available on Windows, as similar functionality will be provided by support of Windows services.
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
| Note |
|---|
The Dbvisit Replicate setup wizard creates the necessary scripts for starting the replication apply APPLY process, so the actual commands dbvrep command listed here are not required and are information purposes only. The script names to start the apply APPLY process are listed in the Nextsteps.txt file created by the setup wizard. |
On Windows:
Start the Command Console with the DDC file.
On Windows, the Dbvisit Replicate can be started as a local service.
| Section |
|---|
| Column | ||
|---|---|---|
| ||
|
| width | 95% |
|---|
| bgColor | CCC |
|---|
dbvrep> start_service applyAPPLY
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:
| Sectionnoformat | ||||
|---|---|---|---|---|
| width | 5%
| ||
dbvrep> create service apply |
...
| width | 95% |
|---|
...
On Linux/Unix:
Start the Dbvisit Replicate executable with a DDC file and start the APPLY as a daemon process:
| No Format | ||
|---|---|---|
| ||
dbvrep> create service apply |
On Linux/Unix:
| Section | ||||||
|---|---|---|---|---|---|---|
Column | | |||||
|
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.
| Note |
|---|
When restarting the MINE process after the MINE process has been stopped for some time, there maybe some additional work required by the MINE process internally before the replication is up to date again. Please see Restarting MINE Process for more information. |
Starting the fetcher process
| Note |
|---|
The Dbvisit Replicate setup wizard creates the necessary scripts for starting the replication fetcher process, so the actual dbvrep command 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 Command Console with the DDC file.
On Windows, the Dbvisit Replicate can be started as a local service.
| No Format | ||
|---|---|---|
| ||
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:
| No Format | ||
|---|---|---|
| ||
dbvrep> create service fetcher |
On Linux/Unix:
Start the Dbvisit Replicate executable with a DDC file and start the fetcher as a daemon process:
| No Format | ||
|---|---|---|
| ||
dbvrep --ddcfile w112a.ddc –-daemon start applyfetcher |
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:
| Section |
|---|
| Column | ||
|---|---|---|
| ||
|
| width | 95% |
|---|
| bgColor | CCC |
|---|
dbvrep> shutdown all
This will stop all the replication processes including mineMINE, apply APPLY and fetcher (if started).
On Linux/Unix, the dbvrep process associated with the mine MINE, APPLY or apply fetcher can also stopped with a kill -9 command.
On Windows, the apply APPLY, MINE or mine 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.