| Table of Contents | ||
|---|---|---|
|
1. Linux
On Linux there are two methods of for start and stop: systemctl service and starting background process via nohup.
| Note |
|---|
Choose only one method from the two for your environment, do not combine them |
1.1 Systemctl Service
The advantage of having Dbvisit Standby Multiplatform components setup as systemctl services is that systemctl will automatically startup Dbvisit Standby Multiplatform components after server boot.
Directly after Installation of Dbvisit Standby Multiplatform is finished, you have the option to install systemctl service:
| Code Block |
|---|
$ sudo /usr/dbvisit/standbymp/bin/dbvagentmanager service install --user oracle
$ sudo /usr/dbvisit/standbymp/bin/dbvcontrol service install --user oracle |
Dbvisit will then create new dbavgentmanager systemctl service description:
| Code Block |
|---|
cat /etc/systemd/system/dbvagentmanager.service
cat /etc/systemd/system/dbvcontrol.service |
You can then use following commands to start or stop dbvagentmanager:
| Code Block |
|---|
sudo /usr/dbvisit/standbymp/bin/dbvagentmanager service start
sudo /usr/dbvisit/standbymp/bin/dbvagentmanager service stop
sudo /usr/dbvisit/standbymp/bin/dbvcontrol service start
sudo /usr/dbvisit/standbymp/bin/dbvcontrol service stop |
It is also possible to use directly systemctl (same goes for dbvcontrol):
| Code Block |
|---|
sudo systemctl start dbvagentmanager
sudo systemctl stop dbvagentmanager
sudo systemctl restart dbvagentmanager
sudo systemctl status dbvagentmanager
sudo systemctl start dbvcontrol
sudo systemctl stop dbvcontrol
sudo systemctl restart dbvcontrol
sudo systemctl status dbvcontrol |
For uninstalling the systemctl dbvagentmanager service from Linux OS we recommend to use following commands:
| Code Block |
|---|
sudo /usr/dbvisit/standbymp/bin/dbvagentmanager service stop
sudo /usr/dbvisit/standbymp/bin/dbvagentmanager service uninstall
sudo /usr/dbvisit/standbymp/bin/dbvcontrol service stop
sudo /usr/dbvisit/standbymp/bin/dbvcontrol service uninstall |
1.2 Background Process
| Note |
|---|
Never use root user for this method. |
If you don’t want to introduce additional complexity by setting up systemctl services, you can start Dbvisit Standby Multiplatform processes directly as oracle user. This is very fast method and can be used when troubleshooting. The disadvantage is that Dbvisit Standby Multiplatform processes will need to be started manually after server boot.
| Code Block |
|---|
nohup /usr/dbvisit/standbymp/bin/dbvagentmanager service run &
nohup /usr/dbvisit/standbymp/bin/dbvcontrol service run & |
There’s no stop command, you have to manually search & kill the dbvagentmanager/dbvcontrol process:
| Code Block |
|---|
$ ps -ef | grep dbvagentmanager | grep -v grep
oracle 17474 3630 1 15:29 pts/0 00:00:00 /usr/dbvisit/standbymp/bin/dbvagentmanager service run
$ kill 17474 |
2. Windows
On Windows you can easily control Dbvisit Standby Multiplatform components through services:
...
Services are created automatically during Dbvisit Standby Multiplatform installation. It is supported to set the startup type of the services to Automatic (Delayed) if required.
3. Oracle Grid Environments
On Oracle Grid environments there are specific steps for creating and starting Dbvisit Standby Multiplatform components services via crsctl cluster resource:
<TBD>
If you have only single node with Oracle grid (for example Oracle Database Appliance server) you can decide whether to use crsctl service, systemctl service or background process - all are supported.