Requirements for keyed replication - 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

Single-threaded database apply processing - MIMIX supports keyed replication only in data groups that are configured for single-threaded database apply processing. Single-threading is indicated by a numeric value for the Number of DB apply sessions (NBRDBAPY) parameter.

Journal images - MIMIX may need to be configured so that both before and after images of the journal transaction are placed in the journal.

The Journal image element of the File and tracking entry options (FEOPT) parameter controls which journal images are placed in the journal. Default values result in only an after-image of the record. However, some configurations require both before-images and after-images. The Journal image value specified in the data group definition is in effect unless a different value is specified for the FEOPT parameter in a file entry or object entry.

It is recommended that you use the Journal image value of *BOTH whenever there are file entries with keyed replication to prevent before images from being filtered out by the database send process. If the unique key fields of the database file are updated by applications, you must use the value *BOTH.

Unique access path - At least one unique access path must exist for the file being replicated.The access path can be either part of the physical file itself or it can be defined in a logical file dependent on the physical file.

You can use the Verify Key Attributes (VFYKEYATR) command to determine whether a physical file is eligible for keyed replication. See Verifying key attributes.