There are times when recoveries exist but are no longer associated with a job. The following conditions could cause recoveries to become orphaned:
-
An unplanned switch has occurred
-
The MIMIX subsystem was ended unexpectedly
-
A recovery job was ended unexpectedly
When automatic audit recovery is enabled, orphaned recoveries are converted to error notifications during system cleanup. If the orphaned recovery is older than the cleanup time specified in the system definition, it is deleted.
When automatic database recovery or automatic object recovery is enabled, orphaned recoveries are deleted, when possible.
Because recoveries are displayed on both systems, but jobs associated with them are only accessible from the originating system, you need to verify that the recovery is orphaned before removing it.