Immediately applying committed transactions - assure_mimix - 10.0

Assure MIMIX Administrator Reference

Product type
Software
Portfolio
Integrate
Product family
Assure
Product
Assure MIMIX™ Software
Version
10.0
Language
English
Product name
Assure MIMIX
Title
Assure MIMIX Administrator Reference
Copyright
2023
First publish date
1999
ft:lastEdition
2024-05-07
ft:lastPublication
2024-05-07T13:36:02.962500

This topic applies to data groups that are configured for single-threaded database apply processing (the NBRDBAPY parameter specifies a numeric value).

In user journal replication, when commitment control is used on a source system, MIMIX supports two modes of applying transactions under commitment control: immediate apply and delayed apply on the target system.

In a data group definition, the value specified for the Commit mode element of the Database apply processing (DBAPYPRC) parameter determines how the apply process will handle journal entries that are under commitment control. Supported values are *DLY and *IMMED. Commit mode values and processing are described in Processing of transactions under commitment control.

Note: Immediate commit mode is required for data groups configured for multithreaded database apply processing. Shipped default values for new data groups automatically use immediate apply for the commit mode. Existing data groups associated with a resource group are automatically converted to immediate commit mode when the resource group is converted to multithreaded database apply processing.

Considerations when choosing which commit mode to use include:

  • Does your environment have long-running commit cycles?

  • Does your environment use data on the target system for other activities such as running reports?

Long-running open commit cycles often occur when performing large clean-up operations, such as when deleting all entries older than a certain date. They can also occur when a user forgets to close a transaction for a length of time.