Working with files needing attention - assure_mimix - 10.0

The DB Errors column on the Work with Data Groups display identifies the number of errors for user journal replication. Specifically, this column identifies the sum of the number of database files, IFS, *DTAARA, and *DTAQ objects that are on hold due to errors (*HLDERR) or have failed recoveries, plus the number of LF and PF files that have access path maintenance failures for a data group. Data group file entries and tracking entries should not be left in *HLDERR state for any extended time. Access path maintenance errors occur when MIMIX could not change a file’s access path maintenance attribute back to immediate.

To access a list of files in error for a data group, do the following:

1. From the MIMIX Basic Main Menu select option 6 (Work with data groups) and press Enter.

2. The Work with Data Groups display appears. Type 12 (Files needing attention) next to the data group you want which has errors identified in the DB Errors column and press Enter.

   The Work with DG File Entries display appears with a list of file entries for the data group that have replication errors, access path maintenance errors, and failed recoveries.

3. Replication errors:.The initial view shows the current replication status of file entries. Any entry with a status of *HLD, *HLDERR, *HLDIGN or *HLDRLTD indicates that action is required. Do the following:

   1. Use Possible actions based on replication status of a file entry to identify choices based on the file entry status and Options for working with file entries from the Work with DG FIle Entries display to identify available options from this display.

      Note: MIMIX retains log spaces for file entries with these statuses so that the journal entries that are being held can be released and applied to the target system. File entries should not be left in these states for an extended period.

   2. If necessary, take action to prevent the error from happening again. Refer to the following topics:

      • Correcting file-level errors

      • Correcting record-level errors

4. Access path maintenance errors: Press F10 as needed on the Work with DG File entries display until you see the access path maintenance view. The AP Maint. Status column identifies any AP maintenance errors for a file with the value *FAILED and failures for logical files associated with a file as *FAILEDLF.

   Immediate action may not be necessary because MIMIX will attempt to retry access path maintenance when the data group ends and when it is restarted. To attempt an immediate retry, use option 40 (Retry AP maintenance).

5. Failed recoveries: Press F10 as needed on the Work with DG File entries display until you see the Recovery Status column. This column identifies the most severe status of any recoveries for the object. Use option 17 (Rcy details) to go to the Work with Recoveries display where you can use available options for addressing failed recoveries. Different options are available for recoveries processed by replication manager and those processed inline by audits or third delay-retry activity. See Displaying recoveries.

   Table 1. Possible actions based on replication status of a file entry

   Status	Preferred Action1
   *ACTIVE	Unless an error has occurred, no action is necessary. Entries in the user journal for the file are replicated and applied. If necessary, any of the options to hold journal entries can be used.
   *HLD	User action is required to release the file entry (option 26) so that held journal entries from the user journal can be applied to the target system.
   *HLDERR	User action is required. Attempt to resolve the error by synchronizing the file (option 16). Note: Transactions and hold logs are discarded for file entries with a status of *HLDERR and an error code of IG. Such a file must be synchronized.
   *HLDIGN	User action is required to either synchronize the file (option 16) or to change the configuration if you no longer want to replicate the file. Journal entries for the file are discarded. Replication is not occurring and the file may not be synchronized. Depending on the circumstances, Release may also be an option.
   *HLDRGZ *HLDRNM *HLDPRM *HLDSYNC	These are transitional states that should resolve to *ACTIVE. If these status persist, check the journaling status for the entry. MIMIX retains log spaces for the held journal entries for the duration of these temporary hold requests.
   *HLDRTY	The file entry is held because an entry could not be applied due to a condition which required waiting on some other condition (such as in-use). After a short delay, the database apply job will automatically attempt to process this entry again. The preferred action is to allow MIMIX to periodically retry the file entry. By default, the database apply job will automatically attempt to process the entry every 5 minutes for up to 1 hour. Manually releasing the file entry will cause MIMIX to attempt to process the entry immediately. Note: From the Assure Unified Interface, you can view information about locks on the object on both systems. From the File Activity tab on the Data Group Details and Activities portlet, select the Compare Details action to view the Locks tab of the Compare Object Details from Nodes window.
   *HLDRLTD	User action is required for a file in the same network. View the related files (option 35). A file that is related due to a dependency, such as a constraint or a materialized query table, is held. Resolving the problem for the related held file will resolve this status.
   *RLSWAIT	The file is waiting to be released by the DB apply process and will be changed to *ACTIVE. If the status does not change to *ACTIVE, check the journaling status. If this status persists, you may need to synchronize (option 16).
   *CMPACT *CMPRLS *CMPRPR	These are transitional states that should resolve automatically. The file entry represents a member that is being processed cooperatively between the CMPFILDTA command and the database apply process.

   Note: Evaluate the cause of the problem before taking any action.