We're here to help!

This Article explains the  best practice of how to schedule the dbv process on primary RAC nodes (oraprd1, oraprd2) as well as on the DR box (droraprd1). Below setup uses a script to run the dbvisit , is it recommended?

oraprd2:

10,25,40,55 0-23 * * 0-6 bash -c . .bash_profile && -usr-local-dbvisit-standby-dbvisit db1 > -dev-null 2>&1
10,25,40,55 0-23 * * 0-6 bash -c . .bash_profile && -usr-local-dbvisit-standby-dbvisit db2 > -dev-null 2>&1
10,25,40,55 0-23 * * 0-6 bash -c . .bash_profile && -usr-local-dbvisit-standby-dbvisit db3 > -dev-null 2>&1
10,25,40,55 0-23 * * 0-6 bash -c . .bash_profile && -usr-local-dbvisit-standby-dbvisit db4 > -dev-null 2>&1
10,25,40,55 0-23 * * 0-6 bash -c . .bash_profile && -usr-local-dbvisit-standby-dbvisit db5 > -dev-null 2>&1
10,25,40,55 0-23 * * 0-6 bash -c . .bash_profile && -usr-local-dbvisit-standby-dbvisit db6 > -dev-null 2>&1

oraprd1:

10,25,40,55 0-23 * * 0-6 bash -c . .bash_profile && -usr-local-dbvisit-standby-dbvisit db1 > -dev-null 2>&1
10,25,40,55 0-23 * * 0-6 bash -c . .bash_profile && -usr-local-dbvisit-standby-dbvisit db2 > -dev-null 2>&1
10,25,40,55 0-23 * * 0-6 bash -c . .bash_profile && -usr-local-dbvisit-standby-dbvisit db3 > -dev-null 2>&1
10,25,40,55 0-23 * * 0-6 bash -c . .bash_profile && -usr-local-dbvisit-standby-dbvisit db4 > -dev-null 2>&1
10,25,40,55 0-23 * * 0-6 bash -c . .bash_profile && -usr-local-dbvisit-standby-dbvisit db5 > -dev-null 2>&1
10,25,40,55 0-23 * * 0-6 bash -c . .bash_profile && -usr-local-dbvisit-standby-dbvisit db6 > -dev-null 2>&1

Should I be scheduling these in parallel as I am doing, or create a execution script to execute in a serial manner? i.e.

cat exec_dbvisit.sh

Execute dbvisit in sequence:

-usr-local-dbvisit-standby-dbvisit db1
-usr-local-dbvisit-standby-dbvisit db2
-usr-local-dbvisit-standby-dbvisit db3
-usr-local-dbvisit-standby-dbvisit db4
-usr-local-dbvisit-standby-dbvisit db5
...
...
... 12 DBs total

The main concern in the above script is that  Dbvisit Standby processes exits abnormally the script will exit without executing any of the following executions. 

Our recommendation would be that to schedule the dbvisit process based on the version you use.

Below link clearly provide us with details on the scheduling.

Version 6.0

https://dbvisit.atlassian.net/wiki/pages/viewpage.action?pageId=591134

Version 7.0

https://dbvisit.atlassian.net/wiki/display/UGDS7/Dbvisit+Standby+Scheduling

Version 8.0

https://dbvisit.atlassian.net/wiki/display/DS8QSG/Dbvisit+Standby+Scheduling

Mike Donovan July 05, 2013 15:15