Scheduling dbutility Updates

The dbutility process command has a built-in scheduling mechanism that allows the run to hibernate and resume at the next scheduled time. When the Server sends the Client an end-of-audit-reached status, dbutility normally terminates. However, if you enable scheduling, dbutility disconnects from the server and the database and hibernates until the next scheduled process command, when it reconnects to the server and the database. This scheduling mechanism only works after you run dbutility for the initial clone of the DMSII database. If the Client crashes or the poser fails, scheduling will fail. Service-based scheduling has none of these shortcomings, as the scheduling task is taken over by the service. For details about service-based scheduling, see the DATABridge Client Console Help.

To schedule updates

  1. Uncomment the scheduling parameters in the DATABridge Client configuration file. Scheduling parameters are listed under the [Scheduling] header in the configuration file.
  2. Select one of the following scheduling methods:
    • Daily scheduling
    • Fixed-delay scheduling
  3. Enter appropriate values for the following scheduling parameters, depending on whether you are using daily scheduling or fixed-delay scheduling. Each parameter is explained in [Scheduling].



    ; dbutility process command only


    ;daily = 08:00, 12:00, 17:00, 24:00

    ;exit_on_error = false

    ;sched_delay_secs = 600

    ;sched_minwait_secs = 3600

    ;sched_retry_secs = 3600

    As long as the process command completes successfully, dbutility becomes inactive (sleep) until the next scheduled time. If the scheduled dbutility process command is successful, the following message appears:

    Next update for DataSource datasourcename will run at hh:mm (delay = nn secs)

    Scheduling of updates will continue until any of the following occurs:

    • You reboot the DATABridge Client machine or end the DATABridge Client session
    • You enter a SCHED OFF console command when dbutility is processing updates
    • A DMSII reorganization (other than a garbage collection)

      Note: If you must stop the dbutility program, it is recommended that you use the QUIT command to exit at the next quiet point. You can also press Ctrl+C, preferably while dbutility is inactive. Pressing Ctrl+C or terminating the session while dbutility is processing updates stops the dbutility process command immediately, even if it is in the middle of a transaction group, and is not recommended.