Locking members during apply - 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-06-11
ft:lastPublication
2024-06-11T18:33:16.692940

A MIMIX configuration option determines the type of lock that the database apply (DBAPY) processes obtain on file members being processed on the target node. The type of lock obtained by MIMIX affects the type of lock that can be obtained by other applications on the target node. Database apply processing will also lock objects as needed to replicate changes from the source node.

The type of lock obtained by MIMIX depends on whether the data group uses multithreaded or single-threaded database apply processing when processing files.

  • For data groups associated with a resource group configured for multithreading, the Lock member during apply configuration option is set to Do Not Lock (*NONE). This value cannot be changed. The database apply process does not hold a lock on file members on the target node. If your environment requires locking for business reasons, the resource group cannot be configured for multithreaded database apply processing.

  • For all single-threaded data groups, the shipped default value for the Lock member during apply configuration option is Exclusive, Allow Read (*EXCLRD). The database apply process holds an *EXCLRD lock on file members being processed on the target node, which allows other users read-only access to the data. Members are locked only when the apply process is started. Locking affects members whose file activity status is active.

In configurations that allow locking, you can change the type of locking used. For more information, see Changing target side locking for DBAPY processes.