Identifying and resolving problems reflected in the Data Group column - assure_mimix - 10.0

Assure MIMIX Operations Guide

Product type
Software
Portfolio
Integrate
Product family
Assure
Product
Assure MIMIX™ Software
Version
10.0
Language
English
Product name
Assure MIMIX
Title
Assure MIMIX Operations Guide
Copyright
2023
First publish date
1999
Last updated
2024-03-12
Published on
2024-03-12T11:06:36.794496

When a data group name is highlighted in color, journaling problems exist that affect replication of one or more types of data.

Table 1. Conditions which highlight the data group name in color.

Color

Possible Problems

Red 

One of the following conditions exists:

  • Files, IFS tracking entries, or object tracking entries defined to the data group are not journaled or are journaled to a different journal than the configured journal on the source system.
  • The source side journal is in standby or inactive state.

Yellow 

One of the following conditions exists:

  • Files, IFS tracking entries, or object tracking entries defined to the data group are not journaled or are journaled to a different journal than the configured journal on the target system. This is only enforced if the data group is set up to journal on the target system as defined in the data group definition.
  • Data group file entries, IFS tracking entries, or object tracking entries are on hold for reasons other than an error.
  • The journal cache value for the source journal does not match the configured value in the journal definition.
  • The journal cache value for the target journal does not match the expected cache value and the database apply session is active. If another data group is using the journal definition as a source journal, the actual journal cache value may be different than the configured value.
  • The target journal state value for the target journal does not does not match the expected state value and the database apply session is active. If another data group is using the journal definition as a source journal, the actual state may be different than the configured value.
  • The recovery policies are disabled due to a recent unplanned switch.
  • A switch occurred and there are replicated jobs remaining on the current source system. Use Working with replicated jobs to evaluate these replicated jobs and either submit or remove them.
Note: In a cooperative processing environment, files, IFS tracking entries, or object tracking entries being added dynamically to the configuration for user journal replication may reflect an intermediate state of not journaled until they have been synchronized and become active to MIMIX.