Processing - DBEngine and DBEnterprise
Most of the options in this section allow the Client to override the configured values of the corresponding parameters in the Engine control file.
Configuration file parameters are included below with the
DBEngine (Extract) workers (1 minimum to 10 maximum)
This option overrides the DBEngine WORKERS=n parameter on the host, which controls the number of extract workers the Databridge Engine can use during the data extraction phase.
Convert reversals to updates
The buttons Use server setting, Don't convert, and Convert allow the Client to override the Databridge Engine control file parameter CONVERT REVERSALS. Refer to the Databridge Host Administrator's Guide for more information on this parameter.
Enable DOC records (for debugging only)
This option, when enabled, requests DOC records from the Databridge Engine (DBEngine or Enterprise Server). Use this option only for troubleshooting Databridge Engine problems.
Include latest StateInfo in record headers
This option, when enabled, requests StateInfo in all data records sent by the server during audit file processing. If the DMSII audit file records have an associated timestamp, this option can result in more accurate audit timestamp values.
Enterprise Server audit file origin
This option, when enabled, specifies the expected origin for Enterprise Server audit files during normal operations. Options include: Cached, Direct disk, and Indirect disk.
Use these options to override Databridge Engine CHECKPOINT FREQUENCY parameters.
Every (n) BLOCKS (0 minimum to 200000 maximum)
commit_absn_inc (0 minimum to 200000 maximum)
Specify a value to override the Databridge Engine CHECKPOINT CLIENT EVERY nnn AUDIT BLOCKS parameter setting. The Databridge Engine will generate a commit at the next quiet point after the specified number of audit blocks have been processed since the last commit.
Every (n) UPDATES (0 minimum to 200000 maximum)
Specify a value to override the Databridge Engine CHECKPOINT CLIENT EVERY nnn UPDATE RECORDS parameter setting. The Databridge Engine will generate a commit at the next quiet point after the specified number of updates have been processed since the last commit.
Every (n) SECONDS (0 minimum to 300 maximum)
Specify a value to override the Databridge Engine CHECKPOINT EVERY nnn SECONDS parameter setting. The Databridge Engine will generate a commit at the next quiet point after the audit timestamp has moved by specified number of seconds since the last commit.
Commit during long transactions
To have the Client override the Databridge Engine CHECKPOINT LONG TRANSACTIONS parameter at the start of a process command, select either Enable (to set the parameter to True) or Disable (to set the parameter to False). If you don't want the Client to override the parameter, select Use server setting.
Commit during idle database
This option allows the Databridge Client to override the Databridge Engine COMMIT DURING IDLE DATABASE parameter setting in the Engine's control file. Select either Enable (to set the parameter to True) or Disable (to set the parameter to False). If you don't want the Client to override the parameter, select Use server setting.
Batch commit parameters
Batch job (start time, end time)
This option specifies the block of time during which batch jobs typically run. For example "22:00, 01:00" indicates that batch jobs run between 10:00 pm and 1:00 am. The syntax for the four commit checkpoint parameters, that can be overridden by the client, was modified to allow an optional second value to be specified. The second value represents the alternate value to be used during the batch period. The client was then modified to implement the automatic switching of commit parameters between the two periods. The switching is based on the value of the audit time stamp rather than the time when the client is run.
When you enable the Batch job (start time, end time) option two time input fields and a group labeled Commit frequency become visible below the enabled option. Use the input fields to set the batch period times and set the commit frequency parameter value for the batch period using the control in the Commit frequency group. You do not need to set all four Commit Frequency options as the disabled options will honor the value in the Engine control file.