Restarting Dbvisit Standby components - Dbvnet and Dbvserver

Owned by Anton Els (Deactivated)
Last updated: Mar 03, 2014

Restarting Dbvisit Standby software stack (Dbvnet and Dbvserver)


It is recommended that when you perform a restart of the full stack (Dbvnet and Dbvserver) that you perform them in the following order.

Important

Dbvnet must be running on both primary and standby servers to allow Dbvisit Standby version 7 to communicate and transfer files between the two nodes. 

It is recommended that you ensure your Dbvisit Schedules are stopped when performing a restart of the Dbvisit Standby stack (Dbvserver and Dbvnet). This include disabling cron schedules if they are used.


Step 1:  Stop Dbvserver (Dbvisit Standby Web Based Interface)

The following command is executed to stop the Dbvserver process.  (note the stop command does not return any output and once executed you will be returned to a new line)

cd  /usr/dbvisit/dbvserver
./dbvserverd stop


Step 2:  Stop Dbvnet (Dbvisit Standby Network Communication)

The following command is executed to stop the Dbvserver process.  (note the stop command does not return any output and once executed you will be returned to a new line)

cd /usr/dbvisit/dbvnet
./dbvnetd stop

Once you have stopped Dbvserver and Dbvnet, please ensure there are no other dbvnet or dbvserver processes still running, before you continue with the next step. This can be done by reviewing the running processes with the command: ps -ef|egrep "dbvnet|dbvserver" |grep -v grep

If there are processes running, please ensure you have executed the above commands correct and if so, then remove these processes by using the Unix kill command with the process ID of the process you want to kill. Be careful when performing these tasks (using the kill command) and make sure you specify the correct process ID's.

 

Step 3:  Clear all temporary cache (temp files)

Dbvisit Standby does generate temporary cache files in the default TEMP location, which on most systems will be "/tmp".

Before starting the Dbvnet and Dbvserver components, it is recommended to clear these directories listed below if they do exist:

  • /tmp/par-*
  • /tmp/dbvtmp-*
  • /tmp/p2xtmp-*
  • /tmp/pdk-*

The following example commands can be used to remove these directories:

 
rm -Rf /tmp/par-* 
rm -Rf /tmp/dbvtmp-* 
rm -Rf /tmp/p2xtmp-*
rm -Rf /tmp/pdk-*

 

Step 4:  Start Dbvnet (Dbvisit Standby Web Based Interface)

The following command is executed to start the dbvnet process.  (note the start command does not return any output and once executed you will be returned to a new line)

The example below also removes old log files from the log directory.

cd  /usr/dbvisit/dbvnet
rm log/*
./dbvnetd start

 

Step 5:  Start Dbvserver (Dbvisit Standby Network Communication)

The following command is executed to start the Dbvserver process.  (note the start command does not return any output and once executed you will be returned to a new line)

The example below also removes old log files from the log directory.

cd /usr/dbvisit/dbvserver
rm log/*
./dbvserverd start


Step 6:  Review processes are running

The final step is to confirm that Dbvnet and Dbvserver are running.

This can be done by reviewing the running processes with the command: ps -ef|egrep "dbvnet|dbvserver" |grep -v grep

Example:

 

oracle@dbvlin101[/usr/dbvisit/dbvserver]: ps -ef|egrep "dbvnet|dbvserver" |grep -v grep
oracle    6142     1  0 Mar03 pts/3    00:00:02 ./dbvnetd start
oracle    6144  6142  0 Mar03 pts/3    00:00:00 ./dbvnetd start
oracle    6145  6142  0 Mar03 pts/3    00:00:00 ./dbvnetd start
oracle    6146  6142  0 Mar03 pts/3    00:00:00 ./dbvnetd start
oracle    6147  6142  0 Mar03 pts/3    00:00:00 ./dbvnetd start
oracle    6154     1  0 Mar03 pts/3    00:00:02 ./dbvserverd start
oracle    6155  6154  0 Mar03 pts/3    00:00:00 ./dbvserverd start
oracle    6157  6154  0 Mar03 pts/3    00:00:10 ./dbvserverd start
oracle    6159  6154  0 Mar03 pts/3    00:00:02 ./dbvserverd start

 

Stop/Start Troubleshooting Tips

Once you have started Dbvnet and Dbvserver you should be able to use the Web Based GUI as well as the network communication should be possible between the primary and standby servers.

For Dbvnet troubleshooting and testing tips, please see here

For Dbvserver, please make sure that there is no firewall blocking your connection to the default port 8443.  If you are using Linux IPTables, please make sure this port is open (review as root user the output of: "iptables -L" command and your configuration in /etc/sysconfig/iptables)

Â