Updating the DATABridge Data Tables

Updating is the process of applying the DMSII database changes to the DATABridge data tables in the relational database. Updating is different from cloning because only the changes, not all of the data, are sent to the DATABridge data tables.

You can update the DATABridge data tables after they have been cloned as long as they meet the following requirements:

• Each DATABridge data table you want to update has a unique index. If a table you want to update does not have a unique index, see Creating Indexes for Tables.
• The DMSII database has not been reorganized. If the DMSII database has been reorganized, see Reorganizations, Filler Substitutions, and Initializations.

You can update the DATABridge Client data tables by entering the dbutility process command each time you want the update to occur, or you can schedule the dbutility process command. How often you update the DATABridge tables depends on the following:

• How current you want the data to be. For time-critical information, you may want to update the DATABridge data tables several times a day.
• How often audit files are available on the host. If the DATABridge Host uses DATABridge Plus, the current audit file is always available to DBEngine and DBServer. You can run the Client continuously to ensure that the DATABridge data tables are kept up-to-date.
• If a closed audit file is not available on the host, you must wait until one is available. Or, if necessary, you can force an audit file to close and therefore be available by using the dbutility switchaudit command. Before you do this, it is recommended that you first check with the DMSII database administrator.
• In some cases, a closed audit file is not available because it has been copied to tape. In this instance, a host operator must mount the tape before the closed audit file can be made available to DATABridge.
• When an audit file is not available, the DATABridge Clients temporarily stop processing until the audit file is available.

  Note: If you do not update the relational database often, it might be more effective for you to reclone the DMSII data sets rather than update them. For example, if you are interested in weekend information only, and several audit files have been closed (and possibly moved to tape) during that time, recloning could be faster than updating.