KRC_failed_job A ClearCase scheduled job has failed. Run cleartool schedule -get -job job name or number to get more information about the failure. For information about specific types of job failures, see Technote 1228516 (Repeating scheduled job warning: ... is still running -- skipping scheduled execution) or Technote 1259944 (Job's task program is not installed -- skipping scheduled execution). The default configuration has the following SQL syntax:
*IF *SCAN KRC_JOBS.Status *EQ '0x' *AND *VALUE KRC_JOBS.Status *NE '0x0'
This situation is evaluated every 30 minutes.
KRC_updater The ClearCase updater has failed. The cache updater did not sucessfully complete execution. The default configuration has the following SQL syntax:
*IF *VALUE KRC_CACHE_UPDATER.status *EQ '1'
This situation is evaluated every 10 minutes.
KRC_updater_log The ClearCase updater has failed. The cache updater did not sucessfully complete execution. The default configuration has the following SQL syntax:
*IF *VALUE KRC_AGENT_ERRORS.Caller *EQ 'collector.bat'
This situation is evaluated every 1 hour.
KRC_rollback_info Replica being restored with restorereplica. This replica is being restored after recovery from backup media. Update requests have been sent to sibling replicas. The replica will remain locked until the updates are complete. The default configuration has the following SQL syntax:
*IF *VALUE KRC_EPOCH_ALL.Old_Epoch *GT KRC_EPOCH_ALL.Epoch *AND *VALUE KRC_EPOCH_ALL.In_restorereplica *EQ 1
This situation is evaluated every 1 hour.
KRC_rollback_warning Epoch rollback detected, VOB locked, not in restorereplica. Epoch rollback has been detected in a locked VOB. If the VOB is locked because it has been restored from backup, run multitool restorereplica before you unlock the VOB. You can optimize that process by naming the sibling to which this replica has most recently exported an update packet (see the sync history workspace). If the VOB has not been restored from backup, contact IBM Rational Support for assistance in determining if the VOB family has divergence. The default configuration has the following SQL syntax:
*IF *VALUE KRC_EPOCH_ALL.Old_Epoch *GT KRC_EPOCH_ALL.Epoch *AND *VALUE KRC_EPOCH_ALL.In_restorereplica *EQ 2 *AND *VALUE KRC_EPOCH_ALL.Is_Locked *EQ 1
This situation is evaluated every 1 hour.
KRC_rollback_critical Epoch rollback detected in a replica that is not locked. Epoch rollback has been detected. Lock this VOB immediately and check for divergence at this replica's siblings. If no divergence is found, run multitool restorereplica at this replica before unlocking it. The default configuration has the following SQL syntax:
*IF *VALUE KRC_EPOCH_ALL.Old_Epoch *GT KRC_EPOCH_ALL.Epoch *AND *VALUE KRC_EPOCH_ALL.In_restorereplica *EQ 2 *AND *VALUE KRC_EPOCH_ALL.Is_Locked *EQ 2
This situation is evaluated every 1 hour.
KRC_replica_f_level_low Replica feature level can be raised. The version of ClearCase on this host can support a higher replica feature level than the replica feature level that is currently set. Use the cleartool chflevel command to raise the replica feature level. When all replicas in the family are at the same feature level, use the chflevel command to raise the family feature level. The default configuration has the following SQL syntax:
*IF *VALUE KRC_REPLICA_SITUATIONS.Replica_F_Level *GE 0 *AND *VALUE KRC_REPLICA_SITUATIONS.Replica_F_Level *LT KRC_REPLICA_SITUATIONS.Host_F_Level
This situation is evaluated every 24 hours.
KRC_replica_f_level_unknown Replica feature level unknown. The feature level of this replica is not set. Run cleartool chflevel to set the replica feature level. After all replicas in the family have been raised to the same feature level, the family feature level can be raised. For more information, see Technote 21246890 The default configuration has the following SQL syntax:
*IF *VALUE KRC_REPLICA_SITUATIONS.Replica_F_Level *LT 0
This situation is evaluated every 1 hour.
KRC_family_f_level_low
Family feature level can be raised.
The family feature level of this replica family is lower than the highest feature level supported by all family members. Run cleartool chflevel at the site that masters the VOB object to raise the family feature level. This allows clients to take advantage of new features supported at the higher feature level.
The VOB family feature level must not be higher than the highest feature level of any replica in the family. Only those operations that are permitted at the family feature level can be imported to a replica in the family. This ensures that all family members can import the same set of operations.
The default configuration has the following SQL syntax:
*IF *VALUE KRC_REPLICA_SITUATIONS.Family_F_Level_Low *EQ 1
This situation is evaluated every 1 hour.
KRC_replica_f_level_too_high Replica feature level not supported on this host. The feature level of this replica is higher than the highest feature level supported by this host. This is probably because the replica was moved to this host from another host that was running a more recent release of ClearCase. Install a newer release of ClearCase on this host, or move this replica to a host whose ClearCase release supports its feature level. The default configuration has the following SQL syntax:
*IF *VALUE KRC_REPLICA_SITUATIONS.Replica_F_Level *GE 0 *AND *VALUE KRC_REPLICA_SITUATIONS.Replica_F_Level *GT KRC_REPLICA_SITUATIONS.Host_F_Level *AND *VALUE KRC_REPLICA_SITUATIONS.Replica_F_Level *GT KRC_REPLICA_SITUATIONS.Family_F_Level
This situation is evaluated every 1 hour.
KRC_family_f_level_too_high
Family and replica feature levels not supported on this host.
The feature level of this replica and family feature level of this replica family are higher than the highest feature level supported by this host. This is probably because the replica was moved to this host from another host that was running a more recent release of ClearCase. Install a newer release of ClearCase on this host, or move this replica to a host whose ClearCase release supports its feature level.
The VOB family feature level must not be higher than the highest feature level of any replica in the family. Only those operations that are permitted at the family feature level can be imported to a replica in the family. This ensures that all family members can import the same set of operations.
The default configuration has the following SQL syntax:
*IF *VALUE KRC_REPLICA_SITUATIONS.Replica_F_Level *GE 0 *AND *VALUE KRC_REPLICA_SITUATIONS.Replica_F_Level *GT KRC_REPLICA_SITUATIONS.Host_F_Level *AND *VALUE KRC_REPLICA_SITUATIONS.Replica_F_Level *EQ KRC_REPLICA_SITUATIONS.Family_F_Level
This situation is evaluated every 1 hour.
KRC_f_level_mismatch
Replica feature level not supported on this host.
The family feature level of this replica is higher than the highest feature level supported by this host. This is probably because the replica was moved to this host from another host that was running a more recent release of ClearCase. Install a newer release of ClearCase on this host, or move this replica to a host whose ClearCase release supports its feature level.
The VOB family feature level must not be higher than the highest feature level of any replica in the family. Only those operations that are permitted at the family feature level can be imported to a replica in the family. This ensures that all family members can import the same set of operations.
The default configuration has the following SQL syntax:
*IF *VALUE KRC_REPLICA_SITUATIONS.Replica_F_Level *GE 0 *AND *VALUE KRC_REPLICA_SITUATIONS.Replica_F_Level *EQ KRC_REPLICA_SITUATIONS.Host_F_Level *AND *VALUE KRC_REPLICA_SITUATIONS.Replica_F_Level *LT KRC_REPLICA_SITUATIONS.Family_F_Level
This situation is evaluated every 1 hour.
KRC_shipping_bay_space Device hosting bays has filled up beyond the configured limit. Increase available space on the device by removing nonessential files and folders, or move the shipping bay to a device that has more space. On Windows hosts, free space on the device where the bays are located must be at least twice the size of the largest packet that will be stored in the bays. There can be two copies of the same packet in the bay at one time: one on its way to another destination and another waiting to be applied to the replica on the host. The default configuration has the following SQL syntax:
*IF *VALUE KRC_SHIPPING_BAYS.Percent_Used *GT 95
This situation is evaluated every 30 minutes.
KRC_inbay_too_long A packet has been in the shipping bay longer than expected. A packet on which this packet depends may have been delayed or lost in transit. This packet cannot be applied to the replica until another sibling sends the oplogs that were in the lost packet. Open the Epochs workspace and check the epoch tables to determine whether the packet's dependencies have been met. Open the Logs workspace and look for errors in MultiSite logs. For more information, see Technote 1132053 (Packet depends on changes not yet received) The default configuration has the following SQL syntax:
*IF *VALUE KRC_FAMILY_HEALTH.Inbay_Duration *GT 900
This situation is evaluated every 10 minutes.
KRC_view_space_low Device hosting views has filled up beyond the configured limit. Increase available disk space by removing unnecessary files from this volume, or move the view storage to a device that has more space. The default configuration has the following SQL syntax:
*IF *VALUE KRC_VIEW_SPACE.Usage_Percentage *GT 95
This situation is evaluated every 24 hours.
KRC_pool_space Device hosting pools has filled up beyond the configured limit. If space is being taken up by Derived Objects (DOs), use the Views workspace to look for unused views holding references to DOs in this VOB. Removing such views reduces the reference counts of these DOs and may allow them to be scrubbed and their disk space reclaimed. If space is being taken up by cleartext, consider reducing the cleartext pool age so that it is scrubbed more aggressively. If there are files or folders on the device that are not part of the pool, remove them. If these steps do not free up enough space on the device, consider moving the pool to a device with more storage capacity The default configuration has the following SQL syntax:
*IF *VALUE KRC_POOLS.Percent_Used *GT 95
This situation is evaluated every 24 hours.
KRC_albddown The albd_server on this host is down The ClearCase albd_server process on this host is down. Possible causes for this include the host being rebooted or an administrator deliberately stopping the albd_server. Check the albd_server log on this host for more information. ClearCase will be unavailable on this machine until the albd_server is running again. The default configuration has the following SQL syntax:
*IF *SCAN KRC_AVAILABILITY.Name *EQ albd_server.exe *AND *VALUE KRC_AVAILABILITY.Status *EQ DOWN
This situation is evaluated every 1 minute.
KRC_albddown The albd_server on this host is down The ClearCase albd_server process on this host is down. Possible causes for this include the host being rebooted or an administrator deliberately stopping the albd_server. Check the albd_server log on this host for more information. ClearCase will be unavailable on this machine until the albd_server is running again. The default configuration has the following SQL syntax:
*IF *SCAN KRC_AVAILABILITY.Name *EQ albd_server *AND *VALUE KRC_AVAILABILITY.Status *EQ DOWN
This situation is evaluated every 1 minute.
KRC_Process_Data_Unavailable Unable to gather process data for this process. The agent was unable to gather performance data for the process. If the problem persists, the Process performance class might be disabled. To enable the process performance class you can use the tool at 'http://www.microsoft.com/windows2000/techinfo/reskit/tools/existing/exctrlst-o.asp' to enable the 'PerfProc' counter. Once this is enabled, restart the agent. The default configuration has the following SQL syntax:
*IF *VALUE KRC_AVAILABILITY.Type *EQ PROCESS *AND *VALUE KRC_AVAILABILITY.Status *EQ PROCESS_DATA_NOT_AVAILABLE
This situation is evaluated every 1 minute.
The condition specified in the situation evaluates to "True" after the situation is triggered 3 consecutive times.
Related topics:
Organization of the predefined workspaces