Typically, file-level errors can be categorized as one of the following:
A problem with the configuration of files defined for replication.
A discrepancy in the file descriptions between the management and network systems
An operational error.
This topic identifies the most common file-level errors and measures that you can take to prevent the problem from recurring. See also Correcting record-level errors.
Once you diagnose and correct a file-level error, the problem rarely manifests itself again. Some of the most common file-level errors are:
Authority: The MIMIXOWN user profile defined in the MIMIX job description does not have authority to perform a function on the target system. You can prevent this problem by ensuring that the MIMIXOWN user profile has all object authority (*ALLOBJ). This guarantees that the user profile has all the necessary authority to run IBM i commands and has the ability to access the library and files on the management system. If you are attempting to replicate files that have protected rows or columns, or system-period temporal tables and their associated history tables, the MIMIXOWN user profile may not have been granted the necessary function usage. For more information about requirements for replicating files that use permissions or masks for row and column access control (RCAC), see the Assure MIMIX Administrator Reference book. For more information about the MIMIXOWN user profile and authority, see the License Manager for IBM i Products book.
Objects existence or corruption: MIMIX cannot run a function against a file on the target system because the file or a supporting object (such as logical files) does not exist or has become damaged. System security is the only way to prevent an object from being accidentally deleted from the target system. Make sure that only the correct personnel have the ability to remove objects from the target system where replicated data is applied. Also, ensure that application programs do not delete files on the target system when there are no apply sessions running.
MIMIX subsystem ended: If the MIMIX subsystem is ended in an immediate mode while MIMIX processes are still active, files may be placed in a “Held” status. This is a result of MIMIX being unable to complete a transaction normally. After MIMIX is restarted, you only need to release the affected files.