BMC AMI Recovery Manager object exception status
The following table lists the various types of object status that can be returned by BMC AMI Recovery Manager and provides corrective actions you can take.
An object must have a status of OK for BMC AMI Recovery Manager to include it in recovery JCL.
For backup JCL, objects with certain non-OK statuses are included in addition to those with an OK status. These are also indicated in the following table.
Status | Included in Backup JCL | Included in Recovery JCL | Explanation | User Response |
|---|---|---|---|---|
ALTER IX | Yes | No | The partitioned index has been altered and requires that all affected partitions be included in the recovery. | Include all affected partitions in the object set. Use action code L and then D to view the SYSCOPY detail. |
BADDSNUM | No | No | According to the Db2 catalog, the space is a nonpartitioned space and the data set number that is provided is not in the range of 1 to 32. | Return to the Object List Generation panel and correct the data set number. |
BAD PART | No | No | According to the Db2 catalog, the object is partitioned and the partition number is not valid. | Return to the Object List Generation panel and correct the partition number. |
BADSHRL | No | No | A SHRLEVEL CHANGE copy cannot be used to recover a NOT LOGGED object that is not a LOB. The object is not included in the recovery | You can select an alternate recovery point for the object (action code L) or select Recover again and choose a new recovery point for the entire object set. It is possible that there is no valid recovery point for the object. |
BAD TYPE | Yes | No | The object is not recoverable to the selected recovery point. An entry in SYSIBM.SYSCOPY indicates that an event that prevents recovery occurred between the recovery point and the prior full image copy. Events precluding a recovery are REORG LOG NO, LOAD LOG NO, LOAD REPLACE LOG NO, or a table being altered to rotate partitions. | You can select an alternate recovery point for the object (action code L) or select Recover again and choose a new recovery point for the entire object set. It is possible that there is no valid recovery point for the object. |
DEFER | No | No | The object was created with DEFINE NO. The underlying data set does not exist. | No action is required. |
DS LEVEL | Yes | No | Copies are needed for recovery by data set, but the object is not expanded by partition and either DSNUTILB is specified or BMC AMI Recover and a partial recovery is specified. | Expand the object into its component partitions in the Object List Generation or List Generation Options panel, as appropriate to your method of object list generation. |
INFLIGHT | Yes | No | This status applies to Db2 V8 and higher. It indicates the object cannot be recovered because the selected recovery utility is DSNUTILB (inflight recovery is only possible when BMC AMI Recover is the recovery utility) | You must manually recover the object. |
INVRECPT | No | Yes | The recovery point is invalid for the specified NOT LOGGED object. A NOT LOGGED object requires recovery to a copy, to an ALTER NOT LOGGED point, or to a CREATE NOT LOGGED point. | You can select an alternate recovery point for the object (action code L) or select Recover again and choose a new recovery point for the entire object set. It is possible that there is no valid recovery point for the object. |
NOCOPIES | Yes | No | No image copies were found in SYSIBM.SYSCOPY for the object, and there were no LOAD REPLACE LOG (YES), LOAD LOG (YES), or REORG LOG (YES) copies. This status applies only to table spaces. | Perform a separate recovery on such objects; select Recover and specify Log Only. This task requires that the space has already been restored outside of Db2 and BMC AMI Recovery Manager (for example, a volume restore). |
NOTAVAIL | Yes | No | A recovery to a specified copy or quiesce point was requested but the copy or quiesce point could not be found. The specified copy or quiesce recovery point could not be found within the specified SYSCOPY limit. | Select an alternate recovery point for the object (action code L) or select Recover again and choose a new object set recovery point. There may be no valid recovery point for the object. |
NOTCLONED | Yes | Yes | A backup or recovery for clones only was requested. The specified object is not a clone and will not be included in the operation. | No action is required. |
NOTDEFND | No | No | The index, table space, or partition was not found in the Db2 catalog. | Return to the Object List Generation panel and correct the entry. |
OK | Yes | Yes | Object status is satisfactory. | No action is required. |
PEND DDL | Yes | No | An entry in SYSIBM.SYSPENDINGDDL prevents the object from being recovered. | No action is required. |
SYS OBJ | No | No | The object is a table space or index from the Db2 catalog and directory or from a temporary database. | Back up or recover the object by using System Resources on the Main Menu. |
TBLPART | No | No | This status applies to Db2 V8 and higher. It indicates that the table space was defined with table-based partitioning. BMC AMI Recovery Manager does not back up or recover such table spaces or any of the associated indexes when using BMC AMI Recover version 5.1 or earlier. | You must manually back up and recover tables defined with table-based partitioning and their associated indexes. |
TEMPDB | No | No | The object is a table space or index from a declared temporary database. | No action is required, although an object from a temporary database cannot be copied or recovered. We recommend that you remove these objects from any BMC AMI Recovery Manager object sets to increase product efficiency. |
TSREORP | No | No | Applies only to indexes. Following a PIT recovery, the table space on which the index is based is placed in REORG PENDING status, and the index cannot be recovered or rebuilt. | REORG the table space and its indexes or select an alternate recovery point. |
TS STAT | No | No | Applies only to indexes. The table space on which the index is based has a status other than OK. | Correct the table space problem indicated by the table space status if possible, or proceed to generate JCL without those objects. |
UNCHANGE | No | No | After a partial verification, this denotes that the table space has had no updates and will be excluded from the backup or recovery JCL. | No action is required. |
VARBIN | Yes | No | Applies only to indexes. DSNUTILB does not support Rebuild Index if the index has a VARBINARY column. | No action is required. |
Related topics