The ProTop scheduler configuration can instruct the DBMonitor process to execute tasks.
The configuration file follows basic Unix cron syntax, with the addition of the optional “[NOALERT]” modifier.
0 * * * 6 foreachdb.sh dbanalys.sh > ${PTTMP}/foreachdb_dbanal.err 2>&1 [NOALERT]
By default, an information (blue) alert is uploaded to the ProTop web portal when a scheduled process is executed. The addition of [NOALERT] parameter prevents that upload. Read the top of the scheduler.cfg file for more detail.
Note: If you do not already have a localized version, copy etc/schedule.cfg to etc/schedule.[*].cfg. e.g. etc/schedule.yourCustId.cfg or etc/schedule.yourServerName.cfg. Edit your localized file and not the original etc/schedule.cfg file, which is overwritten at each update of ProTop.
foreachdb.sh[bat]
As found in [PROTOPDIR]/etc/schedule.cfg, foreachdb.sh (example above) will execute the given command against databases listed in etc/dblist.cfg AND has the “monitor” flag set to “yes” AND and belongs to the current server.
It does not work with every ProTop script or batch file, i.e., hc.[sh|bat], so test and check the logs.
On Windows
If you want the ProTop Scheduler to run jobs in parallel, give each command a unique log file name. If you do not, subsequent commands attempting to use the same log file will fail.