Stopping ProTop for Dictionary Changes

Stopping ProTop for Dictionary Changes

If you apply dictionary changes in single-user mode or use online schema changes, ProTop does not interfere and does not need to be stopped.

If the database is running in multi-user mode and you attempt to load a df from the data dictionary without checking the "Add new objects on-line" box, the ProTop agent, a regular 4GL client, will prevent exclusive access to the database schema.

In that case, you can pause ProTop using one of the following methods:

Schedule an Outage (Preferred)

Run the maintenance.sh (or .bat on Windows) script, using the "on" option and specify the number of hours for the outage:

bin/maintenance.sh on 2

This will disable ProTop for all of the resources on this server and create an Outage entry on the portal for these resources.

Manual Stop

If you prefer to control the stop and start of ProTop manually:

  1. Stop the ProTop service

    • For UNIX - comment out the dbmonitor cron job
    • For Windows - stop the Windows service
  2. Delete $PROTOP/tmp/*.flg. This stops all ProTop processes (dbmonitor and pt3agents).

Restart ProTop

When you finish your schema changes, re-enable ProTop by either:

  1. Restarting the ProTop Service if you stopped it manually or, by
  2. Ending the scheduled maintenance you created above by running:
    bin/maintenance.sh off

    This will allow the ProTop Service (dbmonitor) to restart monitoring for the resources on this server and deactivate the Outage entry on the (new) portal. On the current portal, you can let the outage expire if it has not already or manually deactivate the outage to re-enable the flow of alert emails.